With implicit transactions, the Integration Server automatically manages local transactions without requiring you to explicitly do anything. That is, the Integration Server starts and completes an implicit transaction with no additional service calls required by the adapter user.

A transaction context, which the transaction manager uses to define a unit of work, starts when a flow service executes an adapter service. The connection required by the adapter service is registered with the newly created context and used by the adapter service. If the flow executes another adapter service, the transaction context is searched to see if the connection is registered already. If the connection is already registered, the adapter service uses this connection. If the connection is not registered, the Integration Server retrieves a new connection instance and registers it with the transaction.

Note that if the top level flow invokes another flow, adapter services in the child flow use the same transaction context.

When the top level flow completes, the transaction completes and either is committed or rolled back, depending on the status (success or failure) of the top level flow.

A single transaction context can contain no more than one Tuxedo Adapter Connection. If your flow contains adapter services that use more than one Tuxedo Adapter Connection, you must use explicit transactions, which are described in the next section.

For more information about designing and using flows, see the webMethods Service Development Help for your release.

For more information about transaction types, see Transaction Management of Adapter Connections.