- Considerations for customizing a governance lifecycle
The governance lifecycle represents the states and transitions that can exist in your SOA deployment. - Considerations when removing a lifecycle
Before you install a new governance lifecycle, you must remove the existing lifecycle, and might have to update other configuration items dependent on the defined lifecycle states and transitions. - Defining a new governance lifecycle by using IBM Integration Designer
When defining a new governance lifecycle, you must be aware of the key states that you want to represent. - Manually defining a new governance lifecycle
To manually define a new governance lifecycle, you must create a new SACL file. This is an XML file that corresponds to the SACL schema. - Manually defining a state machine in a lifecycle
Any state machine defined in a SACL file (either mainStateMachine or compositeStateMachine) is built up from a number of key elements that define the state transition model of the state machine. - Configuring a lifecycle classification system
To distinguish the lifecycle classification system from a basic classification system, extra information must be added to the OWL file. - Updating the lifecycle
You can update the lifecycle in separate stages, or by using a script. - Defining state based access controls
To define state based access controls, a set of permissions must be created to correspond to the actions that are to be allowed for any given artifact criteria/state combination. - Defining views based on the lifecycle
After a new lifecycle has been created, it is useful to create web UI views that can filter the service artifacts on the basis of their states.
Parent topic: Configuring and customizing
Related concepts:
Related reference:
