Skip Headers
Oracle® Clinical Development Analytics Installation Guide
Release 2.0.0.2

Part Number E18163-04
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
View PDF

3 Post Installation Tasks

This chapter describes post installation tasks that you must complete before you begin to use the OCDA. This chapter includes the following topics:

Locating and Downloading the OCDA Patches

To locate and download the OCDA patches:

Locating and downloading the OCDA 2.0.0.1 patch

  1. Sign in to My Oracle Support at http://support.oracle.com.

  2. Click the Patches & Updates tab.

    The Patches & Updates page opens and displays the Patch Search region. You have the following options:

    • In the Patch ID or Number is field, enter the primary bug number 10152154.

  3. Click Search to execute your query. The Patch Search Results page opens.

  4. Click the patch ID number. The system displays details about the patch. In addition, you can view the Read Me file before downloading the patch.

  5. Click Download. Follow the instructions on the screen to download and save the patch file.

  6. Transfer the patch zip file to the necessary servers.

  7. Oracle recommends that you create a folder called cda_2.0.0.1 under the original location where you installed CDA, and unzip the patch zip file in the temporary staging location. This extracts the following files:

    • readme_ocda2_0_0_1.htm

    • OCDA_domain_2.0.0.1.zip

    • OracleClinicalDevelopmentAnalytics.zip

    • help.zip

    • ocda_src_config.sql

  8. On the Oracle LSH database server, navigate to the directory where OCDA_domain.zip and other files are placed.

  9. Copy and replace the new files from cda_2.0.0.1 into this directory. This replaces the older version files.

Locating and downloading the OCDA 2.0.0.2 patch

  1. Download the patch for 2.0.0.2 with the primary bug number 11731102. Follow step 1 to step 6 in the Locating and downloading the OCDA 2.0.0.1 patchLocating and downloading the OCDA 2.0.0.1 patchto download the patch.

    Oracle recommends that you create a folder called cda_2.0.0.2 under the original location where you installed CDA, and unzip the patch zip file in the temporary staging location. This extracts the following files:

    • readme_ocda2_0_0_2.htm

    • OCDA_domain_2.0.0.2.zip

    • help.zip

    • ocda_src_config.sql

    • ocda_ddl_pmerr_table_creation.sql

    • ocda_ddl_view_siebel_8.1.1.sql

    • ocda_ddl_synonym_siebel_8.1.1.sql

    • ocda_ddl_non_lsh_tables.sql

    • ocda_sc_del_trigger.sql

  2. On the Oracle LSH database server, navigate to the directory where OCDA_domain.zip and other files are placed.

  3. Copy and replace the new files from cda_2.0.0.2 into this directory. This replaces the older version files.

Before installing the patch, you must create error logging tables that are used by Informatica and views atop Siebel Clinical 8.0.x.

Creating Informatica Error Logging and Oracle Clinical Development Analytics Auxiliary Tables

To create error logging and auxiliary tables:

  1. Log in to LSH database as Apps user.

  2. At the SQL prompt, enter:

    @ocda_ddl_pmerr_table_creation.sql

    The execution of this script creates four error logging tables used by Informatica.

  3. At the SQL prompt, enter:

    @ocda_ddl_non_lsh_tables.sql

    The execution of this script creates auxiliary tables required for OCDA.

Creating Views Atop Siebel Clinical 8.0.x

If your Siebel Clinical version is below 8.1.1, you must create view atop Siebel Clinical 8.0.x.

Following are the prerequisites for creating views:

  • Create a user <OCDA_SC_SRC> with grants for connect, resource, create any synonym, and create any view privileges.

  • The user who is executing this script should have the create view privilege for the <OCDA_SC_SRC> schema.

  • The user <OCDA_SC_SRC> should have privileges to select data from the Siebel source tables listed in the script.

  • <OCDA_SC_SRC> schema login is used in the load set OCDA_SC_OLTP_RL which reads Siebel data.

  1. Log in to Siebel Clinical source database.

  2. At the SQL prompt, enter:

    @ocda_ddl_view_siebel_8.1.1.sql

    The execution of this script creates views atop Siebel Clinical.

Creating Synonyms Atop Siebel Clinical 8.0.x

