ITCAM for SOA 7.2 Fix Pack 1

SLD 'Supercede' Process Rule

The SLD 'Supercede' process rule determines the processing of the WSRR event that is generated when an SLD moves to a superceded state as part of the SLD governance lifecycle in WSRR.

When an SLD becomes superceded, it means that a new compatible service level definition becomes subscribable, with active endpoints, and the provider wants to move consumers and their service level agreements onto this new provided service level definition. No new subscriptions can be made to a service level definition in this state.

When ITCAM for SOA processes this event, it stops the situations that were created for this SLD.

Table 1 lists the transition of an SLD to a superceded state according to the default WSRR governance enablement profile:

Table 1. The transition of an SLD to a superceded state.
WSRR Lifecycle Transition	Transition URI in WSRR event	Event processing in ITCAM for SOA
Supercede	http://www.ibm.com/xmlns/prod/serviceregistry/lifecycle/v6r3/LifecycleDefinition#Supercede	Process

WSRR Notification Event

When an SLD transitions into the 'Supercede' governance lifecycle, WSRR sends an XML notification to ITCAM for SOA, as shown in the following example:

<?xml version="1.0" encoding="utf-8"?>
<body:resources xmlns:body="http://www.ibm.com/xmlns/prod/serviceregistry/
HttpPostNotifierPluginMsgBody">
    <body:resource bsrURI="65549565-d3ba-4aa8.934f.a025f2a04fb6" 
        correlationId="correlation-id1" 
        securityToken="security-token1" 
        type="Subscription">
    <body:notificationResource event="TRANSITION" 
        resourceBsrURI="29243729-5334-44a7.9cf3.3e234b3ef38a" 
        resourceName="MySLD"  
        resourcePrimaryType=
"http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceProfileExtensions#
ServiceLevelDefinition"  
        resourceToSubscribedRelationship="sameObject" 
        resourceType="GenericObject" 
        subscribedBsrUri="29243729-5334-44a7.9cf3.3e234b3ef38a" 
        subscribedName="MySLD" 
        subscribedPrimaryType=
"http://www.ibm.com/xmlns/prod/serviceregistry/profile/v6r3/GovernanceProfileExtensions#
ServiceLevelDefinition" 
        subscribedType="GenericObject" 
transition="http://www.ibm.com/xmlns/prod/serviceregistry/lifecycle/v6r3/
LifecycleDefinition#Supercede"/>
  </body:resource>
</body:resources>

Process Rule Definition

The default WSRR SDMS configuration file template includes the following process rule definition:

<!-- =======================================================
SLD 'Supercede'
======================================================== -->                        
<process-rule event="TRANSITION" 
 represents="SLD_Transition" 
 oif yperation="stop" 
 resourceToSubscribedRelationship="sameObject" 
 transition="alias_v6r3.ld.supersede">
 <rule-primary-types>
    <primary-types resourcePrimaryType="alias_v6r3.gp.extensions.sld" 
                   subscribedPrimaryType="alias_v6r3.gp.extensions.sld"/>
    <primary-types resourcePrimaryType="alias_v6r3.ge.model.sld" 
                   subscribedPrimaryType="alias_v6r3.ge.model.sld"/>
 </rule-primary-types>
</process-rule>

This process rule defines the processing of events that represent a transition of an SLD to a superseded lifecycle state. ITCAM for SOA stops situations for the SLD.

For events that represent a transition of an SLD to a superseded lifecycle state, stop situations for the SLD. In the example event, the SLD is identified by the following attribute:

subscribedBsrUri="29243729-5334-44a7.9cf3.3e234b3ef38a"

The primary types determine that the process rules must be applied to SLDs:

 <rule-primary-types>
    <primary-types resourcePrimaryType="alias_v6r3.gp.extensions.sld" 
                   subscribedPrimaryType="alias_v6r3.gp.extensions.sld"/>
    <primary-types resourcePrimaryType="alias_v6r3.ge.model.sld" 
                   subscribedPrimaryType="alias_v6r3.ge.model.sld"/>
 </rule-primary-types>

The action to take (stop situations) is determined by the following attribute:

operation="stop"

Modifying the Process Rule

You might have to modify this process rule if WSRR has a custom governance enablement profile. In this case, ensure that all the URIs in the process rule are valid in the custom profile.

Ensure that the URI of the WSRR lifecycle stage triggering the process rule is correct in the following line:

transition="alias_v6r3.ld.supersede"

If the existing value of the alias does not match the value in the governance enablement profile, change the alias to the new value. Alternatively, use the new value in the process rule instead of the alias.

Feedback