The SOA policy lifecycle

The SOA policy lifecycle is used to govern a policy from being initially identified, through to being deployed in production, and, finally, deprecated when it is no longer required.

When a policy has been created in WSRR, the policy gets initiated into the SOA policy lifecycle by default and is placed in the Identified governance state. For more information about the governance lifecycle states, including a diagram of the lifecycle and the transitions that moves the policy forward to each state, see IBM® WebSphere® Service Registry and Repository Version 8.0 Information Center - SOA policy lifecycle. The policy can also be transitioned back to a previous governance state to allow for revision of the policy.

A policy can be in one of the following states:
Even though all these governance states are valid states, when it comes to the IBM SOA Policy Pattern, the following are the valid governance states in which a policy is enforced:
  1. Approved
  2. Superceded
  3. Deprecated

Selection rules for determining which policy gets enforced

Any policy that is not in one of the valid states (Approved, Superceded, Deprecated) won't get enforced by the WebSphere Message Broker message flow. If multiple valid policies are retrieved from WSRR for a particular schedule condition, the following selection rules are applied:
  1. The governance state has the following order of precedence:
    • Approved
    • Superceded
    • Deprecated
  2. If more than one valid policy has the same highest precedence based on governance state, the policies are sorted in ascending order of policy names and the first policy is selected.
  3. If more than one valid policy share the same name and the same governance state, the policy that was updated most recently gets enforced.

Concept Concept

Feedback

Timestamp icon Last updated: Thursday, 3 July 2014
http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.soawmbwsrr.doc/topics/csoa_policies_soa_lifecycle.htm