About this task
Before you deploy a message flow in which the Transaction mode property is
set to Global or Yes, and is intended to use XA coordinated
transactions, modify the queue manager .ini file
to include extra definitions for each JMS provider resource manager
that participates in globally coordinated transactions.
To
configure the queue manager for Windows:
What to do next
- Check your configuration:
- In the message flow, ensure that the coordinated property
is enabled by using the IBM® Integration Bus Archive
editor.
- Ensure that each node that must be part of the XA transaction
is set to the global transaction mode.
- Ensure that the service ID that is used for the integration node
and the queue manager is the same user ID.
- Ensure that the JNDI connection factory objects that the JMS nodes
use for a global transaction are configured to be of the type
MQXAConnectionFactory, MQXAQueueConnectionFactory, or MQXATopicConnectionFactory.
- If you create the bindings by using JMSAdmin, use the command
DEF XAQCF or DEF XATCF,
instead of DEF QCF or DEF TCF,
when you define your connection factory.
- Authorize the integration node and queue manager to access
shared resources that are associated with the JMS provider; see Windows systems: modifying the queue manager authorization.
For more information, see
Transactional support in the
WebSphere MQ Version 7.5 product documentation online.
Troubleshooting
IBM Integration Bus examines
the
WebSphere MQ registry to determine
if the queue manager is XA enabled. If
IBM Integration Bus is unable to locate the location
of the queue managers working directory, an error is issued at startup.
You can specify this location by setting the following environment
variable in the
mqsiprofile script:
MQ_DATA_PATH For
example:
MQ_DATA_PATH="C:\Program Files (x86)\IBM\WebSphere MQ"