When you drag an action from the Policy Actions area, the respective step in the Message Flow area highlights where the action fits in, this making the navigation from Policy Actions area to the Message Flow area more intuitive.

Not all stages support the full set of actions. Every action happens only within a respective step. For example, the “Evaluate” actions occur only on the Enforce step; while the “Routing” actions occur only on the Routing step.

Mediator executes the run-time actions configured for a virtual API in a predefined order.

Some actions are mutually dependent. That is, a specific action must be used in conjunction with another particular action. For example, a Message Flow area that includes the Set JMS Headers action must also include the JMS Routing Rule action.

Some actions are mutually exclusive. That is, a specific action cannot be used in conjunction with another particular action. For example, a Message Flow area that includes the JMS Routing Rule action cannot include the Straight Through Routing action.

Some of the actions are allowed to appear multiple times within a message flow step.

For information about the individual run-time actions that are supported out-of-the-box, see Run-Time Governance Reference.

For information about how Mediator executes actions (and how to avoid policy conflicts), see Run-Time Governance Reference.

You can view a tooltip text for any accordion by moving the cursor over the accordion name. The tooltip text gives a summary of the accordion’s purpose.

If you modify the run-time action for a virtual API that is already deployed to webMethods Mediator, CentraSite automatically redeploys the modified API.