Associating policy sets and bindings with message flows and nodes

Use the BAR file editor to associate policy sets and bindings with message flows and nodes, so that they are available to the integration node at run time.

Before you begin

Use the WS Policy Sets and Bindings editor to create and configure policy sets and bindings (see Implementing WS-Security).

These instructions also assume that you have packaged your message flow in a BAR file.

About this task

You can associate a policy set with a message flow or with specific message flow nodes. Associations that are made with a flow apply to all message flow nodes described in the Policy Set and Bindings file. Associations at the flow level are defined as being either for consumer or provider nodes.

An association at the message flow node level overrides any association made at the message flow level. You do not enter information about consumer or provider for an association at message flow node level.

Procedure

  1. In the IBM® App Connect Enterprise Toolkit, open the BAR file that contains the message flow that you want to associate with a policy set and binding.
  2. Click the Manage tab.
  3. Click the message flow or node that you want to associate with a policy set and binding.
    The properties that you can configure for the message flow or for the message flow node are displayed in the Properties view.
  4. If you are configuring a message flow, enter values in the following fields in the Properties view, in the form {policy_project_name}:policy_set_name or {policy_project_name}:policy_set_bindings_name
    • Consumer Policy Set
    • Consumer Policy Set Bindings
    • Provider Policy Set
    • Provider Policy Set Bindings
  5. If you are configuring a message flow node, enter values in the following fields in the Properties view, in the form {policy_project_name}:policy_set_name or {policy_project_name}:policy_set_bindings_name
    • Policy Set
    • Policy Set Bindings

What to do next

For new associations to take effect, deploy the BAR file, then stop and restart the associated message flow.