Domain Application Deployment: Administration: Transactions
The transaction protocol for a JDBC data source determines how connections from the data source are handled during transaction processing. Transactions within a JDBC data source are either global (XA) or non-global (local).
This page enables you to define transaction options for this JDBC data source.
Name Description Supports Global Transactions
Select this option to enable non-XA connections from the data source to participate in global transactions.
In most cases, if your application includes global transactions, you should use an XA JDBC driver to create database connections. You may need to enable this option for use with EJBs. If you enable support for global transactions with a non-XA JDBC driver, you must select an option for transaction processing.
MBean Attribute (Does not apply to application modules) :
Logging Last Resource
Enables a non-XA JDBC connection to participate in distributed transactions using the Logging Last Resource (LLR) transaction optimization. Recommended in place of Emulate Two-Phase Commit.
With this option, the transaction branch in which the connection is used is processed as the last resource in the transaction and is processed as a one-phase commit operation. The result of the operation is written in a log file on the resource itself, and the result determines the success or failure of the prepare phase of the transaction. This option offers some performance benefits with greater data safety than Emulate Two-Phase Commit.
Emulate Two-Phase Commit
Enables a non-XA JDBC connection to emulate participation in distributed transactions using JTA. Select this option only if your application can tolerate heuristic conditions.
With this option, the transaction branch in which the connection is used always returns success for the prepare phase of the transaction. This option offers performance benefits, but also has risks to data in some failure conditions.
Enables a non-XA JDBC connection to participate in distributed transactions using the one-phase commit transaction processing. With this option, no other resources can participate in the global transaction.