IBM Integration Bus, Version 10.0.0.1 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Configuring MQ nodes for transactions

When you define an MQInput, MQGet, MQOutput, or MQReply node, the options that you select for the properties define behavior for the transaction.

Before you begin

Review Configuring transactionality for message flows to understand what configuration is required for transactionality.

About this task

You can use WebSphere® MQ resources in either local or globally coordinated transactions:
If a connection to a queue manager is lost, and that connection is enlisted in a transaction, automatic reconnection is delayed until the inflight transaction is complete. Other queue managers that are required, but are not part of the transaction, reconnect automatically without delay. A completed transaction can include the following cases:
  • The unavailable MQ resource was not required and was not used, because exception handling was defined in the message flow, so the inflight transaction was successful and committed.
  • The unavailable MQ resource was required, and the message flow cannot succeed without it, so the inflight transaction was rolled back.

Review how to set the properties for MQ nodes to determine how they participate in transactions.

Configuring transactions for MQInput and MQGet nodes

Procedure

Configuring transactions for MQOutput and MQReply nodes

Procedure

The option that you select for the Transaction Mode property defines whether the message is written under sync point:
  • If you set the property to Automatic, the node participates in a transaction. If there is no inflight transaction, processed messages are committed immediately.
  • If you set the property to Yes, the node participates in the transaction currently inflight. If there is no transaction, then a new transaction is started for this node, and all other nodes that are connected to its output terminal.
  • If you set the property to No, an inflight message is immediately committed.

What to do next

To use MQ nodes in global transactions, follow the steps in Configuring global coordination of transactions (two-phase commit).

To understand when you might want to use a globally coordinated transaction for your message flow, see the Coordinating transactions section in the topic Message flow transactions.


ac04561_.htm | Last updated 2015-05-28 20:49:47