Skip Headers
Oracle® Clinical Remote Data Capture Onsite Administrator's Guide
Release 4.6

E11064-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Database Connections

During your installation of, or upgrade to RDC Onsite, you configured the database connections on your reports servers and application servers. This chapter repeats the information in case you need to set up additional database connections.

There are two parts to establishing database connections. First, you must update the tnsnames.ora file to include the database. Second, you must use the opaadmin application to set up the necessary database connections to be used with RDC Onsite.

This chapter includes the following topics:

Setting Up the SQL*Net Connections for Existing Databases

Establish that SQL*Net connections exist between the Web Server computer and any databases you have already created by modifying the file tnsnames.ora to include entries for all the databases and Web Servers. The tnsnames.ora file for 10gAS is located at ORACLE_AS10GR2MT_HOME.

Setting Up Database Connections in the opaadmin Utility

The information that you enter for each database with this utility is saved in the file OpaConfig.xml on the application server.

When you use the opaadmin utility to define database connections, you also specify the default database to be used by RDC Onsite. See Customizing the RDC Onsite URL for information on how to connect to non-default databases.

To set up database connections: 

  1. Enter the opaadmin application by opening a browser window and specifying the URL:

    http://server.domain/onsiteadmin/opaConfig.do

    where server.domain is the server and domain of the target AS10gR2 server.

  2. Complete the following fields:

    • Database Name = Name of your database

    • Host = Host name of your database

    • Port = Port number of your database

    • Sid = Sid name of the database

  3. Enter the password for the already existing BC4J_INTERNAL account. If you do not know this password, reset it in the database.

  4. If TMS is installed, enter the password for the TMS_BROWSER account. Leave the TMS_BROWSER passwords blank if TMS is not installed.

  5. Specify Default=true to identify the default database to be used by RDC Onsite users.

  6. Save your changes.

Creating a New User with Access to the opaconfig Form

To create a new user with access to the opaconfig form: 

  1. Log in to OEM (Oracle Enterprise Manager). Select the appropriate instance.

  2. Click the rdc OC4J instance.

  3. Click the Applications tab, the opadamin link, and the Security link.

  4. Click Add User.

  5. Enter Name, Description, Password, Confirm Password. Under Group Memberships, check the jazn.com/OpaConfig check box.

  6. Click OK.

  7. Restart the rdc OC4J instance.

Revoking User Access to the opaconfig Form

To revoke a user's access to the opaconfig form: 

  1. Log in to OEM (Oracle Enterprise Manager). Select the appropriate instance.

  2. Click the rdc OC4J instance.

  3. Click the Applications tab, the opadamin link, and the Security link.

  4. Select the user, and then click Remove. Click Yes on the Confirmation page.

  5. Restart the rdc OC4J instance.