Tuxedo Adapter 6.0 | webMethods Tuxedo Adapter Documentation | webMethods Tuxedo Adapter Installation and User’s Documentation | Built-In Transaction Management Services | Transaction Management Overview | Transaction Types
 
Transaction Types
The Tuxedo Adapter supports local transactions with the Jolt server. For a description of the transaction types supported by the Tuxedo Adapter, see Transaction Management of Adapter Connections.
In general, the Tuxedo Adapter can communicate with multiple Jolt servers (resources) at a time. There are limitations when the adapter tries to access multiple resources using locally transacted connections within a single flow service. Also, the Jolt server can impose its own set of restrictions on how a connection may be used in a transaction.
Note:
If a transaction accesses multiple resources, and more than one of the resources only supports only local transactions, the integrity of the transaction cannot be guaranteed. For example, if the first resource successfully commits, and the second resource fails to commit, the first resource interaction cannot be rolled back; it has already been committed. To help prevent this problem, the Integration Server detects this case when connecting to more than one resource that does not support two-phase commits. It throws a run-time exception and the service execution fails.