If you require additional configuration to enable global transaction support for the JMSInput and JMSOutput node, you must complete the following steps:
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.