You should use synonym creation script only if:

  • You have used the ocda_ddl_view_siebel_8.1.1.sql script to create views, so that rest of the tables needed are created as synonym.

  • You would like to create a separate schema and restrict access to selected data from the Siebel tables.

Following are the prerequisites for creating synonyms:

  • Create a user <OCDA_SC_SRC> with grants for connect, resource, create any synonym, and create any view privileges.

  • The user who is executing this script should have the create synonym privilege for the <OCDA_SC_SRC> schema.

  • The user <OCDA_SC_SRC> should have privileges to select data from the Siebel source tables listed in the script.

  • <OCDA_SC_SRC> schema login is used in the load set OCDA_SC_OLTP_RL which reads Siebel data.

To create synonyms atop Siebel Clinical 8.0.x:

  1. Log in to Siebel Clinical source database.

  2. At the SQL prompt, enter:

    @ ocda_ddl_synonym_siebel_8.1.1.sql

    The execution of this script creates synonyms atop Siebel Clinical.

Setting Up Service Locations

The following services must be available in OCDA:

See Also:

Perform the following steps to confirm which services are shipped with OCDA:

You use Oracle LSH to set up the services for OCDA. To log in to Oracle LSH, you must have a Web browser on your computer and the URL, user name, and password provided by your company.

  1. Log in to Oracle LSH:

    1. Open your Web browser.

    2. Enter the URL provided by your company.

    3. Login as a user with LSH System Administrator role.

  2. Click the Life Sciences Data Hub link. The system displays all the screens to which you have security access.

  3. Click Applications. The system opens the Applications tab.

  4. Click the Select Domain field, and enter OCDA_domain.

  5. Click Go. The Application Area displays its associated Work Areas.

  6. Expand OCDA_OBIEE_CODE_APP_AREA.

  7. Expand OCDA_OBIEE_WA.

  8. Click OCDA Data Warehouse.

  9. Look in the Attributes section and write down the OBIEE Service Location Name.

  10. Create an OBIEE Service Location with the same name as given in the previous step. There are three types of OBIEE services; OBIEE Business Area Install Service, OBIEE Business Area Deploy Service, and OBIEE Business Area IDE Service. You must create all three. If you want to specify a different name for the service location, do the following:

    1. Check out the business area.

    2. Update the service location name.

    Caution:

    Ensure that the Informatica Distributed Processing (DP) Server is up and running. For more information on setting up DP Server in Oracle LSH, refer to Oracle Life Sciences Data Hub System Administrator's Guide (Setting Up the Distributed Processing Server section in Chapter 1, Setting Up Services.

Setting Up Remote Locations in Oracle Life Sciences Data Hub

OCDA installs a default domain OCDA_domain. You must configure remote locations on this domain. The following are the remote locations:

Configuring Remote Locations for Passthrough Views

To configure the remote location OCDA_OC_OLTP_RL:

  1. Click the Remote Location subtab under the Administration tab. The Maintain Remote Locations screen opens.

  2. Click Add Remote Location. The Create Remote Location screen appears.

  3. Enter values in the following fields:

    • Enter OCDA_OC_OLTP_RL as Remote Location Name.

    • Description. Enter a description of the Remote Location.

    • DBLINK Prefix. The name of the database link. If another DBLINK Prefix with the same name exists in the database, the system adds an additional string to make it unique. The DBLINK_NAME is usually the global name or the TNS name of the remote database.

    • Connect String. The name of the string that Oracle LSH must use in the USING clause of the create database link SQL statement. Connect string has following format:

      ((DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=dbportnumber))(CONNECT_DATA=(SID=dbsid))))

    • Adapter. Select Oracle Tables and Views from the drop-down list.

  4. Click Apply.

Repeat the above steps to configure the OCDA_SC_OLTP_RL and OCDA_CUSTOM_OLTP_RL remote locations.

See Also:

Oracle Life Sciences Data Hub System Administrator's Guide (Chapter 6, Registering Locations and Connections), for more information on registering locations and connections in Oracle LSH.

Configuring Connections

Once the remote location is created, add connections to the remote location.

