Which optional component is required to enable global transaction support?

Question

Options

• ACICS
• BIBM MQ
• CIBM TXSeries
• DThird-party transaction manager

• A
  9% (2)
• B
  83% (19)
• C
  4% (1)
• D
  4% (1)

Explanation

On distributed platforms, the default behavior of the integration node is to manage all message flow transactions by using local transactions (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 integration node with a local WebSphere MQ queue manager to manage the message flow transactions as globally coordinated (a two-phase commit approach), by using the XA protocol standard. To globally coordinate transactions, there must be a queue manager specified on the integration node, and that queue manager performs the transaction manager role. The queue manager that is specified on the integration node is used as a globally coordinated resource. Other queue managers cannot participate in the message flow transaction.

No community discussion yet for this question.