Integration
(in-te-gra-tion)
a combination of parts or objects that work well together
Site Visits
IC Member Potpourri
Member Discussions
Integration Consortium
SOA Registry/Repository Questions
Question posted to IC Membership for feedback:
What are people using their SOA Registry / Repository for? Are they using it for more than just Web Services (e.g. COBOL MQ Services, relating dependencies to all service artifacts for a composite service, who is the audience, roles established for managing, administering and using a Registry Repository, etc.
Look forward to receiving IC member feedback. Login to respond.
1. Which Registry / Repository product are you using?
2. Are you using the Reg./Repos. to register all artifacts that make up a composite service, or just the WSDL and XSD? Examples:- BPEL - SCA Module- COBOL copy books?- COBOL MQ Services?- Service Architecture and Usage Documentation?
3. Are you using your Registry/Repository to facilitate governance of your services throughout the services lifecylce. If so, what types of governance are you implementing or planning on implementing?
4. What roles have you established for the administration and use of the Registry/Repository?
5. What audience is using the Registry/Repostiory and for what purposes (Business Analysts, Developers, Architects?)
Comments
|
Mark Kovacevich (htp://www.sophicgroup.net) says: Michael, One of my clients is in the midst of wrapping up a SOA repository, and I though I would share some of the experence with you. 1) BEA's ALER product, formerly known as Flashline. 2) The end goal of the implementation is to have all artifacts that make up the composite service, as well as the applications that are interfacing the service to be included. This includes the XML, WSDL, Meta Data, Components, Copy Books, BEPL, Process Model, Requirements, Database, DB tables, columns... ect. As you might imagine, acquiring this information in an automated fashion is quite complicated. So we narrowed our scope for phase one to just the composite service, it's sub-services, and all the documentation and artifacts that relate directly to that service. 3) The repository is going to be the lynchpin of our design time governance. I am not sure what you are asking regarding the second part of this question, can you please clarify? 4) We have a couple of roles. We first grant everone read access. The we have several submitter roles (Developer, Business Analyst, Project Manager). And then we have approver roles (Architect, Business Architect). 5) Initially, as we role the implementation our, the audience is going to be limited to IT personal, such as the IT Business Analyst/PM group and the deveopment/architect team. Hope this was helpful,
|
- November 2007 (1)
