Configuring ODBC connections for globally coordinated transactions

Configure the definition of your ODBC databases to the transaction manager (the queue manager).

Before you begin

You must create and configure the databases by following the instructions in Working with databases.

You, or your message flow developer, must also ensure that the message flows deployed to the integration node are set up to support coordination. The tasks that are involved in configuring the message flows correctly are described in Configuring transactionality for message flows.

On distributed systems, a WebSphere® MQ queue manager associated with the integration node performs the transaction manager role, which means that IBM® Integration Bus requires access to WebSphere MQ when processing messages. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.

On z/OS®, transactions are always globally coordinated; you do not have to choose or configure for this option.

Procedure

  1. Ensure that your databases are configured for global coordination.
    For the databases that your message flows connect to, complete the tasks that are described in Configuring databases for global coordination of transactions.
  2. Configure the integration node environment so that the integration node queue manager coordinates transactions with database resource managers.
    The steps to configure the integration node environment depend on the database manager that you are using.

Results

When you have completed these steps, your message flows are processed by using global coordination, which is managed by the queue manager.

You must complete all the steps correctly; if you do not, global coordination will not work.