Administration Console Online Help

Create a JDBC Data Source

Use this page to create a JDBC data source. A JDBC 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.

Select the database management system of your database. The
Administration Console tailors the list of known JDBC drivers to the
DBMS you select and constructs connection properties in a format that
the DBMS supports.

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.

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.

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.

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.

The list of properties passed to the JDBC driver that are used to
create physical database connections. For example: server=dbserver1.
List each property=value pair on a separate line.

To enable driver-level features, add the driver property and its
value to the Properties list. WebLogic Server sets driver-level
properties in the Properties list on the driver's
ConnectionPoolDataSource object.

Note:

For security reasons, when WebLogic Server is running in
Production mode, you cannot specify database passwords in this
properties list. Data source deployment will fail if a password is
specified in the properties list. To override this security check,
use the command line argument
"weblogic.management.allowClearTextPasswords" when starting the
server.

The name of the database table to use when testing physical
database connections. This name is required when you specify a Test
Frequency and enable Test Reserved Connections.

The default SQL code used to test a connection is "select
count(*) from TestTableName"

Most database servers optimize this SQL to avoid a table scan,
but it is still a good idea to set the Test Table Name to the name
of a table that is known to have few rows, or even no rows.

If the Test Table Name begins with "SQL ", then the
rest of the string following that leading token will be taken as a
literal SQL statement that will be used to test connections instead
of the standard query. For example: SQL BEGIN; Null; END;