On the Summary
of Data Sources page, click New and select
GridLink Data Source.

On the
JDBC Data Sources Properties page, enter or select the
following information:

Name - Enter a
name for this JDBC GridLink data source. This name is used in the
configuration file (config.xml) and throughout
the Administration Console whenever referring to this data
source.

JNDI
Name - Enter the JNDI path to where this JDBC data
source will be bound. Applications look up the data source on the
JNDI tree by this name when reserving a connection.

XA Driver - Select if you want to use XA
processing.

Click Next to continue.

On the Transaction Options page, follow these steps.
Depending on the driver you selected on the JDBC Data Source
Properties page, you may not need to specify any of these
options.

Supports Global Transactions - Select
this check box (the default) to enable global transaction support in
this data source. Clear this check box to disable (ignore) global
transactions in this data source. In most cases, you should leave
the option selected.

If you selected Supports Global
Transactions, select an option for transaction
processing: (available options vary depending on whether you select
an XA driver or a non-XA driver)

This option is only
available when you select an XA JDBC driver to make database
connections.

Logging Last Resource - Select this
option to enable a non-XA JDBC connection to participate in
global transactions using the Logging Last Resource (LLR)
transaction optimization. Recommended in place of Emulate
Two-Phase Commit.

This option is only available when you
select a non-XA JDBC driver to make database
connections.

WebLogic attempts to create a connection from the Administration
Server to the database. Results from the connection test are
displayed at the top of the page. If the test is unsuccessful, you
should correct any configuration errors and retry the test.

If the JDBC driver you selected is not installed on the
Administration Server, you should click Next
to skip this step.

Click Next to continue.

On the
ONS Client Configuration page, enter values for the following
properties:

Select Fan Enabled to subscribe to Oracle
Fan Events.

Enter the ONS host and port for each ONS
node.

Optionally, configure an ONS wallet file if you want ONS to use
SSL protocol.

Click Next to continue.

On the
Test ONS client configuration page, review the
parameters and click Test All ONS Nodes. To
test individual nodes, click Test ONS Node for
an ONS host and port.

Click Next to continue.

On the
Select Targets page, select the servers or
clusters on which you want to deploy the data source.

Click
Finish to save the JDBC data source
configuration and deploy the data source to the targets that you
selected.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).