Using the WebLogic JTA Driver

The WebLogic JTA driver provides a full distributed transaction implementation of the DataSource interface. The JTA driver also supports connection pooling. To enhance performance, the WebLogic JTA driver uses standard SQL commands to the database when the scope of the transaction is limited to a single DataSource .

To provide all the ACID properties between WebLogic Server and the database server, the transaction services provided by the JTA driver require that all resources involved in the transaction are XA-compliant. When multiple DataSource s are involved in the transaction, the JTA driver uses a Two-Phase Commit (2PC) engine. Finally, distributed transactions introduce race conditions and concurrency issues that must be dealt with. This refers to the Isolation property of ACID. For example, two separate transactions might try to update the same data at the same time. JDBC specifies Transaction Isolation Levels that allow you to control how the database behaves in these situations. Each of these topics were introduced in the preceding sections.