Configuring JMSInput and JMSOutput nodes to support global transactions

If you want to include JMSInput and JMSOutput nodes in globally-coordinated transactions, additional configuration is required.

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 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.

To configure JMSInput and JMSOutput nodes:

  1. Switch to the Broker Application Development perspective.
  2. Set the message flow property Coordinated Transaction to yes in the BAR file properties.
  3. For each JMSInput or JMSOutput node required in the global transaction, set the Advanced property Transaction mode to Global in the message flow editor.
  4. Create a Queue Connection Factory and either use the default name, recoverXAQCF , or supply your own name. See the JMSInput or JMSOutput node for further details about creating JNDI administered objects.
  5. On distributed systems, you must set up a stanza for each JMSProvider that you want to use, prior to deployment.

    The following table shows the JMSProvider switch files that are provided on each platform.

    Start of change
    Platform 32-bit file 64-bit file

    AIX®

    libJMSSwitch.so libJMSSwitch64.so

    HP-UX on Itanium

      libJMSSwitch.so

    HP-UX on PA-RISC

    libJMSSwitch.sl libJMSSwitch64.sl

    Linux® on POWER™

    libJMSSwitch.so  

    Linux on System z®

    libJMSSwitch.so  

    Linux on x86

    libJMSSwitch.so  

    Linux on
    x86-64

    libJMSSwitch.so  

    Solaris on SPARC

    libJMSSwitch.so libJMSSwitch64.so

    Solaris
    on x86-64

    libJMSSwitch.so  

    Windows®

    JMSSwitch.dll  
    End of change

    Select the appropriate link for details of this task on the platform, or platforms, that your enterprise uses:

    For further information, see:

    z/OS platform On z/OS®, the only JMSProvider 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 distributed systems, 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:

For more information, see the section on making the JMS provider client available to the JMS nodes in JMSInput node.

Related concepts
JMS Transactionality
Related tasks
Linux and UNIX systems: configuring the queue manager to coordinate JMS resources
Windows systems: configuring the queue manager to coordinate JMS resources
Windows systems: modifying the queue manager authorization
Related reference
JMSInput node
JMSOutput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:39:58

ac28600_