WebSphere MQ Adapter 6.5 | webMethods WebSphere MQ Adapter Documentation | webMethods WebSphere MQ Adapter Installation and User’s Guide Documentation | About the WebSphere MQ Adapter | Adapter Connections | Transaction Management of WebSphere MQ Adapter Connections
Transaction Management of WebSphere MQ 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. WebSphere MQ Adapter connections support the following transaction types. For a detailed discussion of transaction management and WebSphere MQ Adapter, see Transaction Management Overview.
Transaction Type
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 Integration Server 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.
Implicit transactions complete when the flow service that contains the LUW finishes executing. If you create a looping operation within your LUW that could potentially involve a large number of requests, you might want to manage the transactions explicitly to reduce the possibility that you will need to roll back a large number of requests because a single request fails.
A non-transactional connection is stateless and does not use syncpoint processing. All services associated with a non-transactional connection perform a single request as an autonomous unit of work.
For example, when a flow invokes a Get service associated with a non-transactional connection, then these services remove each message from the WebSphere MQ immediately after they processes the message.