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 choose 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. For more information about the settings on this Filters section, see Specifying the Scope of a Run-Time Policy. |
Policy Actions Message Flow | The settings on this area specify the actions that the gateway will execute when the policy is enforced. For more information about setting the properties on this area, see Assigning Actions to a Run-Time Policy. |
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. For more information, see Viewing the List of Virtual APIs to Which a
Run-Time Policy Applies. |