WSRR ALEConfiguration file

The first three definitions map the three types of Business Capability on WSRR to three different categories of Business Solution on Rational Asset Manager:

• Business Application on WSRR maps to a Web Application on Rational Asset Manager
• Business Service on WSRR maps to a Service on Rational Asset Manager
• Business Process on WSRR maps to a Process on Rational Asset Manager

<Mapping extends="BUSCAP" ramCategory="Software Development/Kind/Web Application" ramType="Business Solution"
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessApplication" />
<Mapping extends="BUSCAP" ramCategory="Software Development/Kind/Service" ramType="Business Solution" 
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessService" />
<Mapping extends="BUSCAP" ramCategory="Software Development/Kind/Process" ramType="Business Solution" 
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessProcess" />

These Business Capability types extend the BUSCAP mapping:

<Mapping extends="ASSET" id="BUSCAP" ramType="Business Solution" 
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessCapability">
  <Relationship ramName="specification" wsrrName="gep63_capabilityVersions"/>
  <Relationship ramArtifactLabel="Charter" ramName="_artifactLabel1" wsrrName="gep63_charter"/>
</Mapping>

Each Business Capability maps a couple of relationships. The gep63_capabilityVersions relationship now maps to the specification relationship on Rational Asset Manager and not to a release; in this interaction WSRR Service Versions map to Rational Asset Manager Specifications.

The Business Capability then extends the ASSET mapping:

<Mapping id="ASSET" ramType="RAM_Asset" 
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/v6r3/ALEModel#Asset">
  <Attribute ramName="RAM_description" wsrrName="WSRR_description"/>
  <Attribute map="RAM" ramName="RAM_state" wsrrName="ale63_remoteState"/>
</Mapping>  

This means that all objects of these types will map:

• The WSRR_description attribute to the RAM_description attribute.
• The WSRR ale63_remoteState attribute to the RAM_state attribute. To see the state that the corresponding Rational Asset Manager asset is in, you can view any Advanced Lifecycle Edition synchronized object in WSRR.

The other main object type to be considered is the Service Version, which is mapped to a Rational Asset Manager Specification:

<Mapping extends="ASSET" id="SV" ramCategory="Software Development/Kind/Service/Interface" ramType="Specification"   
  wsrrType="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#ServiceVersion" />  

Consider the definitions for the WSRR Business Capability object type:

<Trigger source="WSRR" state="http://www.ibm.com/xmlns/prod/serviceregistry/lifecycle/v6r3/LifecycleDefinition#CharterReview" 
  type="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessCapability">
	<Action action="create" target="RAM"/>
	<Action action="update" target="RAM"/>
	<Action action="transition" state="Proposed" target="RAM" transition="com.ibm.ram.businessSolution.action.propose"/>
</Trigger>

<Trigger source="WSRR" state="http://www.ibm.com/xmlns/prod/serviceregistry/lifecycle/v6r3/LifecycleDefinition#CapabilityApproved" 
  type="http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceEnablementModel#BusinessCapability">
	<Action action="update" target="RAM"/>
	<Action action="transition" state="Approved" target="RAM" transition="com.ibm.ram.businessSolution.action.approve"/>
</Trigger>

The first trigger is met when the BusinessCapability reaches the state of CharterReview. When the state is met, the following actions are completed:

1. A Business Solution is created on Rational Asset Manager.
2. The Business Solution is updated by WSRR.
3. The Business Solution is moved through the lifecycle into the Proposed state using the propose transition action.

The second trigger is met some time later when the BusinessCapability reaches the state of CapabilityApproved. When the state is met the following actions are completed:

• The Business Solution is updated by WSRR.
• The Business Solution is moved through the lifecycle into the Approved state using the approve transition action.

You can see these transitions and actions in Figure 1.

In the configuration file there are equivalent triggers for the three specific types of BusinessCapability:

• BusinessApplication
• BusinessService
• BusinessProcess