D Creating a GridLink Data Source

This appendix describes the procedure for creating a GridLink data source without support for global transactions using the Oracle WebLogic Server Administration Console.

This appendix contains the following topics:

Section D.1, "Creating a GridLink Data Source Using the Oracle WebLogic Server Administration Console"

D.1 Creating a GridLink Data Source Using the Oracle WebLogic Server Administration Console

To create a GridLink data source:

Log in to the Oracle WebLogic Server Administration Console at the URL listed in Section 8.18.2, "Validating Access through Oracle Traffic Director."
If you have not already done so, in the Change Center, click Lock & Edit.
In the Domain Structure tree, expand Services, then select Data Sources.
On the Summary of Data Sources page, click New and select GridLink Data Source, and enter the following:
- Name: Enter a logical name for the data source. (For example: DatasourceName)
- JNDI: Enter a name for JNDI. (For example: jdbc/DatasourceName)
- Database Driver: Select For the Database Driver, select Oracle's Driver (Thin) for GridLink Connections Versions: 11 and later.
- Click Next.
In the Transaction Options page, de-select Supports Global Transactions, and click Next.
In the GridLink Data Source Connection Properties Options screen, select Enter individual listener information and click Next.
Enter the following connection properties:
- Service Name: Enter the service name of the database with lowercase characters. For a GridLink data source, you must enter the Oracle RAC service name. For example:
```
SOAEDG.mycompany.com
```
- Host Name and Port: Enter the SCAN address and port for the RAC database being used. You can identify this address by querying the appropriate parameter in the database using the TCP Protocol:
```
show parameter remote_listener;

NAME                 TYPE        VALUE
 
--------------------------------------------------
 
remote_listener     string      DB-SCAN.mycompany.com
```
  Note:
  
  For Oracle Database 11g Release 1 (11.1), use the virtual IP and port of each database instance listener, for example: CUSTDBHOST1-VIP.mycompany.com (port 1521) and CUSTDBHOST2-VIP.mycompany.com (port 1521), where 1521 is DB_LSNR_PORT
  
  For Oracle Database 10g, use multi data sources to connect to an Oracle RAC database. For information about configuring multi data sources see Appendix A, "Using Multi Data Sources with Oracle RAC."
- Database User Name: DatasourceUser
- Password: For example: welcome1
- Confirm Password: Enter the password again and click Next.
On the Test GridLink Database Connection page, review the connection parameters and click Test All Listeners. Here is an example of a successful connection notification:
```
Connection test for jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=DB-SCAN.mycompany.com)
(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SOAEDG.mycompany.com))) succeeded.
```
where port 1521 is DB_LSNR_PORT.

Click Next.
In the ONS Client Configuration page, do the following:
- Select FAN Enabled to subscribe to and process Oracle FAN events.
- Enter here also the SCAN address for the RAC database and the ONS remote port as reported by the database (example below) and click ADD:
```
[srvctl config nodeapps -s
 
ONS exists: Local port 6100, remote port 6200, EM port 2016
```
- Click Next.
Note:

For Oracle Database 11g Release 1 (11.1), use the hostname and port of each database's ONS service, for example:
```
CUSTDBHOST1.mycompany.com (port 6200)
```
and
```
CUSTDBHOST2.mycompany.com (6200)
```
On the Test ONS Client Configuration page, review the connection parameters and click Test All ONS Nodes.

Here is an example of a successful connection notification:
```
Connection test for DB-SCAN.mycompany.com:6200 succeeded.
```
Click Next.
In the Select Targets page, select osb_cluster and soa_cluster as the targets, and All Servers in the cluster.
Click Finish.
Click Activate Changes.