Activating a Run-Time Policy
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 of its 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.
The icon in the Active column on the Policies > Run-Time page indicates the policy’s activation state as follows:
Icon | Description |
| Policy is active. |
| Policy is inactive. |
The activation state of a policy is also reported next to the State field in the Run-Time Policy Details page.
1. In CentraSite Control, go to Policies > Run-Time.
This displays a list of defined run-time policies in the Run-Time Policies page.
2. Locate the policy you want to activate and select Details from its context menu.
This opens the Run-Time Policy Details page.
3. Examine the Actions profile and verify that all of the actions on this profile display the green checkmark icon in the Parameters Set column. If any of the actions display the red circle icon in this column, set their parameters before you continue.
4. In the Policy Information panel, click Change State. (If you do not see Change State, it is probably because you do not have permission to change the lifecycle state of a policy.)
5. In the Change Lifecycle State dialog box, select the Productive lifecycle state and click OK.
6. Examine the State field in the Policy Information panel to verify that the policy's state has been changed.
If this state change requires approval, the State field 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.
Note:
While the policy is in pending mode, it cannot be edited.
7. After you activate the policy, users with the proper permissions can deploy the services to your PEP. At that time, CentraSite automatically validates the service's policies (for example, check for policy conflicts or other violations).
