Advanced tutorial: Configuring the Advanced Lifecycle Edition

This is an advanced tutorial which shows how you can modify the interaction and synchronization between WSRR and IBM® Rational® Asset Manager.

The definitions that make up the synchronization pattern between Rational Asset Manager and WSRR are described in the following topics Behavior customizations for Advanced Lifecycle Edition. This tutorial gives a real-life example of how modifications to the configuration can be achieved by looking at each section in the configuration files.

This tutorial simplifies the interaction by:

Removing the DOU and the Service Interface Specification to be synchronized.
Having the main interactions with Business Capabilities managed by WSRR.
Having the main interactions with Capability Versions managed by Rational Asset Manager.

Time required

This tutorial should take approximately 3 hours to complete. If you explore other concepts related to this tutorial, it could take longer to complete.

Skill level

Advanced.

Audience

This tutorial is intended for advanced users who are considering changing the default interaction between WSRR and Rational Asset Manager. It is aimed at integration specialists who are familiar with the modelling and lifecycles on both WSRR and Rational Asset Manager.

System requirements

You are required to use:

WSRR Studio V8.0 and above.
WSRR V8.0 and above.
IBM Rational Asset Manager V7.5 and above.

Prerequisites

Before reading this tutorial you should make sure that you understand how the lifecycles work on both Rational Asset Manager and WSRR. Additionally, you should also understand the existing Advanced Lifecycle Edition (ALE) configuration on Rational Asset Manager; for more information, see Integrating with WebSphere Service Registry and Repository in the Rational Asset Manager Information Center.

You should also understand the existing ALE configuration on WSRR; for more information, see Integration with Rational Asset Manager. In planning for any changes in the ALE configuration, you must understand what changes you need in the Rational Asset Manager and WSRR lifecycles for the objects that are of interest to you. For changes in the WSRR profile, consult the WSRR Studio documentation; for more information, see WSRR Studio.

Before you begin:

This tutorial illustrates the concepts of the synchronizations in the Advanced Lifecycle Edition and is not intended as a set of recommended changes. However, if as part of the tutorial you choose to make changes to your system, create a backup copy of the configuration files, both called ALEConfiguration.xml, for WSRR and Rational Asset Manager prior to making any changes.
Download the tutorial sample files ALEConfigurationScenario.zip, and extract the contents of the compressed file to a location of your choice. The file contains the following:
- The WSRR /WSRR/ALEConfiguration.xml file, described in the following lesson: WSRR ALEConfiguration file.
- The Rational Asset Manager /RAM/ALEConfiguration.xml file, described in the following lesson: Rational Asset Manager ALEConfiguration file.

Expected results

The following diagrams summarize the simplified interactions between WSRR and Rational Asset Manager which this tutorial will achieve through modifications to the configuration files on WSRR and Rational Asset Manager systems. These particular interactions might not suit your own requirements; they are for illustrative purposes only.

The story starts when a business user creates a Business Capability and places it in Charter Review state. This transition will result in a Business Solution being created on Rational Asset Manager. This Business Solution is then automatically transitioned into the Proposed state.

Figure 1. Business capability & Business solution synchronization managed by WSRR.

Figure 2. Service Version & Specification synchronization managed by Rational Asset Manager.

As shown in Figure 2, the Service Version object is now mapped to a Rational Asset Manager Specification object (the default Rational Asset Manager mapping is to a Release object). The Release object will still be involved in the modelling, as will be shown later in this tutorial.

Figure 2 follows on from Figure 1; a Specification object was automatically created in Rational Asset Manager when the Business Capability was moved into an Approved state in WSRR. On the Rational Asset Manager system, the Release and the Specification objects need descriptions and dates to be associated with them. Additionally, the Specification object must be directly associated with the Release object. It is the act of classifying the Specification as a Service Interface that triggers the creation of the Service Version in WSRR, see Figure 3 for more information.

Figure 3. Service Version & Specification synchronization continued.

When the Specification has been classified it must be approved on the Rational Asset Manager system by transitioning it into the Scoped state. This transition drives the equivalent transition in WSRR. When the WSDL or XSD document has been developed on Rational Asset Manager, they must be associated with the Specification object so that the Specification can be placed in the Specified state. Finally, the Specification is Approved, which triggers the transition to the Specified state in WSRR and also copies the artifacts to WSRR.

Beyond these interaction diagrams, the governance story is exactly the same as described in the existing governance enablement profile tutorials; a Service Level Definition with associated endpoints must still be defined and approved, endpoints must still be defined and approved in staging and production environments, and so on. For more information about these activities, see the governance enablement profile tutorials: Tutorials for the governance enablement profile.

< Previous | Next >