Adapter Development Kit 9.12 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Integration Server Transaction Support | Overview
 
Overview
This section describes how Integration Server supports transactions. Integration Server considers a transaction to be one or more interactions with one or more resources that are treated as a single logical unit of work. The interactions within a transaction are either all committed or all rolled back. For example, if a transaction includes multiple database inserts, and one or more inserts fail, all inserts are rolled back.
Integration Server supports the following types of transactions:
*Local Transaction. Transaction to a resource's local transaction mechanism.
*XAResource Transaction. Transaction to a resource's XAResource transaction mechanism.
Integration Server can manage both types of transactions, without requiring the adapter users' input.
*Integration Server uses a container-managed (implicit) transaction management approach based on the JCA standard.
*Integration Server performs additional connection management. This is because the adapter services use connections to create transactions.
For more information about implicit transactions, see Implicit Transaction Usage Cases. However, there are cases where adapter users need to explicitly control the transactional units of work. For more information about explicit transactions, see Explicit Transaction Usage Cases.
Integration Server relies on a built-in transaction manager to support transactions. The transaction manager is responsible for the following:
*Beginning and ending transactions.
*Maintaining a transaction context.
*Enlisting newly connected resources into existing transactions.
*Ensuring that local and XAResource transactions are not combined in invalid ways.
*Manages operations performed by a transacted JMS trigger, or a built-in JMS service that uses a transacted JMS connection alias.
Important:
You cannot create steps and trace a flow that contains a transacted adapter service.
Note:
If you interact with a resource that does not support transactions, Integration Server does not create a transaction for it.
For more information about specifying the type(s) of transactions to support in your adapter, see Specifying Transaction Support in Connections.