Transaction Types
Integration Server supports the following kinds of transactions:
A
local transaction (LOCAL_TRANSACTION), which is a transaction to a resource’s local transaction mechanism
An
XAResource transaction (XA_TRANSACTION), which is a transaction to a resource’s XAResource transaction mechanism
Integration Server can automatically manage both kinds of transactions without requiring the user to do anything. For more information about implicit transactions, see
Implicit and Explicit Transactions.
However, in some cases, users need to explicitly control the transactional units of work. Examples of these cases are provided in
Implicit and Explicit Transactions.
To support transactions, Integration Server relies on a built-in Java EE transaction manager. The transaction manager is responsible for beginning and ending transactions, maintaining a transaction context, enlisting newly connected resources into existing transactions, and ensuring that local and XAResource transactions are not combined in illegal ways.
The transaction manager only manages operations performed by adapter services, a transacted JMS trigger, or a built-in JMS service that uses a transacted JMS connection alias.
Important:
You cannot step or trace a flow that contains a transacted adapter service or a transacted JMS service.