Create a JDBC GridLink Data Source: Transaction Properties
Use this page to create a JDBC GridLink data source. A JDBC GridLink data source is an object bound to the JNDI tree that provides database connectivity through a pool of JDBC connections. Applications can look up a data source on the JNDI tree and then reserve a database connection from a data source.
Name Description Supports Global Transactions
Select this option if database connections from this data source will be used in global transactions.
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.
Select this option if you want to enable non-XA JDBC connections from the data source to participate in global transactions using the one-phase commit transaction processing. With this option, no other resources can participate in the global transaction.
Emulate Two-Phase Commit
Select this option if you want to enable non-XA JDBC connections from the data source to emulate participation in global 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.
Logging Last Resource
Select this option if you want to enable non-XA JDBC connections from the data source to participate in global transactions using the Logging Last Resource (LLR) transaction optimization. This option is 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.
This option is automatically selected if you select an XA JDBC driver. With this option, database connections from the data source fully participate in global transactions. The WebLogic Server transaction manager enforces the two-phase commit protocol.