Skip Headers
Oracle® Health Sciences Clinical Development Analytics Installation Guide
Release 2.1 for Plus Configuration

E25026-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

2 Oracle Health Sciences Clinical Development Analytics Installation

This chapter presents an overview of the Oracle Universal Installer and CDA installation process. It also describes the CDA Installation tasks that you must complete for different environments. This chapter includes the following topics:

Note:

You can install CDA using any OBIEE configuration supported by Oracle LSH.

2.1 About Oracle Health Sciences Clinical Development Analytics Installation

CDA has multi-server architecture. There are two parts of installation:

2.2 About the Oracle Universal Installer

CDA uses the Oracle Universal Installer to guide you through each step of the installation process.

The Oracle Universal Installer provides the following features:

Figure 2-1 Welcome Screen

Description of Figure 2-1 follows
Description of "Figure 2-1 Welcome Screen"

2.2.1 Requirements for Tablespace

Before you run the installer, make sure that the autoextend feature is enabled for the following tablespaces in the Oracle LSH database:

  • APPS_TS_MEDIA

  • APPS_TS_TX_DATA

  • APPS_TS_TX_IDX

  • APPS_UNDOTS1

  • CTXSYS

Oracle recommends the following tablespace free space (minimum):

  • APPS_TS_MEDIA – 1 GB of free space

  • APPS_TS_TX_DATA – 2 GB of free space

2.3 Gathering Table Statistics

Before you install CDA, run the Gather Schema Statistics concurrent program to gather table statistics. The concurrent program can be run from the System Administrator Responsibility to generate statistics. Perform the following steps:

WARNING:

Ensure there are no other concurrent jobs are running when you gather table statistics; else those concurrent jobs might complete with errors.

  1. Log in to Oracle LSH with the System Administrator responsibility.

    For example, you can use the sysadmin account and password.

  2. Navigate to System Administrator > Run.

    The Submit a New Request window opens in Oracle Applications Profile Forms.

  3. Click OK.

    The Submit Request window opens.

  4. In Name, select Gather Schema Statistics.

  5. Click in the Parameters field.

  6. In the Parameters window, enter CDR as the Schema Name.

    This can be run for specific schemas by specifying the schema name or entering CDR to gather statistics for every schema in the database.

  7. Click OK.

  8. Click Submit.

  9. Perform step 2 through 8 for APPS schema also.

To check if the Gather Schema Statistics concurrent program you submitted has executed successfully, perform the following steps:

  1. Log in to Oracle LSH with the System Administrator responsibility.

    For example, you can use the sysadmin account and password.

  2. Navigate to System Administrator > View.

    The Find Requests window opens in Oracle Applications Profile Forms.

  3. Select All My Requests.

  4. Click Find.

2.4 Running the CDA Installer on Windows

The basic CDA components are installed using the Oracle Universal Installer. The installer gathers all the information about the database connectivity, data mart, Informatica repository by presenting a sequence of prompt screens and then installs the components accordingly.

Important:

Make sure that both the Oracle Database client and the Informatica client are available on the same system where you plan to execute the installer.

