Client support for transactions

This page describes the support of application clients for the use of transactions.

data source directly in the client process. In such cases, any work performed through the JDBC provider is not coordinated as part of the global transaction. Instead, the work runs under a resource manager local transaction. The client container process is non-recoverable and contains no transaction coordinator with which a resource manager can be enlisted.

A client can begin a transaction, then call a remote application component such as an enterprise bean. In such cases, the client-initiated transaction context is implicitly propagated to the remote appserver, where a transaction coordinator is created. Any resource managers accessed on the recoverable appserver (or any other appserver hosting application components invoked by the client) are enlisted in the global transaction.

Client application components must be aware that locally-accessed resource managers are not coordinated by client-initiated transactions. Client applications acknowledge this through a deployment option that enables access to the UserTransaction interface in the client container. By default, access to the UserTransaction interface in the client container is not enabled. To enable UserTransaction demarcation for an application client component, set the Allow JTA Demarcation extension property in the client deployment descriptor. For information about editing the client deployment descriptor, refer to the Rational Application Developer information.

---

 

Related concepts

Transaction support in WAS

 

Related information

Rational Application Developer documentation