Create a GridLink Data Source on Dept1_Cluster1

You create a Grid Link Data Source data source to each of the Oracle database instances during the process of setting up the multi-data source, both for these data sources and the global leasing multi-data source. When you create a data source:

• Make sure that this is a non-xa data source

• Target these data sources to the Dept1_Cluster1 cluster.

• Make sure that the datasources connection pool initial capacity is set to 0. To do this, in the Oracle WebLogic Server Administration Console, select Services, JDBC, and then Datasources. In the Datasources screen, click the Datasource Name, then click the Connection Pool tab, and enter 0 in the Initial capacity field.

• Ensure that an ONS daemon is running on your database servers at all times. You can start the ONS daemon on a database server by running the onsctl command:

  start

To create a Grid Link Data source, complete the following steps:

1. Log in to the Oracle WebLogic Server Administration Console.
2. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
3. In the Domain Structure tree, expand Services, then select Data Sources.
4. On the Summary of Data Sources page, click New and select GridLink Data Source.

   The Create a New JDBC GridLink Data Source page is displayed.

5. Enter the following information:

   • Enter a logical name for the datasource in the Name field. For example, gridlink.

   • Enter a name for JNDI. For example, jdbc/gridlink.

   • Click Next.

6. In the Transaction Options page, de-select Supports Global Transactions, and click Next.
7. Select Enter individual listener information and click Next.
8. Enter the following connection properties:

   • Service Name: Enter the name of the Oracle RAC service in the Service Name field. For example, enter myService in Service Name.

     ---

     Note -  The Oracle RAC Service name is defined on the database, and it is not a fixed name.

     ---

   • Host Name - Enter the DNS name or IP address of the server that hosts the database. For an Oracle GridLink service-instance connection, this must be the same for each data source in a given multi data source.

   • Port - Enter the port on which the database server listens for connections requests.

   • Database User Name: Enter the database user name. For example, myDataBase.

   • Password: Enter the password. For example, myPassword1.

   • Confirm Password and click Next.

   ---

   Tip  -  For more information, see the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

   ---

   The console automatically generates the complete JDBC URL. For example:

   jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=left)(PORT=1234))(ADDRESS=(PROTOCOL=TCP)(HOST=right)(PORT=1234))(ADDRESS=(PROTOCOL=TCP)(HOST=center)(PORT=1234)))(CONNECT_DATA=(SERVICE_NAME=myService)))

9. On the Test GridLink Database Connection page, review the connection parameters and click Test All Listeners.

   Oracle 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.

   Click Next.

10. In the ONS Client Configuration page, do the following:

    • Select Fan Enabled to subscribe to and process Oracle FAN events.

    • 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.

    • Click Next.

11. On the Test ONS client configuration page, review the connection parameters and click Test All ONS Nodes.

    Click Next.

12. In the Select Targets page, select Dept1_Cluster1 as the target and All Servers in the cluster
13. Click Finish.
14. Click Activate Changes.
15. Now you must configure SDP-enabled JDBC drivers for the cluster. For instructions, go to Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1.