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