Install the Oracle Clinical Front End Components

To install the Oracle Clinical Front End components:

1. Log in as the user you selected in Identify a Single Account to Perform All Application Tier Installation Tasks.
2. In the staging area, locate the directory where you downloaded and extracted Oracle Clinical (see Download the Software).
3. Run the following file as an administrator:
   Disk1\install\setup.exe

   The Installer opens to the Welcome screen.

   Note:

   See Use the Silent Installer (Optional) for instructions for running the Installer as a file with pre-entered parameter values.

   Note:

   Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Clinical.
4. In the Select a Product to Install page, select Oracle Clinical Front End 5.2.2.0.x.
5. Follow instructions on the installation screens, providing the information you have gathered in Gather Required Information.
6. If the Installer detects that you have already installed Release 5.0 or above and created the OPADomain, the Installer asks if you want to overwrite OPADomain or not.
   Choose to overwrite it if your previous installation failed or only partially completed; for example, the RDC Onsite URL does not work. If you have created it successfully, and especially if you have done customizations such as setting up clusters or multiple databases, do not overwrite OPADomain.
7. Summary: The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.
   Review the installation details to verify that they are correct. To revisit earlier installation screens and make changes, click Back.

   When you are ready to continue, click Install.

8. Install: The Installer copies the files onto the server, completes the setup and configuration tasks, and generates a log file of this installation.
   In addition, the Install screen displays the location of the log file that records the results of the installation activities for this session. Make a note of this information so you can view the log file after the installation.
9. End of Installation: The End of Installation screen reports whether the installation was successful. In addition, this screen lists the URLs that you use to access the Oracle Clinical, RDC Onsite, and RDC Administration applications.
   The Installer saves the URL information in the following file:

   \opapps52\log\setup.txt

   When you have finished reviewing the installation information, click Exit.

For more information, see:

• Review the Installation Log Files
  
• Restart the Computer
  
• Add WebLogic Data Sources If Using Multiple Databases
  

Review the Installation Log Files

Doc bug 28977635

1. Review the generated installation log file, installActionstimestamp.log, located at:
   \Oracle\Inventory\logs

   For example:

   C:\Program Files\Oracle\Inventory\logs

   This is the name of the most current log file. Earlier files have a timestamp appended to the name.

Also, review the log files located in the C:\opapps52\log folder.

Work with Oracle Health Sciences Support, if necessary, to resolve any errors.

Restart the Computer

To ensure that all configuration changes are initialized:

1. Restart the computer before you continue with the next task in the installation process or before you install Oracle Clinical Reports Server.

Add WebLogic Data Sources If Using Multiple Databases

When you run the Oracle Clinical Installer, it sets up two data source connections, one for OPA and one for RDC Onsite, from the WebLogic Server (WLS) to the database you specify in the Installer screens.

If you plan to use more than one database:

1. Create a WLS data source for RDC for each additional database.

If you also are using TMS on multiple databases:

1. Create additional data sources for OPA and the TMS Browser.

   The OPA connection is used for running TMS reports.

Instructions are in the Oracle Clinical Remote Data Capture Onsite Administrator's Guide and the Oracle Thesaurus Management System User's Guide.