Configuring JMS and SOAP nodes to support globally coordinated transactions

To include nodes that use JMS transport, such as the JMS and SOAP nodes, in globally coordinated transactions, you must complete additional configuration.

1. In the IBM Integration Toolkit, switch to the Integration Development perspective.
2. In the BAR file properties, set the Coordinated Transaction message flow property value to yes.
3. In the Message Flow editor, set the Transaction mode property to Yes for each node that uses JMS transport that is required in the XA coordinated transaction.
4. Create a Queue Connection Factory, and use either the default name, recoverXAQCF, or supply your own name.
   For more information about creating JNDI administered objects, see JNDI administered objects.
5. There are two modes for enlisting an XAResource with the transaction coordinator:
   1. Static enlistment, which means that the XAResource is called to perform a start transaction when any message flow in the same Integration Bus starts a global coordinated transaction.
   2. Dynamic enlistment where the JMS node registers an interest in joining a global transaction when it has work to perform.

   Before deployment on distributed systems, you must set up a stanza for each JMS provider that you want to use. For Windows, the JMS provider switch file is called DynJMSSwitch.dll. For all other operating systems, the JMS provider switch file is called libDynJMSSwitch.so.

   Follow the steps in the appropriate topic for the operating system, or systems, that your enterprise uses:

   • Linux® and UNIX systems
   • Windows systems

     On Windows only, you must also modify the queue manager authorization, as described in Windows systems: modifying the queue manager authorization.

   • On z/OS, the only JMS provider that is supported is the IBM WebSphere MQ Java Client, and the only transport mode that is supported for that client is BIND mode; no further configuration steps are required. Sync point control for the JMS provider is managed with RRS sync point coordination of the queue manager of the integration node.

   Note: From IBM Integration Bus Version 9.0.0.6, JMS XA registration is performed using the dynamic XA call sequence using switch files containing the identified "Dyn" for example DynJMSSwitch.dll. In order to provide compatibility with existing installations, switch files with the previous names have been provided but these are copies of the dynamic registration switch file. The version of the switch file used by the QueueManager must match the version being used by the integration node. The use of mismatched switch files is not supported and is likely to cause mixed results when processing XA JMS transactions.