To add connections to the remote location:

  1. In the main screen for the Remote Location for which you want to create a Connection, click Create Connection. The Connection Maintenance screen opens.

  2. Click Create Connection. The Create Connection screen appears.

  3. Enter values in the following fields:

    Table 3-1 Connections for OCDA_OC_OLTP_RL

    Name User Name Password

    RXC

    RXC

    Password to access the RXC schema in Oracle Clinical.

    RXA_DES

    RXA_DES

    Password to access the RXA_DES schema in Oracle Clinical.

    OPA

    OPA

    Password to access the OPA schema in Oracle Clinical.


    Table 3-2 Connections for OCDA_SC_OLTP_RL

    Name User Name Password

    siebel

    siebel

    Password to access the Siebel Clinical schema.


    Note:

    If you have used either the view creation script or the synonym creation script, you must use the same user who is the owner of the schema for setting OCDA_SC_OLTP_RL.

    Table 3-3 Connections for OCDA_CUSTOM_OLTP_RL

    Name User Name Password

    RXI

    RXI

    Password to access the RXI schema.


  4. Click Apply.

  5. Repeat for each connection.

Configuring Load Set Attributes

Perform the following steps in Oracle LSH to configure load set attributes for OCDA_OC_OLTP_RL:

  1. Navigate to the OCDA_SOURCES_APP_AREA.

  2. Click OCDA_OC_DATA_WA work area.

  3. Click OCDA_OC_RXA_DES_LS load set.

  4. Click Check Out.

  5. Click Apply.

  6. In the Load Set Attributes section, click Update.

  7. Click the Search icon for Remote Location field.

  8. Select OCDA_OC_OLTP_RL/RXA_DES.

  9. Click Apply.

  10. Repeat step 4 to step 7 for OCDA_OC_RXC_LS.

  11. Select OCDA_OC_OLTP_RL/RXC.

  12. Click Apply.

  13. Reinstall the work area containing the load set and passthrough views.

Perform the following steps in Oracle LSH to configure load set attributes for OCDA_SC_OLTP_RL:

  1. Navigate to the OCDA_SOURCES_APP_AREA.

  2. Click OCDA_SC_DATA_WA work area.

  3. Click OCDA_SC_LS load set.

  4. Click Check Out.

  5. Click Apply.

  6. In the Load Set Attributes section, click Update.

  7. Click the Search icon.

  8. Select OCDA_SC_OLTP_RL/SIEBEL.

  9. Click Apply.

  10. Reinstall the work area containing the load set and passthrough views.

Perform the following steps in Oracle LSH to configure load set attributes for OCDA_CUSTOM_OLTP_RL:

  1. Navigate to the OCDA_SOURCES_APP_AREA.

  2. Click OCDA_CUSTOM_TABLE_WA work area.

  3. Click OCDA_RXI_LS load set.

  4. Click Check Out.

  5. Click Apply.

  6. In the Load Set Attributes section, click Update.

  7. Click the Search icon.

  8. Select OCDA_CUSTOM_OLTP_RL /RXI.

  9. Click Apply.

  10. Reinstall the work area containing the load set and passthrough views.

See Also:

Oracle Life Sciences Data Hub Application Developer's Guide (Chapter 12, Using, Installing, and Cloning Work Areas), for more information on using, installing, and cloning work areas.

Configuring Oracle Business Intelligence Enterprise Edition

To configure the OBIEE application, you must:

  1. Add an entry to the NQSConfig.ini file for the OCDA repository file. The NQSConfig.ini file is located at OracleBI/server/Config/.

    For more information on integrating with other systems, refer to Oracle Life Sciences Data Hub Installation Guide (Chapter 8, Integrating with Other Systems).

  2. Edit the instanceconfig.xml file to point its CatalogPath entry to the Web Catalog of OCDA.

    For more information on administering the Oracle BI Presentation Catalog, refer to Oracle Business Intelligence Presentation Services Administration Guide.

    For more information on setting up the OBIEE Admin tool, refer to Oracle Life Sciences Data Hub Application Developer's Guide (Defining Oracle Business Intelligence Business Areas section in Chapter 11, Defining Business Areas for Visualizations).

Setting Up the Source System

