Configuring promotion to multiple runtime environments

If you have multiple runtime environments that are not configured in a cluster, you can still promote to all these environments in a single operation.

Consider an example configuration where there is a single logical staging environment, but it is composed of separate WSRR instances that are not clustered. The instances are in three different geographical locations. The locations are physically so far apart that clustering is not appropriate because of the large latency that such distances impose.

The solution involves defining subclassses to a parent classification (see the related link). The logical Staging environment is split into three physical instances in different data centers. The three child environments are subclasses of Staging:

Staging
               ->StagingEast
               ->StagingWest
               ->StagingCentral

These environments are defined in the standard way in the environments section of the promotion properties configuration file:

<environment
  name="http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingEast">
  <promotion>
    <type>sync-minimal</type>
  </promotion>
  <servers>
    <server name="stgeast.jkhe.com" port="2809"/>
  </servers>
  <security enabled="true">
    <wsrrUser>usereast</wsrrUser>
    <wsrrPassword>passwordeast</wsrrPassword>
  </security>
</environment>
<environment
  name="http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingWest">
  <promotion>
    <type>sync-minimal</type>
  </promotion>
  <servers>
    <server name="stgwest.jkhe.com" port="2809"/>
  </servers>
  <security enabled="true">
    <wsrrUser>userwest</wsrrUser>
    <wsrrPassword>passwordwest</wsrrPassword>
  </security>
</environment>
<environment
  name="http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingCentral">
  <promotion>
    <type>sync-minimal</type>
  </promotion>
  <servers>
    <server name="stgcent.jkhe.com" port="2809"/>
  </servers>
  <security enabled="true">
    <wsrrUser>usercent</wsrrUser>
    <wsrrPassword>passwordcent</wsrrPassword>
  </security>

All three staging environments must be explicitly listed for a transition that triggers a promotion to the logical staging environment:

<transition 
  name="http://www.ibm.com/xmlns/prod/serviceregistry/6/0/GovernanceProfileLifecycle#ApproveStagingDeployment">
  <target-environments>
    <name>
      http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingEast
    </name>
    <name>
      http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingWest 
    </name>
    <name>
      http://www.ibm.com/xmlns/prod/serviceregistry/6/1/GovernanceProfileTaxonomy#StagingCentral 
    </name>
  </target-environments>
</transition>

When an object undergoes the ApproveStagingDeployment transition, three promotions are triggered: one to each of the three physical staging environments. Objects that are classified with the parent environment (Staging) will be promoted to all three physical staging environments. Objects classified with a specific sub-classification will be promoted to that environment only.