WebSphere Message Brokers
File: ac28600_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:19:52

Configuring JMSInput and JMSOutput nodes to support global transactions

If you require additional configuration to enable global transaction support for the JMSInput and JMSOutput node, you must complete the following steps:

  1. Set the Message Flow property Coordinated Transaction to yes in the bar file properties.
  2. For each JMSInput or JMSOutput node required in the global transaction, set the Advanced property Transaction Mode to Global in the message flow editor.
  3. Create a Queue Connection Factory and supply either a default name, recoverXAQCF or supply a user defined name. See JMSInput or JMSOutput node for further details on creating JNDI administered objects.
  4. On platforms other than z/OS, you must set up a stanza for each JMS provider that you want to use, prior to deployment. Select the appropriate link for details of this task on the platform, or platforms, that your enterprise uses:
    For further information, see:

    On WebSphere Message Broker for z/OS, the only JMS provider supported is the IBM WebSphere MQ Java Client and the only transport mode supported for that client is BIND mode; no further configuration steps are required.

The JMS provider might supply additional jar files that are required for transactional support; see the documentation supplied with the JMS provider for more information. For example, on platforms other than z/OS, the WebSphere MQ JMS provider supplies an extra jar file com.ibm,mqetclient.jar.

You must add any additional jar files to the broker shared_classes directory. On Windows, this directory is C:\Documents and Settings\All Users\Application Data\IBM\MQSI\shared-classes. For more information, see the section on making the JMS provider client available to the JMS Nodes in JMSInput node.

Choice of JMS Provider

Any JMS provider that conforms to the Java Message Service Specification, version 1.1 and that supports the JMS XAResource API through the JMS session can be used if transaction coordination is required.

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 JMSInput and JMSOutput nodes.

Related concepts
JMS Transactionality
Related reference
JMSInput node
JMSOutput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:19:52

ac28600_ This topic's URL is: