Introduction
To help facilitate governance processes in an SOA, WebSphere Service
Registry and Repository (hereafter called Service Registry) provides a
simple mechanism for defining a life cycle that can be applied to
services managed within it. Objects or related groups of objects
stored in Service Registry can be transitioned through the states
defined in the life cycle, and the resulting states will be reflected
in the classification metadata associated with those objects. You can
use the Service Registry console or APIs to locate and use the objects
based upon these classifications.
Service Registry and Repository comes configured with a default service
life cycle based on IBM's SOA governance model. However, most
organizations will want to modify or replace this default life cycle
with one that matches their exact requirements. The states and
transitions of the Service Registry default life cycle are shown in Figure 1.
Figure 1. The default
WebSphere Service Registry and Repository life cycle
1 of 11 |
Next
Comments
Back to top
Help: Update or add to My dW interests
What's this?
This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.
And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.
View your My developerWorks profile
Return from help
static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere, SOA and Web services
ArticleID=253357
TutorialTitle=Multiple life cycles with WebSphere Service Registry and Repository
publish-date=09122007
author1-email=tim_baldwin@uk.ibm.com
author1-email-cc=crothemi@us.ibm.com