Configuring databases for coordinated message flows

If your message flow interacts with a database, and you want to coordinate the updates made to the database with other actions within the message flow, configure your broker to manage these updates.

Before you start:

To complete this task, you must have completed the following task:

  1. Update the broker queue manager information by defining an XAResourceManager stanza for each of the databases that will participate in globally coordinated transactions when updated by message flows on that broker.
    • On Linux and UNIX, add an XAResourceManager: stanza to the broker queue manager's initialization file qm.ini. The content of this stanza is database specific; see the instructions in the sections that follow.
    • On Windows, define the XAResourceManager using WebSphere MQ Services. Click the queue manager name in the left pane and select Properties from the menu. In the Resources tab of the Properties dialog, enter the values indicated in the following sections.
    • On z/OS, you do not have to take any specific action, but RRS must be available.
  2. If your message flows reference message dictionaries, or contain Publication nodes, you must also define an XAResourceManager stanza for the broker internal database using the same method.

64 bit or 32 bit coordination

The database drivers that are needed for XA coordination will depend on the version of WebSphere MQ that you will be using to perform transaction management. If you are going to use WebSphere MQ V5.3 then you can only perform XA coordination in 32 bit mode and so you must choose and configure the 32 bit drivers in both your qm.ini and ODBCINI files. If you are going to use WebSphere MQ V6 then the XA coordination must be performed in 64 bit mode and you should choose and configure the 64 bit drivers in you qm.ini and ODBCINI64 files.

Related concepts
Message flows overview