WebSphere Message Brokers
File: ae83280_
Writer: Laura Cowen

Task topic

This build: July 31, 2007 21:29:12

Configuring global coordination of transactions (two-phase commit)

To ensure data integrity during transactions, globally coordinate message flow transactions with a WebSphere MQ queue manager.

Before you start:

You must have completed the following tasks:

On distributed platforms (UNIX®, Linux (x86 platform), and Windows®), by default the broker manages all message flow transactions using a one-phase commit approach. In many contexts this is sufficient, but if your business requires assured data integrity (for example, for audit reasons or for financial transactions), configure your system so the broker's WebSphere MQ queue manager manages the message flow transactions in a two-stage commit approach using the XA protocol standard. For more information about global coordination of transactions, refer to the Transactional model in the Related links.

z/OS platform On z/OS®, all transactions are globally coordinated by Resource Recovery Service (RRS) so the following instructions are not relevant. RRS must, however, be available. For more information about RRS planning on z/OS refer to the Related links.

To configure your system for global coordination of transactions:

  1. Ensure that the databases are configured for global coordination. For information on how to perform this configuration refer to the Related links.
  2. Configure the broker environment so that the broker's queue manager coordinates transactions. The steps to configure the broker environment depend on the database manager that you are using and whether the broker's queue manager and the execution group are 32-bit or 64-bit.

    If you are using shared memory to connect directly to a 64-bit database instance, you must use a 64-bit queue manager to globally coordinate transactions (all WebSphere MQ Version 6 queue managers on 64-bit platforms are 64-bit). A 32-bit queue manager cannot connect directly to a 64-bit database instance.

  3. Configure the message flow for global coordination. For information on how to perform this configuration refer to the Related links.
When you have completed all of the steps, your message flows are processed using global coordination, which is managed by the queue manager.

You must complete all of the steps correctly; otherwise, global coordination will not work.

For an example of how you can use WebSphere MQ to globally coordinate transactions, look at the following sample: You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
Related concepts
The Transactional model
Related tasks
Configuring globally coordinated message flows
Configuring databases for global coordination of transactions
Resource Recovery Service planning on z/OS
Enabling connections to the databases
Creating a broker
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:12

ae83280_ This topic's URL is: