Transaction Management of Adapter Connections
When you define a connection, the transaction type you choose determines the type of transaction management that the connection's operations will use. The
Tuxedo Adapter supports transactional connection types. For a detailed discussion of transaction management and the
Tuxedo Adapter, see
Transaction Management Overview.
A transactional connection uses syncpoint processing, which means that you can group one or more requests into a single Logical Unit of Work (LUW). You can control these requests manually (explicit transactions), or you can allow the Integration Server's transaction manager control them for you (implicit transactions).
To control these requests explicitly within a given LUW, you use the built-in services described in
Built-In Transaction Management
Services. If you do not use these built-in services, the
Integration Server will manage the requests automatically (implicitly).
If a transaction uses only a single connection, or multiple connections that are all from the same connection pool, you do not need to manage the transaction explicitly. However, if a transaction uses multiple LOCAL_TRANSACTION transaction connections from different connection pools, you must manage the transaction explicitly.
Note:
Implicit transactions complete when the flow service that contains the LUW finishes execution. If you create a looping operation within your LUW that could potentially involve a large number of requests, consider managing the transactions explicitly to reduce the possibility that you will need to roll back a large number of requests because a single request fails.