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 run-time policy, you must place the policy in the Productive state. Switching the policy to the Productive state triggers an internal system policy that activates the policy and makes it eligible for deployment.

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.