When you add a message flow to a BAR file in preparation for deploying it to an integration node, you can set additional properties that influence its run time operation.
If a message flow or subflow has user-defined properties, you can configure these properties by selecting the relevant message flow or subflow (not the .cmf compiled message flow file); see Configuring a message flow at deployment time with user-defined properties.
You can also view and update the configurable properties for the individual message flow nodes. The properties that are available to update depend on the nodes within the message flow; some nodes have no configurable properties to display. The node properties that are configurable are predominantly system-related properties that are likely to change for each integration node to which the message flow is deployed. These properties include data source names and the names of WebSphere® MQ queues and queue managers. For full details of configurable properties for a node, see Configurable properties of message flow nodes.
On the Configure tab, you can set the following properties:
This property specifies the consumer policy to use to authenticate, encrypt, and sign messages for the SOAPRequest, SOAPAsyncRequest, and SOAPAsyncResponse nodes.
This property associates a policy set binding with a consumer policy set and contains information that is specific to the environment and operating system, such as information about keys.
This property controls whether the message flow is processed as an XA coordinated transaction that is coordinated by WebSphere MQ. Such a message flow is said to be fully XA coordinated. By default the Coordinated Transaction check box is not selected.
Use coordinated transactions only where you need to process the message, and any database updates that are performed by the message flow in a single unit-of-work, by using a two-phase commit protocol. In this case, both the message is read and the database updates are performed, or neither action is done.
If you change this value, ensure that the queue manager for the integration node is configured correctly. If you do not set up the queue manager correctly, the integration node generates a message when the message flow receives a message to indicate that, although the message flow is to be XA coordinated, the queue manager configuration does not support coordination.
See IBM® Integration Bus system requirements for information about
which databases are supported as participants in an XA coordinated
transaction, and the System Administration section of
the
WebSphere MQ Version 8.0 product documentation online for how to
configure WebSphere MQ and the database
managers.
This property has no effect if the message flow does not process WebSphere MQ messages.
This property specifies the name of the monitoring profile configurable service to apply to one or more message flows in a BAR file. The monitoring profile is used to configure your message flows to emit monitoring events.
For more information, see Configuring monitoring event sources by using a monitoring profile.
This property specifies the provider policy to use to authenticate, encrypt, and sign messages for the SOAPInput and SOAPReply nodes.
This property associates a policy set binding with a provider policy set and contains information that is specific to the environment and operating system, such as information about keys.
This property specifies a security profile that has authorization enabled so that a message flow can complete authorization with Tivoli® Federated Identity Manager (TFIM). You can set a security profile on a message flow or on individual input nodes. If no security profile is set for the input nodes, the setting is inherited from the setting on the message flow.
For more information, see Configuring authorization with TFIM V6.1.