webMethods Broker used as a JMS provider is a Java Transaction API (JTA) capable provider. webMethods Broker used as a JMS provider supports the JTA XAResource API as described in the Java Message Service (JMS) standard. JTA support enables webMethods Broker to participate in distributed transactions. For more information about JTA support for a webMethods Broker client-side clustering environment, see JTA /XA Support in a JMS Clustered Environment.

webMethods Broker used as a JMS provider is not a distributed transaction manager but relies on the transaction managers that the supported application servers provide. webMethods Broker supports distributed transactions on supported application servers, although it does not support distributed transactions for standalone JMS messaging solutions.

webMethods Broker used as a JMS provider supports the transactional connection factories XAConnectionFactory, XAQueueConnectionFactory and XATopicConnectionFactory to create connections to administered objects that will be managed by the application server's distributed transaction coordinator in distributed transactions. Messages created from these objects can be grouped into distributed transactions with other resources.

Local or one-phase-commit transactions can be handled in standalone messaging applications within the context of a single session. These transactions are not based on XA resources nor are they handled at the administrative level. For more information, see Implementing a Local Transaction.