By default, OCDA is configured to use both Oracle Clinical and Oracle's Siebel Clinical as the data source. If you want to use only Oracle Clinical or only Siebel Clinical as a single data source, perform the following steps:

  1. In Oracle LSH, navigate to OCDA_domain > OCDA_CODE_APP_AREA.

  2. Click OCDA_UTIL_WA.

  3. Click Installation.

  4. In the Work Area Install screen, select the following options:

    • Install Mode: Full

    • Install Option: Force Script Re-generation

  5. In Work Area Objects, click Omit None.

  6. Click Apply and Install.

  7. Log in to the Oracle LSH database server as an apps user, navigate to the directory where ocda_src_config.sql is placed.

  8. Run the following command:

    sqlplus apps/<apps_password>@<DB_INSTANCE> @ocda_config_src.sql

    This prompts you to enter the following information:

    • User Name: Enter the LSH application user account as created in the Creating an Oracle Life Sciences Data Hub User Account section.

    • Password: Enter the LSH application user account password as created in the Creating an Oracle Life Sciences Data Hub User Account section.

    • Source System: Enter the source system ID to disable. The possible values are:

      1 - ORACLE CLINICAL

      2 - SIEBEL CLINICAL

      Note:

      If you disable one of the source systems and apply any OCDA patch, an error is displayed because system is not able to find objects of the disabled source system.

Setting Oracle Clinical Development Analytics Repository Password

The default Administrator password for the OCDA repository file (rpd) is SADMIN. To set this default password in the deployed repository file, you must ensure that you set the Administrator password as SADMIN in Oracle LSH under the OBIEE Remote Location. To do this, perform the following tasks:

  1. Create an OBIEE Remote Location in Oracle LSH. Perform steps listed in Creating an OBIEE Remote Location, Creating an OBIEE Remote Location.

    IMPORTANT: The Remote Location name must have the same name as the OBIEE service location name set up in the Setting Up Service Locations section.

  2. Create an OBIEE Remote Location Connection and set the Administrator password as SADMIN. Perform steps listed in Creating an OBIEE Remote Location Connection, Creating an OBIEE Remote Location Connection.

  3. Navigate to OCDA_domain > OCDA_OBIEE_CODE_APP_AREA > OCDA_OBIEE_WA, and install OCDA Data Warehouse.

You can use Oracle LSH to change the Administrator password once you have deployed the repository file. To do this, perform the following tasks:

  1. Use the Oracle BI Administration tool to change the Administrator password in the deployed repository file.

  2. Use Oracle LSH to update the new password in the OBIEE Remote Location Connection.

  3. Use Oracle LSH to update the new password in the repository file stored in OCDA Business Area. For more information about modifying the OCDA repository file, refer to Oracle Clinical Development Analytics User and Administrator Guide (Chapter 4, Maintaining the Repository and Warehouse).

Note:

If you use the Oracle BI Administration tool to make any changes to the repository including changes to the Administrator account password, you must manually upload that modified repository into Oracle LSH. If you do not upload the modified repository, changes are lost the next time you install the OCDA Business Area.

Creating an OBIEE Remote Location

Perform the following steps in Oracle LSH to define a Remote Location:

  1. Click the Remote Location subtab under the Administration tab. The Maintain Remote Locations screen opens.

  2. Click Add Remote Location. The Create Remote Location screen appears.

  3. Enter values in the following fields:

    • Name. Enter the exact same name you have given for the OBIEE service location.

    • Description. Not required.

    • DBLINK Prefix. Enter any value. The system does not use this value.

    • Connect String. Enter any value. The system does not use this value.

    • Adapter. Select OBIEE from the drop-down list.

    • Conversion Multiplier. Do not enter a value.

  4. Classification: The system does not use these values.

  5. Click Apply to save your work. The system opens the main screen for the new Remote Location.

    By default, the Remote Location inherits the user group assignments of the Adapter Area.

Creating an OBIEE Remote Location Connection

For each OBIEE Remote Location, create a Remote Connection.

Perform the following steps in Oracle LSH to define a Connection:

  1. In the main screen for the Remote Location for which you want to create a Connection, click Create Connection. The Create Connection screen opens.

  2. Enter values in the following fields:

    • Name. Enter a name for the Connection.

    • Description. Not required.

    • User Name. Enter Administrator.

    • Password. Enter SADMIN as the password. Oracle LSH encrypts the password for security.

    • Connection Type. The system does not use this value.

    • Remote Location. The system populates the field with the name of the Remote Location for which you are defining this Connection.

  3. Classification: The system does not use these values.

  4. Click Apply to save your work. The system displays the main screen for the new Connection.

