Technical data

16 Managing JDBC Connectivity
16-8 Administration Guide
The following table describes how to use these objects in local and distributed
transactions:
Note: For distributed transactions, use an XA-compliant driver, such as the
WebLogic jDriver for Oracle/XA, which is the XA compliant version of the
WebLogic jDriver for Oracle.
When to Use a Tx Data Source
If your applications or environment meet any of the following criteria, you should use
a Tx Data Source instead of a Data Source:
Table 16-1 Summary of JDBC Configuration Guidelines
Descriptio
n/Object
Local Transactions Distributed
Transactions
XA Driver
Distributed
Transactions
Non-XA Driver
JDBC driver n WebLogic jDriver
for Oracle, Microsoft
SQL Server, and
Informix.
n Compliant
third-party drivers.
n WebLogic
jDriver for
Oracle/XA.
n Compliant
third-party
drivers.
n WebLogic jDriver for
Oracle, Microsoft
SQL Server, and
Informix.
n Compliant third-party
drivers.
Data Source Data Source object
recommended. (If there is
no Data Source, use the
JDBC API.)
Tx Data Source
required.
Tx Data Source required.
Set
enable two-phase
commit=true
if more
than one resource. See
“Configuring Non-XA
JDBC Drivers for
Distributed Transactions”
on page 16-20.
Connection
Pool
Requires Data Source
object when configuring
in the Administration
Console.
Requires TXData
Source.
Requires TXData Source.
MultiPool Connection Pool and
Data Source required.
Requires TXData
Source.
Requires TXData Source.