Creating a Design/Change-Time Policy
Pre-requisites:
To create a new design/change-time policy, you must have one of the following permissions in CentraSite:
To create policies for a specific organization, you must have the Manage Design/Change-Time Policies permission for that organization. By default, users in the
CentraSite Administrator, Organization Administrator, or Policy Administrator role have this permission.
To create system-wide policies (that is, policies that apply to all organization within an instance of
CentraSite ), you must have the Manage System-Wide Design/Change-Time Policies permission. By default, users in the
CentraSite Administrator role and Operations Administrator role have this permission.
To create a design/change-time policy
1. In CentraSite Control, go to Policies > Design/Change-Time.
This displays a list of defined design-time and change-time policies in the Design/Change-Time Policies page.
2. Click Add Policy.
3. In the Policy Information panel, specify the following fields:
In this field... | Do the following... |
Name | Type a name for the new policy. A policy name can contain any character (including spaces). A policy name does not need to be unique within the registry. However, to reduce ambiguity, you should avoid giving multiple policies the same name. As a best practice, Software AG recommends that you adopt appropriate naming conventions to ensure that policies are distinctly named within your organization. |
Description | (Optional). Type a description for the new policy. This description appears when a user displays a list of policies in the user interface. |
Version | (Optional). Specify a version identifier for the new policy. Note: The version identifier does not need to be numeric. Examples: 0.0a 1.0.0 (beta) Pre-release 001 V1-2007.04.30 The version identifier you type here is the policy's public, user-assigned version identifier. CentraSite also maintains an internal, system-assigned version number for the policy. |
Priority | Type an integer that represents the priority of this policy with respect to other policies that might be triggered by the same event. The priority value determines the order in which the policies are enforced. The lower the Priority value, the higher the priority (that is, 0 is the highest priority and policies with this priority value are executed first). Priority values 0 through 10 and values greater than 9999 are reserved for predefined policies. You cannot assign these values to the user-defined policies that you create in CentraSite Control. The default priority for a user-defined policy is 11. |
4. In the Scope panel, specify the object and event types to which the policy applies.
In this field... | Do the following... |
Object Types | Specify the types of objects to which this policy applies. Note: If the object that you select is a base type that has virtual types associated with it, and the Inherit Base Type Policies option is enabled for certain of its virtual types, be aware that the policy you create is applied to instances of the base type and instances of those virtual types. |
Event Types | Specify the types of events to which this policy applies. Important: The OnCollect, OnMove and OnExport events are designed to execute handler and collector processes. Do not use these events unless you are creating a handler or collector policy. The improper use of these event types can damage the registry. |
Organization | Specify the organization to which the policy applies or select All if the policy applies to all organizations. Note: The Organization list contains the names of all organizations for which you have Manage Design/Change-Time Policies permission. The option appears in the list if you also have Manage System-Wide Design/Change-Time Policies permission. |
5. Click Next.
6. If you selected the PreStateChange or PostStateChange event in the previous panel and there is a lifecycle model for the object types that you have specified, CentraSite Control asks you to select the lifecycle states that triggers the policy. To complete this panel, do the following:
a. If you want the policy to execute immediately before the state is actually changed, click Add States in the Before the Object Enters State list and select the states that causes this policy to execute. (The Before the Object Enters State list is present if you selected the PreStateChange event in the previous panel.)
b. If you want the policy to execute immediately after the state is changed, click the Add States button in the After the Object Entered State list and select the states that causes this policy to execute. (The After the Object Entered State is present if you selected the PostStateChange event in the previous panel.)
c. Click Next.
7. From the Available Actions list, select the actions that you want CentraSite to execute when it applies this policy. Keep the following points in mind when you select the actions for the policy:
The actions shown in the
Available Actions list are determined by the object types and event types that you specified on the
Scope panel. If you do not see an action that you need, that action is probably not compatible with all of the object types and event types that you selected in the
Scope panel.
If necessary, you can click
Previous to return to the
Scope panel and change your object-type and event-type selections.
Ensure that the actions in the
Selected Actions list appear in the order that you want
CentraSite to execute them at enforcement time. If necessary, use the controls above the list to place the actions in the correct order.
Be aware that actions from the WS-I category cannot be combined with other types of actions. Also be aware that when you add a WS-I action to the action list,
CentraSite automatically adds dependent actions to the list as necessary.
8. Click Finish to save the new (as yet incomplete) policy.
9. Complete the new policy by doing the following:
a. Configure the parameters for each action on the Actions tab.
b. (Optional). Specify additional selection criteria to narrow the set of objects to which this policy applies.
c. If the policy is to be enforced during a PreStateChange or PostStateChange event, ensure that the options on the States tab specify the lifecycles and state changes to which the policy applies.
d. If you want to allow other users to view, edit, or delete this policy, click the Permissions tab and assign permissions to those users.
10. When you are ready to put the policy into effect, activate the policy.