Perform the following steps to install the CDA application on Windows:

  1. Extract the contents of the media pack into a temporary directory (For example, C:\ocda_temp).

  2. Navigate to the \install directory under the extracted temporary folder.

  3. Double-click the setup.exe file to launch the Oracle Universal Installer with the Welcome screen.

    The installer will take you through a series of screens having fields. Attend to the Installer's prompts. The following sections describe each Installer screen, and the required action.

  4. Review the Oracle Universal Installer Welcome screen and click Next. The Welcome screen provides information about the Oracle Universal Installer. The following function buttons appear on the installation screens:

  5. Click Next.

  6. Specify Home Details screen is displayed.

    The OHSCDA Home path is the location where all the staged files from the Installer will get copied to the local system. This is also the location from where Installer would execute the database and Informatica scripts.

    Example Name: OCDAHome1

    Path: C:\OCDA

  7. Click Next.

  8. Install or Upgrade OHSCDA screen is displayed.

    Specify whether you want to make a fresh installation of OHSCDA or upgrade an existing OHSCDA instance.

  9. Click Next.

  10. OHSCDA Data Warehouse Details screen is displayed.

    This screen collects all the information regarding the OHSCDA data warehouse details.

    Enter values in the following fields:

    System Password for OHSCDA Database: This is the System Password of the database where OHSCDA DataWarehouse will be deployed.

    OHSCDA Warehouse Target Connect Name: Logical Name for Connection to be created in Informatica. For example, DataWarehouse. For upgrade, this should be same as the one already configured in Oracle DAC and Informatica PowerCenter.

    Connect String of the Warehouse: Connection of the database where OHSCDA DataWarehouse will be deployed.

    OHSCDA Warehouse Schema (RXI) Password:

    OHSCDA RPD (RXI_MDM) Password:

    Default Table Space:

    Temporary Table Space:

  11. Click Next.

  12. OHSCDA Informatica PowerCenter Details screen is displayed.

    This screen collects all information to connect to the Informatica server.

    Enter values in the following fields:

    Informatica Repository Name : Informatica Repository Name where you plan to import OHSCDA Informatica mappings.

    Informatica Domain Name: Domain of the Informatica repository.

    Informatica Hostname: Host name of the Informatica server.

    Informatica Repository Port Number: Port number of the Informatica server.

    Informatica Username with admin privileges: User with Admin privilege to import XMLs.

    Informatica Password for Admin user:

  13. Click Next.

  14. OHSCDA Informatica PowerCenter Client Home Directory screen is displayed.

    The Informatica PowerCenter client home path is required for the installer to run successfully.

    Example:

    Informatica PowerCenter client home: D:\Informatica\9.0.1\clients\PowerCenter client\client

  15. Click Next.

  16. Multi Source Integration screen is displayed.

    Select Yes to confirm that you plan to use multi source integration feature of OHSCDA.

    If you do not plan to use multi source integration, select No and move to step 21.

  17. Click Next.

  18. Oracle WebLogic Server Details for OHSCDA screen is displayed.

    Enter values in the following fields:

    Username for accessing Oracle WebLogic : Enter a new username. Make sure that the same username is created in Section 3.12.5.4, "Setting Up the User,".

    Password for the user :

  19. Click Next.

  20. Oracle Healthcare Master Person Index screen is displayed.

    Enter values in the following fields:

    System Password for OHMPI Database : System Password of the database where OHMPI model will be deployed

    sys Password for OHMPI Database: SYS password of the database where OHMPI model will be deployed

    Master Password for OHMPI Schemas: Master Password that will be set to all 15 OHMPI schemas.

    Connect String of OHMPI Schemas:

    Default Table Space:

    Temporary Table Space:

  21. Click Next.

  22. Summary screen is displayed.

    Verify setting => details provided in the summary screen.

  23. Click Install.

    At the completion of the installation, you can inspect the installation log at:

    <ocda_home>\install\ocda_install.log.

2.5 Running the CDA Installer on Unix

Consider the following configuration specific instructions:

2.5.1 Installing CDA on the Same Server as Oracle LSH

To install the CDA application on the Oracle LSH Server on Unix:

Important:

