Before you start:
Read Message flow transactions to understand how the broker handles transactions. Depending on the external resource managers that the broker accesses during the processing of its deployed message flows, you must complete the appropriate resource-dependent set of tasks to ensure that all resources are configured correctly. For example, you might have to create and configure databases.
You, or your message flow developer, must also ensure that the message flows deployed to the broker are set up to support coordination. The tasks involved in configuring the message flows correctly are described in Configuring transactionality for message flows.
You can access the following external resources in a message flow transaction:
- WebSphere MQ queues and messages
- Databases
- JMS providers
On distributed platforms, the default behavior of the broker is to manage all message flow transactions by using a one-phase commit approach. In many contexts this approach is sufficient, but if your business requires assured data integrity and consistency (for example, for audit reasons, or for financial transactions), you can configure the broker and its WebSphere MQ queue manager to manage the message flow transactions in a two-stage commit approach, by using the XA protocol standard.
You configure the WebSphere MQ queue manager by updating its qm.ini file, to add definitions of the additional resource managers with which you want WebSphere MQ to coordinate updates. Follow the instructions provided for the resource managers that are relevant in your environment:
On z/OS®,
all transactions are globally coordinated by Resource Recovery Service
(RRS), therefore the instructions in this topic do not apply. However,
you must ensure that RRS is available; see Resource Recovery Service planning on z/OS.
You must complete all the steps correctly; if you do not, global coordination will not work.
You can view information about samples only when you use the product documentation that is integrated with the IBM® Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.
Last updated Friday, 21 July 2017