Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Overview of webMethods Adapter for Enterprise JavaBeans | Adapter Connections | Transaction Management of Adapter for Enterprise Javabeans Connections
 
Transaction Management of Adapter for Enterprise Javabeans Connections
Adapter for Enterprise Javabeans connections support the following transaction types:
Transaction Type
Description
Non-transactional
Used by the EJB Non-transactional Connection connection template. The connection provides no transaction control over the operations being performed. Once completed, an operation cannot be reversed. That is, the connection automatically commits (Auto Commit) all operations.
Local
Used by the EJB Local Connection connection template. With this transaction type, all of the operations on the same connection in one transaction boundary 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.
For all supported versions of all supported application servers, Integration Server transaction manager can accommodate any number of adapter services using local transaction connections in a single flow.
XA
Used by the EJB XA Connection connection template.This transaction type allows the connection to participate in two-phase transactions executed across multiple distributed 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.
When you configure a connection, the connection template you choose determines the type of transaction management that the connection's operations use implicitly. Implicit transactions are managed by Integration Server's transaction manager. For more information about implicit transactions, Implicit and Explicit Transactions.
You can also explicitly manage transactions using built-in services. See Overview for information about explicitly managing transactions.