This section assumes that the Oracle database is located on the same server as the middle-tier.
  1. Log in as owner of Oracle Applications middle-tier.

  2. Source the APPSORA.env file in $APPL_TOP of your Oracle LSH installation to set the environment variables.

  3. Verify that the Oracle Applications variable $APPLPTMP is defined and that the permissions on the directory are correct and set to 777.

    Ensure that both the applmgr user and the database user oracle have read/write permissions on $APPLPTMP. CDA installation uses this standard location to stage a file that needs to be loaded into the Oracle LSH database.

  4. Insert the CD labeled Oracle Health Sciences Clinical Development Analytics 2.1 into the CD-ROM drive. Transfer the platform specific zip file on the disc to the Oracle LSH server. Extract the contents of the platform specific zip file.

    If you downloaded the CDA media pack from the Oracle E-Delivery Web site, navigate to the directory where you downloaded and extracted the media pack. Locate the platform specific zip file. Transfer the platform specific zip file to the Oracle LSH server. Extract the contents of the platform specific zip file.

  5. Assign 755 permissions to the contents of the install folder where the installer is unzipped

    chmod -R 755 <Path to directory where the installer is unzipped>

  6. Navigate to the following directory:

    install

  7. Set the X Window display output to your local computer's IP address. For example:

    C shell: setenv DISPLAY 123.45.67.89:0l

  8. Invoke the runInstaller executable to launch the installer.

    ./runInstaller

    The installer opens the Welcome screen, which provides information about the Oracle Universal Installer and its options.

  9. Click Next

  10. If you are running the installer for the first time, the Specify Inventory Directory and Credentials screen appears.

    Click Browse to navigate through the available directory to select a location. Select Operating System Group Name from the drop-down list.

  11. Click Next to continue. In the Specify Home Details screen:

    1. Enter a name for this installation.

    2. Enter the full path to Oracle home directory. You can click Browse to navigate through the available directories to select a location for the Oracle home directory.

  12. Click Next to continue. In the Oracle CDA Home Directory screen, enter the full path to Oracle CDA home.

    Oracle CDA home is the directory where the installer puts required installation and log files. It is a permanent directory, retained after installation. Oracle recommends that you create CDA home directory under APPL_TOP (sourced by the APPSORA.env file). For example,

    In Unix, <Path to APPL_TOP>/cda

  13. Click Next to continue. In Enter Temporary Staging Area for the Domain File screen, do not modify the default location (the value of APPLPTMP). This is the temporary staging area from where OCDA_domain.zip will be loaded into the database.

  14. Click Nexton Application Server screen.

  15. Click Next to continue. In the Enter Database TNS Name screen, enter a Transparent Network Substrate (TNS) name.

  16. Click Next to continue. In the Enter User Name for the Oracle Applications screen, enter a user name that you created as part of the Oracle Applications installation.

  17. Click Next to continue. In the Enter Password for the Oracle Applications User Name screen, enter the password for the Oracle Applications user name you specified, and then confirm the password.

  18. Click Next to continue. In the Enter User Name for Oracle LSH Application screen, enter an existing user name.

    You created this user as a prerequisite to installing CDA.

  19. Click Next to continue. In the Enter Password for the Oracle LSH Application User Name screen, enter the password for the Oracle LSH user name you specified, and then confirm the password.

  20. Click Next to continue. In the Enter Password for the System User screen, enter the password for the System database user, and then confirm the password.

  21. Click Next to continue. In the Enter Data Tablespace Name screen, enter the name for an existing data tablespace APPS_TS_TX_DATA.

  22. Click Next to continue. In the Enter Temporary Tablespace Name screen, enter the name for the temporary tablespace that is used for the RXI user.

  23. Click Next to continue. Information screen reminds you to inspect log files. The following log files are generated in Unix environment:

  24. Click Next to continue. On the Summary screen, review the information about your CDA installation.

    • setup.txt, ocda_schema_creation.log, and error.txt in CDA home directory

    • OCDA_domain_import.log in APPLPTMP directory.

  25. Click Install to begin the installation.

  26. Verify the log files.

    Note:

    During the OCDA_Domain import, you can monitor QuickLog.log in CDA_home directory. It shows current import activities that are done by LSH release utilit.y

    If you observe that OCDA_domain import, during installation, is taking more than 3 hours, gather the schema statistics by following the steps in sectionSection 2.3, "Gathering Table Statistics"

2.5.2 Installing CDA on a Stand-alone Database Server

