How do I know if I need the WebSphere Service Registry and Repository?
The promise of SOA depends heavily on the ability to share assets. Such sharing requires coordinated facilities for access and control. With SOA adoption, the increase in the number of services that an organization needs to track and manage becomes evident. Also, with adoption comes the recognition of a need for better processes to manage the lifecycle of services. A disciplined approach to lifecycle management, part of the overall governance, helps ensure that the design, development, deployment, and operation of services adhere to policies. In the most effective SOA deployments, governance processes are woven throughout all phases of the lifecycle. Governance addresses the need for financial transparency, the alignment between business and IT, and process control, as well as how these business imperatives are achieved. The right software tools can greatly facilitate governance. These are some of the primary indications on when one should consider WebSphere Service Registry and Reposi
Related Questions
- What is the roadmap of WebSphere Service Registry and Repository in relation to Web Services Gateway/UDDI in WAS?
- Are there other IBM products that will help me get the most out of my WebSphere Service Registry and Repository?
- How does the WebSphere Service Registry and Repository integrate with other IBM products?