See Also:

  • Oracle Life Science Data Hub System Administrator's Guide (Creating an OBIEE Remote Location and Connection for RPD Password Security)

  • Oracle Clinical Development Analytics User and Administrator Guide (Chapter 6, Implementing Security), for more information on implementing security in OCDA.

Handling Deletion in Oracle's Siebel Clinical

For information on how to handle deletion of records in Siebel Clinical, refer to Oracle Clinical Development Analytics User and Administrator Guide (Chapter 5, Extract Transform Load Programs).

If Siebel clinical is one of your source and you are not handling deletions perform the following steps in Oracle LSH to configure load set attributes for OCDA_CUSTOM_OLTP_RL:

  1. Navigate to the OCDA_SOURCES_APP_AREA.

  2. Click OCDA_DELETE_LOG_TABLE_WA work area.

  3. Click OCDA_RXI_DELETE_LS load set.

  4. Click Check Out.

  5. Click Apply.

  6. In the Load Set Attributes section, click Update.

  7. Click the Search icon.

  8. Select OCDA_CUSTOM_OLTP_RL /RXI.

  9. Click Apply.

  10. Reinstall the work area containing the load set and passthrough views.

Loading Oracle Clinical Development Analytics Seed Tables

Log in to the Oracle LSH database using the rxi account, and run the OCDA_W_RXI_LOV_S_seed.sql script from the temporary staging location.

This script inserts seed data into the W_RXI_LOV_S table.

Scheduling and Executing Extract Transform Load Jobs

Note:

Ensure that each ETL program has a default Execution Setup.

For information on scheduling and executing Extract, Transform, and Load (ETL) jobs, refer to Oracle Clinical Development Analytics User and Administrator Guide (Chapter 5, Extract Transform Load Programs).

Deploying the Oracle Clinical Development Analytics RPD

Note:

Ensure that ETL is executed and warehouse has requisite data before you deploy the RPD.
  1. Ensure that OBIEE DP server is up and running.

  2. Navigate to OCDA_domain > OCDA_OBIEE_CODE_APP_AREA > OCDA_OBIEE_WA

  3. Install the OCDA_OBIEE_WA work area in Full mode.

Deploying Oracle Clinical Development Analytics on Oracle WebLogic Managed Server

You need to manually deploy OCDA's help and images files on Oracle WebLogic Managed Server. Perform the following steps:

  1. Stop the Oracle WebLogic Server.

  2. Navigate to <OBIEE_HOME>\web and extract analytics.war to the same location.

    <OBIEE_HOME> is the OBIEE installation folder.

  3. In a temporary staging location, unzip the help and images files.

  4. Copy the help and images folders to the following locations:

    • <OBIEE_HOME>\web\app\res\s_oracle10

    • <OBIEE_HOME>\web\analytics\res\s_oracle10

  5. Start Administration Server for Oracle WebLogic Server Domain.

  6. Start Node Manager.

  7. Launch Admin Serve Console.

    This opens the Oracle WebLogic Server Administration Console.

  8. Log in to Oracle WebLogic Server Administration Console.

  9. In the left pane of the Administration Console, select Deployments.

  10. In the right pane, click Install.

    This opens the Install Application Assistant.

  11. In Path, enter the path as <OBIEE_HOME>\web

    where:

    <OBIEE_HOME> is the OBIEE installation folder.

  12. Select analytics and click Next.

  13. In Choose targeting style, select Install this deployment as an application and click Next.

  14. In Available targets for analytics, select the servers in the cluster on which you want to deploy OCDA.

  15. Click Next.

  16. In the General section, enter the name of this deployment as analytics.

  17. In the Security section, select DD Only: Use only roles and policies that are defined in the deployment descriptors.

  18. In the Source accessibility section, select I will make the deployment accessible from the following location, and enter the following path in Location:

    <OBIEE_HOME>\web\analytics

  19. Click Next.

  20. Select Yes, take me to the deployment's configuration screen and click Finish.

  21. Start all the servers in the clusters.

  22. Start the following servers:

    • Oracle BI Java Host

    • Oracle BI Presentation Server

    • Oracle BI Server

  23. Select the analytics deployment.

  24. Click the Testing tab.

    The Test Point column lists the links.

  25. Click on all the links in the Test Point column.

See Also: