< Previous | Next >

Lesson 1.4: Publish the service to WebSphere Service Registry and Repository

After the developer develops, tests, and builds the solution in a regular development build, she can submit the solution as an asset to Rational® Asset Manager as a formal solution. The developer then publishes this solution-level asset to WSRR. The solution-level asset includes the WSDL and all of the code that implements the service.

When the developer publishes the formal build that is associated with the WSDL service to WSRR and the service concept is in the published state, WSRR must govern the service interface. To allow WSRR to govern the service interface, the developer publishes the service WSDL by using the implementation asset in Rational Asset Manager. This creates a production-ready solution in WSRR.

After the developer publishes both the WSDL and the implementation assets to complete the production-ready solution, she returns to WSRR and changes the service governance to the 'Versioned' state. As shown in the following illustration, the developer creates a formal relationship from the service solution to the existing service concept.

Related service to the low touch claim service concept.

After the developer creates this relationship, the implementation and the service are integrated at deployment time. View the following graphical outline of the solution.

Comprehensive solution illustrating the mapping between the concept, the solution, and the implementation in WSRR.

Lesson checkpoint

You watched a demonstration of how to publish assets from Rational Asset Manager in WebSphere Service Registry and Repository and how to create relationships in WSRR that map the solution and the implementation for the service.
< Previous | Next >

Feedback