CentraSite User's Guide : Runtime Governance : Run-Time Policy Management : Managing Run-Time Policies through CentraSite Business UI : Modifying Run-Time Policy Details
Modifying Run-Time Policy Details
Pre-requisites:
To examine and modify the properties of a run-time policy in CentraSite, you must have one of the following permissions:
*To examine and modify the properties of a organization-specific policy, you must have the Manage Run-Time Policies permission for the organization specified in the scope of the original policy. For example, if the original policy is scoped for organization ABC, you are not permitted to examine and modify the properties of that policy unless you have permission to manage run-time policies for organization ABC.
*To examine and modify the properties of a system-wide policy, you must have the Manage System-Wide Run-Time Policies permission.
Important:  
If you belong to a role that includes the Manage System-Wide Run-Time Policies permission, you have the ability to modify CentraSite's predefined policies. However, you should not do this. These policies perform critical functions within the registry and must not be modified except under the direction of a technical representative from Software AG.
You cannot modify a policy while it is in the Productive state. To make changes to a policy, you can do any of the following:
*Create a new version of the policy, make the necessary changes to the new version and switch the new version to the Productive state when you are ready to put it into effect. Switching the new version to the Productive state will immediately put the previous version in the Retired state. (The Retired state is an end state. After you place a policy in this state, you can no longer reactivate it.)
*Create a completely new policy that includes the required changes. When you are ready to put the new policy into effect, switch the old policy to the Suspended state and switch the new policy to the Productive state. When you are certain that you will no longer need to revert to the original policy, switch it to the Retired state.
*Switch the existing policy to the Suspended state, make the necessary changes to the policy and then switch it back to the Productive state. While the policy is in the Suspended state, it will not be enforced. (Because suspending the policy results in an enforcement gap, one usually does not use this approach in a production environment.)
To view or modify the properties of a run-time policy
1. In the CentraSite Business UI activity bar, click Manage Governance Rules.
2. To filter the list to see just a list of the available policies, do the following:
a. Go to the advanced search panel.
b. In the Narrow Your Results section, do the following:
a. Locate Applicable Scopes.
b. Choose Runtime Policy from the drop-down list.
c. Click the plus button next to the drop-down box or press Enter to add the scope Runtime Policy to the search recipe.
CentraSite displays the list of runtime policies that are available to you in the Search Results for Governance Rules page.
3. Click the policy you want to examine and modify the attributes.
This opens the Run-Time Policy Details page.
4. If the policy is active, deactivate it.
You cannot modify the details of an active policy.
5. On the Run-Time Policy Details page, examine or modify the properties as required.
Field
Description
Name
The name of the run-time 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, we recommend that organizations adopt appropriate naming conventions to ensure the assignment of distinct policy names.
Description
(Optional). Additional comments or descriptive information about the policy.
Version
The user-assigned version ID assigned to this policy. You may use any versioning scheme you select for identifying different versions of a policy. The identifier does not need to be numeric.
Examples:
0.0a
1.0.0 (beta)
Pre-release 001
V1-2007.04.30
Apply policy to all organizations (option)
This property determines if the policy is system-wide (global).
Apply Policy to Organization
This property determines if the policy belongs to a specific organization.
Filters
The settings on this section determine the virtual types to which the policy is applied.
Policy Actions Message Flow
The settings on this area specify the actions that the gateway executes when the policy is enforced.
Gateways
One or more gateways to which the policy is published.
Published Virtual APIs
Displays the list of virtual APIs/virtual REST APIs/virtual XML APIs to which the policy applies.
6. Click Save.
7. When you are ready to put the policy into effect, activate and publish the policy.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)
Product LogoContact Support   |   Community   |   Feedback