Adding WebLogic Server Data Sources

When you run the Oracle Clinical Installer, it sets up a data source for OPA and RDC from the WebLogic Server to a the default database.

If you plan to use more than one database, you must create a data source for RDC for each additional database. If you also are using TMS, you need to create data sources for OPA. The OPA connection is used for running TMS reports.

Go through these instructions for one data source at a time.

1. Log in to the WebLogic Server Administration Console at:

   http://host:7101/console/login/LoginForm.jsp

2. Select Data Sources, then New, the Generic Data Source.
3. Enter a name for the data source.
4. Enter the JNDI name as:
   • For OPA: jdbc/opadatabase_nameDS
   • For RDC: jdbc/rdcdatabase_nameDS
5. On the next screen:
   • If the database you want to connect to is a RAC database, choose Oracle's Driver (Thin) for Service connections; Versions: Any
   • If the database is not a RAC database, choose Oracle's Driver (Thin) for Instance connections; Versions: Any
6. On the next screen, uncheck Supports Global Transactions.
7. On the next screen, enter the database name, host name, and port for the database. For the user, enter the following user account and its password:
   • For OPA: tms proxy
   • For RDC: rdc_midtier_proxy
8. On the next screen, select Test Configuration to validate if you can connect using the pool setup.
9. On the next screen, assign OpaServer1 as the target.
10. Click Finish.
11. Select the newly created Data Source, click the Connection Pool tab, and then click Advanced.
12. Add the property databaseName=OracleDataSource into Properties field.
13. Add the property dataSourceName= sid/database_name into Properties field where sid/database_name accordingly if the property not getting created already by the weblogic admin console's create data source wizard.
14. Uncheck Wrap Data Types and save.
15. Review and set additional parameters in Advanced Settings as appropriate for your expected data load.
16. Activate your changes or restart the OPA server for the changes to take effect. Also see Restarting the OPA Server.