4-8 Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server
HOST=centerPORT=1234CONNECT_DATA=SERVICE_ NAME=myService
You can also use a SCAN address. For example: jdbc:oracle:thin:DESCRIPTION=ADDRESS_
LIST=ADDRESS=PROTOCOL=TCPHOST=MyScanAddr-scn.myCompany.co mPORT=1234CONNECT_DATA=SERVICE_NAME=myService
■
Enter myDataBase in Database User Name.
■
Enter myPassword1 in Password.
4.2.4 Test Connections
Test Database Connection allows you to test a database connection before the data
source configuration is finalized using a table name or SQL statement. If necessary, you can test additional configuration information using the Properties and System
Properties attributes.
4.2.5 Configure an ONS Client Configuration
ONS client configuration allows the data source to subscribe to and process Oracle
FAN events. To configure an ONS client:
■
Select Fan Enabled.
■
In ONS host and port, enter a comma-separate list of ONS daemon listen addresses and ports for receiving ONS-based FAN events. You can use Single
Client Access Name SCAN addresses to access FAN notifications.
■
Optionally, configure secure ONS client communication using SSL. See Section 4.2.5.1, Secure ONS Client Communication.
4.2.5.1 Secure ONS Client Communication
To use an Oracle Wallet file with WebLogic Server, you must:
■
Add the following files to the WebLogic Server classpath:
–
MW_HOMEmodulescom.oracle.osdt_cert_1.0.0.0.jar
–
MW_HOMEmodulescom.oracle.osdt_core_1.0.0.0.jar
–
MW_HOMEmodulescom.oracle.oraclepki_1.0.0.0.jar
■
Update your GridLink Data Source configuration to include the directory of the Oracle wallet file in which the SSL certificates are stored and the ONS Wallet
password. See Secure ONS Listener using Oracle Wallet in Oracle WebLogic Server Administration Console Help.
■
For more information on Oracle Wallet, see the Database Advanced Security Administrators Guide.
4.2.6 Test ONS Client Configuration
Test ONS client configuration allows you to test a database connection before the
data source configuration is finalized.
Using GridLink Data Sources 4-9
4.2.7 Target the Data Source
You can select one or more targets to deploy your new JDBC GridLink data source. If you dont select a target, the data source will be created but not deployed. You will
need to deploy the data source at a later time.
4.3 Enable Socket Direct Protocol for a Grid Link Data Source
To enable SDP for an existing Grid Link data source, use the following steps:
■
Add system property -Djava.net.preferIPv4Stack=true to the server startup command line.
■
To enable SPD for a Grid Link data source using the Admininstration Console:
1. If you have not already done so, in the Change Center of the Administration
Console, click Lock Edit. 2.
In the Domain Structure tree, expand Services, then select Data Sources. 3.
On the Summary of Data Sources page, click the data source name.
4. Select the Configuration: Connection Pool tab.
5. In Url, edit the url, replacing instances of PROTOCOL=TCP with
PROTOCOL=SDP .
6. Click Save.
7. To activate these changes, in the Change Center of the Administration
Console, click Activate Changes.
This change does not take effect immediately—it requires that the data source be redeployed untargeted and retargeted or the server be restarted.
For example: jdbc:oracle:thin:DESCRIPTION=ADDRESS_
LIST=ADDRESS=PROTOCOL=SDPHOST=leftPORT=1234ADDRESS=PRO TOCOL=SDPHOST=rightPORT=1234ADDRESS=PROTOCOL=SDPHOST=c
enterPORT=1234CONNECT_DATA=SERVICE_NAME=myService
4.4 Configuring Connection Pool Features
Each JDBC data source has a pool of JDBC connections that are created when the data source is deployed or at server startup. Applications use a connection from the pool
then return it when finished using the connection. Connection pooling enhances performance by eliminating the costly task of creating database connections for the
application.
The following sections include information about connection pool options for a JDBC data source.
■
Section 4.4.1, Enabling JDBC Driver-Level Features
■
Section 4.4.2, Enabling Connection-based System Properties.
Note: To use Socket Direct Protocol SDP, your database network
must be configured to use Infiniband. See Configuring SDP Support for InfiniBand Connections in the Oracle Database Net Services
Administrators Guide.