To install the CDA application when the database is located on a separate server than Oracle LSH (split configuration):

  1. Log in as owner of the Oracle Relational Database Management System (RDBMS) software.

  2. Insert the CD labeled Oracle Health Sciences Clinical Development Analytics 2.1 into the CD-ROM drive. Transfer the platform specific zip file on the disc to the Oracle LSH server. Extract the contents of the platform specific zip file.

    If you downloaded the CDA media pack from the Oracle E-Delivery Web site, navigate to the directory where you downloaded and extracted the media pack. Locate the platform specific zip file. Transfer the platform specific zip file to the Oracle LSH server. Extract the contents of the platform specific zip file.

  3. Assign 755 permissions to the contents of the install folder where the installer is unzipped.

    chmod -R 755 <Path to directory where the installer is unzipped>

  4. Navigate to the following directory:

    install

  5. Set the X Window display output to your local computer's IP address. For example:

    C shell: setenv DISPLAY 123.45.67.89:0l

  6. Invoke the runInstaller executable to launch the installer.

    ./runInstaller

    The installer opens the Welcome screen, which provides information about the Oracle Universal Installer and its options.

  7. Click Next to continue. In the Specify Home Details screen:

    1. Enter a name for this installation.

    2. Enter the full path to Oracle home directory. You can click Browse to navigate through the available directories to select a location for the Oracle home directory.

  8. Click Next to continue. In the Oracle CDA Home Directory screen, enter the full path to Oracle CDA home.

    Oracle CDA home is the directory where the installer puts required installation and log files. It is a permanent directory, retained after installation. Oracle recommends that you create CDA home directory under the ORACLE_HOME. For example,

    In Unix, <Path to ORACLE_HOME>/cda

  9. Click Next to continue. In Enter Temporary Staging Area for the Domain File screen, enter the full path of the temporary staging area from where OCDA_domain.zip will be loaded into the database.

    This is a temporary directory where the installer will copy a file that needs to be loaded into the Oracle Database. Enter a valid location. Ensure that this directory has full permission for processes to read/write to this directory. The Oracle database must also have access to this directory so that it can read/write. It is necessary that you set up this directory in the database init.ora settings.

  10. Click Next on Application Server screen.

  11. Click Next to continue. In the Enter Database TNS Name screen, enter a Transparent Network Substrate (TNS) name.

  12. Click Next to continue. In the Enter User Name for the Oracle Applications screen, enter a user name that you created as part of the Oracle Applications installation.

  13. Click Next to continue. In the Enter Password for the Oracle Applications User Name screen, enter the password for the Oracle Applications user name you specified, and then confirm the password.

  14. Click Next to continue. In the Enter User Name for Oracle LSH Application screen, enter an existing user name.

    You created this user as a prerequisite to installing CDA.

  15. Click Next to continue. In the Enter Password for the Oracle LSH Application User Name screen, enter the password for the Oracle LSH user name you specified, and then confirm the password.

  16. Click Next to continue. In the Enter Password for the System User screen, enter the password for the System database user, and then confirm the password.

  17. Click Next to continue. In the Enter Data Tablespace Name screen, enter the name for an existing data tablespace APPS_TS_TX_DATA.

  18. Click Next to continue. In the Enter Temporary Tablespace Name screen, enter the name for the temporary tablespace that is used for the RXI user.

  19. Click Next to continue. Information screen reminds you to inspect log files. The following log files are generated in Unix environment:

  20. Click Next to continue. On the Summary screen, review the information about your CDA installation.

    • setup.txt, ocda_schema_creation.log, and error.txt in CDA home directory

    • OCDA_domain_import.log in the directory selected in step 8.

  21. Click Install to begin the installation.

  22. Verify the log files.

    Note:

    During the OCDA_Domain import, you can monitor QuickLog.log in CDA_home directory. It shows current import activities that are done by LSH release utility.

    If you observe that OCDA_domain import, during installation, is taking more than 3 hours, gather the schema statistics by following the steps in sectionSection 2.3, "Gathering Table Statistics"

After you have finished all the installation tasks, you must perform the post installation tasks listed in Chapter 3, Post Installation Tasks.