WebLogic Server provides a transaction service that allows J2EE applications to manage their own transaction boundaries. WebLogic’s transaction service supports multithreaded clients — i.e., a client can make concurrent requests for transactions in multiple threads. WebLogic Server implements flat transactions, which means that multiple transactions cannot be associated with the same thread at the same time. WebLogic supports distributed transactions that may span multiple WebLogic servers, clusters, and even domains.
The EJB container uses WebLogic’s transaction
service to coordinate transactions across EJB components. EJBs that
support bean-managed transactions and J2EE applications both use the
JTA to explicitly manage their own transactions. J2EE clients can
TransactionManager objects from the JNDI tree and
use these interfaces to demarcate their transaction boundaries. This
allows lightweight clients to begin and commit transactions, and
delegate the actual responsibility of coordinating the transaction to
the remote transaction manager running on WebLogic
The JTA defines the contract between the transaction manager and all resources involved in a distributed transaction — i.e., the application, the application server, and the resource manager. It allows you to coordinate updates to multiple resources in a safe, elegant way, regardless of the transaction manager. The transaction manager ...