CentraSite 10.7 | CentraSite User’s Guide | Runtime Governance | Run-Time Policy Management | Managing Run-Time Policies through CentraSite Business UI | Activating a Run-Time Policy
 
Activating a Run-Time Policy
Note:
This section is not applicable if theCentraSite run-time aspects are not enabled. By default, run-time aspects configured from CentraSite are disabled. However, you can enable them if required. To enable theCentraSite run-time aspects, see Enabling CentraSite Run-Time Aspects.
Pre-requisites:
To activate a run-time policy in CentraSite, you must have one of the following permissions:
*To activate 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 activate that policy unless you have permission to manage run-time policies for organization ABC.
*To activate a system-wide policy, you must have the Manage System-Wide Run-Time Policies permission.
A run-time policy is not eligible for deployment unless it is active. In other words, when CentraSite deploys a virtual service, it uses only active run-time policies to produce the effective policy for the virtual service. Whether a run-time policy is active or inactive is determined by its lifecycle state.
Run-time policies are governed by the same lifecycle model as design/change-time policies. The predefined lifecycle model for policies that is installed with CentraSite is made up of four states: New, Productive, Suspended and Retired. Under this lifecycle model, all policies enter the New state when they are initially created.
While a run-time policy is in the New state, it is inactive. To activate a policy, you change the policy's lifecycle state to the Productive state. This state change executes CentraSite's Automatic Policy Activation policy.
Note:
The Automatic Policy Activation policy is a hidden system policy. You cannot edit or delete this policy.
If a virtual service is already deployed to webMethods Mediator and is in the scope of an activated run-time policy, you must redeploy the virtual service to Mediator so that the actions are activated.
Note:
We recommend that you use the lifecycle model that CentraSite provides for policies “as-is”, even for a multi-stage deployment.
CentraSite does not begin enforcing a run-time policy until you activate it.
When you activate a run-time policy, keep the following points in mind:
*You are not allowed to activate the policy unless all the required parameters have been set.
*Some organizations require an approval to activate the policy. If your organization has an approval action associated with the activation of a policy, CentraSite does not activate the policy until the required approvals are obtained.
*If an earlier version of the policy is already active, CentraSite deactivates the old version before it activates the new one. When a policy becomes active, CentraSite begins enforcing it immediately.
*When a policy becomes active, CentraSite begins enforcing it immediately. You can suspend enforcement of a policy by switching it to the Suspended state.
*To activate a policy, you must have permission to change the policy to the Productive state. To successfully change a policy to the Productive state, you must also have the Modify permission on all virtual type services to which the policy is applied.
*Upon activation of a policy, CentraSite applies the active policy to all of the virtual APIs that are in the scope of this policy.
*You should be aware that a run-time policy is automatically published whenever a virtual API associated to it is published to the Mediator gateway.
To determine whether a policy is active or inactive, examine the policy's decoration indicator on the Search Results for Governance Rules page. The decoration indicates the policy's activation state as follows:
Decoration
Description
Policy is active.
Policy is inactive.
*To activate a run-time policy
1. In the CentraSite Business UI activity bar, click Governance Rules.
2. To filter the list to see just a list of the available run-time 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 page.
3. Click the policy you want to activate.
This opens the Run-Time Policy Details page.
4. Examine the information on Run-Time Policy Details (Step 2 of 3) and verify that all of the actions on the Message Flow area are set properly.
5. In Run-Time Policy Details (Step 3 of 3), do one of the following:
*Click Activate to activate the policy. (If you do not see the Activate button, it is probably because you do not have permission to change the lifecycle state of a policy.)
*Click Activate and Publish to activate and publish the policy to webMethods Mediator in a single step. (If you do not see the Activate and Publish button, it is probably because you do not have permission to change the lifecycle state of a policy or publish the policy.)
6. Examine the policy's decoration indicator on the Search Results for Governance Rules page to verify that the policy's state has been changed.
If this state change requires approval, the policy's decoration indicator indicates that the policy is in the pending mode. CentraSite automatically switches the policy to the requested state (and activate the policy) after all the necessary approvals have been obtained.
Alternatively, in the Search Results for Governance Rules page, you can change the policy's lifecycle state to the Productive state, by toggling the policy's decoration indicator on and off.
Note:
While the policy is in pending mode, it cannot be edited.