Transaction Type | Description |
XA_TRANSACTION | This transaction type allows the connection to support two-phase transactions executed across multiple resources. In one transaction boundary, all of the operations on multiple connections will be committed or rolled back together. A transaction boundary means the scope of the transaction, from the beginning to the end of a transaction. It can be in one adapter service, one flow service, one Java service, or several steps in a flow service. The following JMS providers do not support the XA_TRANSACTION transaction type: webMethods Broker 8.2 SP2, 9.0 SP1 and 9.5 SP1 when used as a JMS provider BEA WebLogic 10.3.1.0 JMS provider Note: All of the connections involved in a two-phase transaction must support the XA_TRANSACTION transaction type. Note: You cannot use connections that use the XA_TRANSACTION transaction type with notifications. |
NO_TRANSACTION | When receiving messages, the connection automatically acknowledges the received message. (Sessions are created with the CLIENT_ACKNOWLEDGE acknowledge mode.) When sending messages, the message is automatically delivered. For instructions on managing transactions manually, see
Built-In Transaction Management
Services. |
LOCAL_TRANSACTION | The connection does not automatically commit transactions. You can manually define the transactions, or the Integration Server transaction manager will manage it for you. For instructions on managing transactions manually, see
Built-In Transaction Management
Services. |