See information about the latest product version
Configuring JMS and SOAP nodes to support XA coordinated transactions
To include nodes that use JMS transport, such as the JMS and SOAP nodes, in XA coordinated transactions, you must complete additional configuration.
If you require transaction coordination, choose a JMS provider that conforms to the Java™ Message Service Specification, version 1.1 and that supports the JMS XAResource API through the JMS session.
If you specify your own JMS provider using the JMSProviders configurable service, set the jmsProviderXASupport attribute to true to indicate that the selected JMS provider supports XA coordinated transactions. If you set this property to true, and the selected JMS provider does not support XA transactions, an exception is raised. If you set this property to false, but the Transaction mode property on the node is set to Yes and the Coordinated Transaction message flow property is selected, an exception is raised.
If the message designer has specified a non-XA-compliant provider, the non-transactional mode only is supported. In this case, you must set the Transaction mode property to None for all JMS and SOAP nodes that use JMS transport.
To configure the nodes:
You must add any additional JAR files to the broker shared_classes directory:
On Linux and UNIX: var/mqsi/shared-classes.
On Windows, %ALLUSERSPROFILE%\Application Data\IBM\MQSI\shared-classes, where %ALLUSERSPROFILE% is the environment variable that defines the system working directory. The default directory depends on the operating system.
- On Windows XP and Windows Server 2003: C:\Documents and Settings\All Users\IBM\MQSI\shared-classes
- On Windows Server 2008: C:\ProgramData\IBM\MQSI\shared-classes
For more information, see the section about making the JMS provider client available to the JMS nodes in JMSInput node.
Optional: To secure the JMS connection factory, the JNDI bindings, or both, see Securing JMS connections and JNDI lookups.