Transaction Type | Description |
NO_TRANSACTION | The connection provides no transaction control over the operations being performed. That is, the connection automatically commits (Auto Commit) all operations. |
LOCAL_TRANSACTION | With this transaction type, all of the operations on the same connection in one transaction boundary are 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. |
XA_TRANSACTION | This transaction type allows the connection to support two-phase transactions executed across multiple databases. In one transaction boundary, all of the operations on multiple connections are 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. Note: All of the connections involved in a two-phase transaction must support the XA_TRANSACTION transaction type. |