2 Installing Oracle Health Sciences Clinical Development Analytics

This chapter describes the OHSCDA installation tasks that you must complete.

OHSCDA application installation consists of the following components:

• Adding InForm Studies to the OHSCDA Warehouse

• Running the OHSCDA Installer

• Source-specific Procedures

• Setting Up Relational Connections in the Informatica Workflow for OHSCDA

• Preparing a DAC Repository for OHSCDA

• Emplacing the OHSCDA Help and Image Files

• Preparing the OBIEE Web Catalog and Repository for OHSCDA

• Configuring HTML 5

• Configuring Maps

• Creating Security Groups and Application Roles for OHSCDA

2.1 Adding InForm Studies to the OHSCDA Warehouse

Note:

You must perform the tasks in this section only if:

• You have InForm as a source

• It is a fresh installation of OHSCDA

Figure 2-1 displays the OHSCDA InForm consolidation installation scenarios.

Figure 2-1 OHSCDA InForm Consolidation Installation Scenarios

Description of ''Figure 2-1 OHSCDA InForm Consolidation Installation Scenarios''

Note:

You can download the OHSCDA patch from My Oracle Support (https://support.oracle.com).

2.1.1 OHSCDA InForm Consolidation Schema

This section describes how OHSCDA extracts InForm's operational data and loads it into the OHSCDA warehouse. All of the data for each InForm study is maintained in a transactional database (actually a database schema). InForm maintains one or more InForm databases per Oracle database instance. Each study also has a Reporting and Analysis database (again, a set of objects in a schema, not necessarily an exclusive database instance) which contains data in views designed for query, as opposed to transactional activity.

Inform maintains the Reporting and Analysis database for each study in a study-specific schema. For efficiency and maintainability, OHSCDA has created a program that extracts data from a number of InForm Reporting and Analysis databases and places that data into a single consolidated database. Then, OHSCDA's source-dependent extract code reads from the consolidated database, and writes to the OHSCDA warehouse.

For the remainder of this section, refer to any given InForm Reporting and Analysis database as a source schema and the schema in which OHSCDA consolidates InForm data as the consolidation schema.

OHSCDA consolidates data from selected InForm source schema views, the selected ones being the ones that have data corresponding to columns in the OHSCDA data model. The following are the InForm source views that are consolidated for OHSCDA:

• IRV_AF_SUBJECT_FORMS

• IRV_CUR_QUERY

• IRV_CUR_RULE

• IRV_CUR_SITE

• IRV_CUR_SPONSOR

• IRV_CUR_SUBJECT

• IRV_CUR_USER

• IRV_FORM_REVS

• IRV_ITEMSET_REVS

• IRV_ITEM_REVS

• IRV_QUERY_STATE_CHANGES

• IRV_SECTION_REVS

• IRV_STUDYVERSIONS

• IRV_STUDYVERSION_FORMS

• IRV_STUDYVERSION_VISITS

• IRV_SUBJECT_STATE_CHANGES

• IRV_SV_SUBJECTVISITS

• IRV_USERS_SITES

For each of these source views, the consolidation schema contains a consolidation table. Each consolidation table has the same columns as its source view, except that the consolidation table has three additional columns:

• STUDYGUID

• CONSOLIDATION_DATETIME

• MODIFIEDDATETIME

STUDYGUID is needed to retain the association of each record with its InForm study. CONSOLIDATION_DATETIME and MODIFIEDDATETIME allows OHSCDA ETL to detect which consolidated records have been added or updated since the prior ETL execution.

The names of tables in the consolidation schema match the names of their source views, with the following change:

• IRV in the source view name is replaced with RXI in the consolidation table name.

Consolidation is the process of getting new or modified records from a source schema and updating the consolidation schema with those records. Consolidation is carried out by periodic execution of a scheduled job in each InForm schema that contributes to the consolidation schema. Execution is done through the DBMS_JOB facility. Each source schema is consolidated on its own schedule.

There is no master job that oversees or coordinates the consolidation of all the source InForm schemas. You can choose to consolidate different InForm schemas at different times, and with different intervals between consolidations. However, the more spread out consolidations are, the wider the time period represented by the records in the consolidation schema. So it is recommended that you schedule consolidation jobs to fall within a small time window. For details on scheduling, see Section 2.1.5, "Adjusting Scheduling of Consolidation Jobs".

When the Consolidation job executes for a particular source schema, it does the following:

For each source table from which OHSCDA extracts data,

• Identify what records have been created or modified in this table since the previous consolidation

• For each modified source record, drop the corresponding record in the consolidation table

• Insert all new and modified records in the Consolidation schema table, setting their StudyGUID, and modification timestamps

The procedures that does this work reside in each InForm Reporting and Analysis Schema, they are placed there as part of the process of preparing that schema for consolidation.

Preparation for consolidation also creates an access account in the database holding the source schema. This account is the one that reads the Reporting views, and writes to the consolidation tables. This access account is named CDAxxx, where xxx is the Study name.

All movement of data is done by a pull from the Reporting and Analysis Database to the Consolidation database. This ensures that there is no path by which someone who can connect to the consolidation schema is able to modify the InForm database.

The instructions that follow tell how to do the initial setup of the consolidation schema (this also enrolls the first Study to be consolidated as part of the process) and then how to set up each additional InForm study so that it becomes a contributor to the Consolidation schema.

2.1.2 Prerequisites

1. Download the OHSCDA patch (as required) from My Oracle Support (https://support.oracle.com). For information on the required patch, see Figure 2-1.

2. Unzip the downloaded patch.

3. Copy and unzip the Inform_Consolidate.zip file to a server from which it is possible to access all InForm source database that contain studies that are to be consolidated and also to access the database in which the consolidation schema is located.

2.1.3 Setting up Consolidation Schema

This section describes the steps to create the Consolidation Schema. As part of the process, it enrolls an initial InForm study as a source to be consolidated.

Note:

• If you are using the OHSCDA 3.0.0.2 patch, you must set up both the source trial and destination consolidation databases.

• If you are using the OHSCDA 3.0.0.4 patch, you must only set up the destination consolidation database.

2.1.3.1 Preparing TNSNAMES Files on Source Trial and Destination Consolidation Database Servers

If one does not already exist, create a TNSNAMES.ORA entry for the Consolidation database instance on each InForm database server that contains a study that is to be consolidated.

Note:

This is not essential. If you prefer not to create the TNSNAMES entries, you can provide the complete connection string instead of the TNS name when specifying remote databases below.

• On the consolidation schema database server, add a TNSNAMES.ORA entry for each source schema database.

2.1.3.2 Creating a Consolidation Management Root Directory

• On consolidation schema database server, create a root directory for managing the files needed to configure and log consolidation of the source schemas.

We will refer to this directory as <$ConsolidationMgmtRoot>.

If source trial and destination consolidation databases are in the same network, then a single <$ConsolidationMgmtRoot> is sufficient. Else, replicate the directory in both the servers.

During the setup of the source trial database, use TrialCDA and logs folders. And, during the setup of the destination consolidation database, use DestCDA and logs folder.

2.1.4 Initiating Consolidation of InForm Studies

This section describes the steps you must follow to prepare a source schema for consolidation and perform the initial execution of consolidation of that schema. Subsequent consolidations occurs automatically at an interval you define as part of the preparation described here.

The setup and configuration is performed in the following two phases for each study trial:

• Section 2.1.4.1, "Source Trial Database Configuration"

• Section 2.1.4.2, "Destination Consolidation Database Configuration"

2.1.4.1 Source Trial Database Configuration

Follow the instructions in this section for each InForm study that is to be consolidated for consumption by OHSCDA.

1. On either source trial or destination consolidation schema database server, based on the network architecture as described in Section 2.1.3.2, "Creating a Consolidation Management Root Directory", create the <Study-name> folder within <$ConsolidationMgmtRoot>/ to hold the files for consolidation of this study.

2. Copy the following folders from Inform_Consolidate.zip into <$ConsolidationMgmtRoot>/<Study-name>/:

   • TrialCDA

   • Logs

3. Set your current directory to the <$ConsolidationMgmtRoot>/<Study-name>/TrialCDA/ directory.

4. Edit CONFIGTRIALCDA.sql to set specific values of configuration parameters for this study. Make the following changes:

   Table 2-1 Source Trial Configuration Parameters

   Parameter	Set value to
   Slash	Use \ for Windows or / for Linux
   trial_name	The name of the study.
   inform_release	For InForm 4.6, enter R46. For later releases, enter R55.
   trial_tnsname	Name in the local TNSNAMES file of the source database for the study. Can also supply entire TNS entry for the source database as a string.
   trial_schema_user	Username of the InForm source schema.
   trial_schema_password	Password of the InForm source schema.
   trial_ro_user	This is OHSCDA reporting object schema user name and is defaulted to trail_name prefixed with 'cda'.
   trial_ro_password	This is OHSCDA reporting object schema password and is defaulted to trail_name prefixed with 'cda'. You can change this password.
   DDS_SCHEMA_OWNER	This is OHSCDA reporting object schema user name. This value must be same as the value you have entered for trial_ro_user.
   trial_dba_user	Database username who has the dba privileges.
   trial_dba_password	Password for database username.
   trial_ts	Name of a tablespace in the source schema database to which the access account for this study will be given access.
   trial_ts_temp	Name of a temporary tablespace in the source schema database to which the access account for this study will be given access.

   
   

5. Save the file.

6. From the SQLPlus prompt, execute the following:

   @Setup_Trial_CDA.sql
   

7. Navigate to the <$ConsolidationMgmtRoot>/<Study-name>/Logs directory to review the log.

   If any errors are found, make necessary corrections and re-execute Setup_Trial_CDA.sql.

2.1.4.2 Destination Consolidation Database Configuration

Follow the instructions in this section for each InForm study that is to be consolidated for consumption by OHSCDA.

1. On the consolidation schema database server, based on the network architecture as described in Section 2.1.3.2, "Creating a Consolidation Management Root Directory", create the <Study-name> folder within <$ConsolidationMgmtRoot>/ if the destination consolidation database is not in the same network as the source trial database.

   The <Study-name> folder holds the files for consolidation of this study.

2. Copy the following folders from Inform_Consolidate.zip into <$ConsolidationMgmtRoot>/<Study-name>/:

   Note:

   Do not copy the Logs folder if the destination consolidation database is in the same network as the source trial database.

   • DestCDA

   • Logs

3. Set your current directory to the <$ConsolidationMgmtRoot>/<Study-name>/DestCDA directory.

4. Edit CONFIGDESTCDA.sql to set specific values of configuration parameters for this study. Make the following changes:

   Note:

   If you prefer not to create the TNSNAMES entries, you can provide the complete connection string instead of the TNS name when specifying the remote databases below.

   The trial parameters mentioned in Table 2-2 must match with the ones defined in Table 2-1.

   Table 2-2 Destination Configuration Parameters

   Parameter	Set value to
   Slash	Use \ for Windows or / for Linux
   Parameters for configuring the source schema and database
   trial_name	The name of the study.
   inform_release	For InForm 4.6, enter R46. For later releases, enter R55.
   trial_tnsname	Name in the local TNSNAMES file of the source database for the study. Can also supply entire TNS entry for the source database as a string.
   trial_schema_user	Username of the InForm source schema.
   trial_global_name	Global name of the source schema database. You can get this by connecting to the source schema and running the following query: SELECT * FROM GLOBAL_NAME
   trial_ro_user	This is OHSCDA reporting object schema user name and is defaulted to trail_name prefixed with 'cda'.
   trial_ro_password	This is OHSCDA reporting object schema password and is defaulted to trail_name prefixed with 'cda'. You can change this password.
   Parameters for configuring the target schema and database
   dest_tnsname	Name of the target database in the TNSNAMES file on the source database server for the study. Can also supply entire TNS entry for the target database as a string.
   dest_schema_owner	This defaults to and is same as trial_ro_user parameter.
   dest_schema_password	This defaults to and is same trial_ro_password parameter.
   dest_consolidated_user	This is the consolidation schema username. Default is RXI_INFORM.
   dest_consolidated_password	This is the consolidation schema password. Defaults is RXI_INFORM. You can change this password.
   dest_dba_user	Database username who has dba privileges on the consolidation database.
   dest_dba_password	Password for the database username on the consolidation database.
   dest_ts	Name of a tablespace in the target schema database to which the consolidation and access account will be given access.
   dest_ts_temp	Name of a temporary tablespace in the target schema database to which the consolidation and access account will be given access.
   consolidate_job_interval	The interval between executions of the program to consolidate new and modified data from this study. A value of 1 results in an interval of one day. A value of 1/24 results in an interval of one hour.

   
   

5. Save the file.

6. From the SQLPlus prompt, execute the following:

   @Setup_Dest_CDA.sql
   

7. Navigate to the <$ConsolidationMgmtRoot>/<Study-name>/Logs directory to review the log.

   If any errors are found, make necessary corrections and re-execute Setup_Dest_CDA.sql.

2.1.5 Adjusting Scheduling of Consolidation Jobs

As mentioned earlier, initial consolidations, especially of large source schemas, should be done in isolation to avoid contention for resources. But once the initial consolidation of a schema is done, subsequent consolidations of that schema are incremental and involve smaller numbers of records (incremental consolidations are limited to new or modified Subjects, CRFs, and Queries accumulated since the previous consolidation).

Once initial consolidation of an InForm trial source schema is complete, it is useful to adjust the scheduling of its incremental consolidations so that they start near to the time of other incremental consolidation of other source schemas. The closer in time consolidations start across studies, the smaller the time period represented in the consolidation schema.

To adjust the time when a study's consolidation job executes, perform the following steps:

1. Connect as the InForm trial source schema owner.

2. Determine the consolidation job ID using the following query for InForm 4.6:

   • select job
     from user_jobs
     where what like 'REFRESH_PROCS.REFRESH_WITH_STREAMS_DELAY%';
     

   or the following query for InForm 5.5, 6.0, and 6.1:

   select job
   from user_jobs
   where what = 'CDA_PROCS.CONSOLIDATE';
   

3. Change the time for the next execution of the job by using the dbms_job.next_date procedure.

   Note:

   The next_date parameter is an Oracle date-time in which you can specify both the date and time for the next execution.

   Remember to follow the call with a commit. For example,

   begin
   dbms_job.next_date (
     job => 12345,
     next_date => to_date('21-AUG-2013@01:01:00','DD-MON-YYYY@HH24:MI:SS')
   );
   end;
   commit;
   /
   

   This causes job 12345 to next be executed at 1:01 AM on 21-AUG-2013.

You can also change the interval between subsequent executions of the job using the dbms_job.interval procedure. Set the interval parameter to the string 'SYSDATE + <desired-interval>', replacing <desired-interval> with the number of days, or the fraction of a day to elapse before the next execution.

begin
dbms_job.interval(
  job => 12345,
  interval => 'SYSDATE + 1/2'
);
end;
commit;
/

This sets the interval between executions of job 12345 to half a day or every 12 hours.

2.2 Running the OHSCDA Installer

The basic OHSCDA 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.

Note:

Same installer can be used for both install modes - fresh installation or upgrading from previous version.

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 OHSCDA 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.

   The Welcome screen provides information about the Oracle Universal Installer.

4. Click Next.

   The Specify Home Details screen appears.

5. Enter the name of the installation and path where all the staged files from the Installer get copied to the local system. This is also the location from where Installer executes the database script.

   Example Name: OCDAHome1

   Path: C:\OCDA

6. Click Next.

   The Install or Upgrade OHSCDA screen appears.

7. Select one of the following options:

   • Install: If you want to make a fresh installation of OHSCDA.

   • Upgrade: If you want to upgrade an existing OHSCDA 3.2 instance.

8. Click Next.

   The OCDA Data Warehouse Details screen appears.

9. Enter values in the following fields:

   • Database Host Name

   • Database Port No

   • Database Service Name

   • System Password

   • Default Tablespace Name

   • Temporary Tablespace Name

   • Enable National Language Support (NLS)

10. Click Next.

11. Enter values in the following fields:

    Note:

    The password must be alphanumeric and can contain only "_" or "#" special character.

    • OCDA Warehouse Schema (RXI) Password

    • OCDA Warehouse Schema (RXI) Confirm Password (Not applicable for Upgrade)

    • OCDA RPD (RXI_RPD) Password

    • OCDA RPD (RXI_RPD) Confirm Password (Not applicable for Upgrade)

12. Click Next.

    The Informatica PowerCenter Details screen appears.

13. Enter values in the following fields:

    • Informatica Repository Name

    • Informatica Domain Name

    • Informatica Host Name

    • Informatica Repository Port Number

    • Informatica Username with Admin Privileges

    • Informatica Password for Admin User

    • Confirm Informatica Password for Admin User

14. Click Next.

    The Informatica PowerCenter Client Home Directory screen appears.

15. Specify Informatica PowerCenter client Home directory. For example: C:\Informatica\9.6.1\clients\PowerCenterClient\client

16. Click Next.

17. Verify the details provided in the Summary screen.

18. Click Install.

    Note:

    You must record the log file path that appears on the bottom of the screen for future reference.

2.3 Source-specific Procedures

This section describes procedures you must perform for certain OHSCDA sources. Please review each section and determine if it applies to the source(s) you are using for OHSCDA. If the section does apply, carry out the procedure. If the section is optional, decide whether it is appropriate for your requirements and act accordingly.

2.3.1 Handling Deletions of Source Records

Different source applications handle the deletion of records in different ways. Oracle Clinical allows deletions of records in a way that avoids orphans, and has built-in auditing of these deletions. Siebel Clinical also allows deletions, properly cascading to maintain referential integrity, but does not have built-in auditing of deletions. InForm does not provide any means to hard-delete records in its transactional database. So, it does not need to be concerned neither with maintaining integrity in the face of deletions nor with auditing deletions.

2.3.1.1 Handling Deletions in Oracle Clinical

OHSCDA's ETL consults the audit trails to determine if source records have been deleted, and then soft-deletes those records in the warehouse.

2.3.1.2 Handling Deletions in Siebel Clinical

OHSCDA provides a feature to manage hard deletion of records in Siebel Clinical. Create triggers in the source system to handle deletion of records.

1. Navigate to the following temporary staging location where the OHSCDA installer copies the installation files:

   <OCDA_HOME>\OCDA_Common\OCDA_Common_Scripts\Delete_Script

2. Connect to the Siebel Clinical schema and run the ocda_sc_del_trigger.sql script delivered with OHSCDA. This script creates the triggers on tables provided as input. The following are the tables in Siebel Clinical for which OHSCDA supports creating triggers:

   • S_CL_PTCL_LS

   • S_PROD_INT

   • S_CL_SUBJ_LS

   • S_CONTACT

   • S_CL_PGM_LS

   • S_PTCL_SITE_LS

   • S_EVT_ACT

   • S_ORG_EXT

   • S_PTCL_VER_LS

   • S_ASSESS

   Provide a list of comma separated values of table names for which the triggers need to be created as the script's input. For example, S_CL_PTCL_LS, S_PROD_INT, and S_CL_SUBJ_LS. The tables names that you provide can only be a subset of the tables listed above.

   Note:

   When you delete a record in the table, the primary key of the deleted record is inserted in the RXI_DELETE_LOG_S table on the Siebel source system.

3. Set the values of the OHSCDA.DELETE_FLOW and DELETE_FLOW variables to Y while executing the load plan in ODI.

4. Execute the ETLs. For information, see Oracle Clinical Development Analytics Administrator's Guide.

   The Siebel Clinical related SDE mappings read the above instance of the RXI_DELETE_LOG_S table.

Note:

Records that are deleted in the source system are soft deleted in the data warehouse.

2.3.1.3 Handling Deletions in InForm

Since no deletions are supported through the InForm UI, OHSCDA makes no provision for detecting them. If you need to delete records from an InForm transactional table at the backend and want the OHSCDA warehouse to be consistent with that change, you must identify the warehouse records that arose from the InForm records that are to be deleted. Also, you must remove them from the consolidation schema and the warehouse.

2.3.2 (Optional) Handling Deletion or Deactivation of a Study

Depending on how you use OHSCDA, you may prefer to have reports that give information only on currently active studies. If so, and if source studies are completed or possibly deleted, the recommended approach for removing such a study from OHSCDA is to use OHSCDA's access control capability. That is, enable Study and Study-site access controls, and then exclude the study and its sites from the list of studies (and sites) available to OHSCDA users. Aside from being simpler than identifying and deleting records from the warehouse, this approach has the advantage of being reversible if the decision to remove the study from the warehouse is reconsidered.

If you do not wish to use access control to avoid display of deactivated or deleted studies, there is an alternative solution. In the OHSCDA warehouse, every dimension table, and every base fact table, has a column named DELETE_FLG. OHSCDA's OBIEE repository is designed to treat records where DELETE_FLG equals 'Y' as if they were not present in the warehouse. OHSCDA's SIL also disregards records with DELETE_FLG = 'Y' when calculating values for aggregate tables (those with names ending with _A). So you can cause records to be effectively removed from the warehouse by setting their DELETE_FLG to 'Y'. Thus, if a study has been removed from a source database, you could identify all dimension and fact records for that study, and set their DELETE_FLG to 'Y'. This causes them to be forever invisible to OHSCDA's analytics.

This solution could be used, but only with great caution, for a study that is considered to be deactivated, but still remains in the source. Once marked as deleted, warehouse records for a study will not get their DELETE_FLG set back to 'N', but OHSCDA creates new warehouse records if there are changes or additions in the source for that study. So, if the study is truly inactive in the source, soft-deleting warehouse records for the study by setting DELETE_FLG to 'Y' will work. But any changes or additions to the study would cause new records to be loaded into the warehouse for the study, and it would re-appear in analyses.

2.3.3 (Optional) Fine-tuning of Oracle Clinical Settings

To optimize source system integration with OHSCDA, perform the following steps:

1. For OC 4.6, navigate to Informatica Relational Connections > OC Connection Object > Attribute in Informatica Workflow Manager.

2. Set Connection Environment SQL value as:

   • For Oracle Database 11.2.0.2:

     alter session set optimizer_features_enable='11.2.0.2'
     

   • For Oracle Database 11.2.0.3:

     alter session set optimizer_features_enable='11.2.0.3'
     

   • For Oracle Database 11.1.0.7:

     alter session set optimizer_features_enable='11.1.0.7'
     

3. Create the following indexes on their respective Oracle Clinical tables:

   • Function based index on DISCREPANCY_ENTRIES - NVL ("MODIFICATION_TS", "CREATION_TS")

   • Function based index on DISCREPANCY_ENTRY_REVIEW_HIST - NVL ("NEXT_STATUS_TS", "CREATION_TS")

   • Function based index on RECEIVED_DCIS - NVL ("MODIFICATION_TS", "RECEIVED_DCI_ENTRY_TS")

   • Function based index on RECEIVED_DCMS - NVL ("MODIFICATION_TS", "RECEIVED_DCM_ENTRY_TS")

2.4 Setting Up Relational Connections in the Informatica Workflow for OHSCDA

For each database that will be a source for extracting data into the OHSCDA warehouse, perform the following steps to create a Relational Connection in the Informatica Workflow Manager:

1. Launch the Informatica PowerCenter Workflow Manager.

2. Connect to the repository where OHSCDA Informatica mappings are imported.

3. Select Connections, and then select Relational to display the Relational Connection Browser.

4. Click New to display the Select Subtype dialog.

5. Select Oracle as database type, and then click OK. The Connection Object Definition dialog box is displayed with options for the selected database platform.

6. Enter values in the following fields according to the Source database connection:

   • Connection Name: Enter the logical connection name.

   • User Name: Enter the user name that can access source data (For example, rxa_des for Oracle Clinical.)

   • Password: Enter the database password.

   • Connection String: Enter the Connect string for connecting to the database.

   • Code Page: Enter UTF-8 encoding of Unicode.

   Note:

   These values will also be required in setting up DAC. Make note of them to ensure that you enter the same during DAC setup.

   The TNS entry for all your source and target databases must be added on Informatica Server.

   Note:

   You must repeat steps 1 through 4 for each required source connection.

2.5 Preparing a DAC Repository for OHSCDA

1. Create a new DAC repository, as an Administrator.

2. Unzip OCDA_HOME\oracle.pharma.ocda.standard\DAC_Code\CDA_Warehouse.zip onto the computer where you will run DAC client.

3. Import the OHSCDA Warehouse Application metadata.

   1. Start the Data Warehouse Administration Console (DAC) client.

   2. From the Tools menu select DAC Repository Management, and then select Import.

   3. Click Change import/export folder to navigate to the folder where you unzipped CDA_Warehouse.zip in step 2 of Section 2.5, "Preparing a DAC Repository for OHSCDA".

   4. Click OK to display the Import dialog box.

   5. Select the following categories of metadata you want to import: Logical, Overwrite log file, and User Data. Deselect the User and System check boxes.

   6. Select CDA_Warehouse application in the ApplicationList.

   7. Click OK.

   8. Enter the verification code and click Yes in the secondary window that is displayed after the import.

   9. You can inspect the import log in ${DAC_ INSTALL_DIR}\log\import.log to verify if import is successful.

4. Configure Informatica Repository Service in DAC.

   1. Navigate to the Setup view, and then select the Informatica Servers tab.

   2. Click New to display the Edit tab below or select an existing Informatica server from the list.

      If you are configuring a new installation, the Informatica Servers tab will be empty. If you are upgrading an existing installation, the Informatica Servers tab might contain existing Informatica servers.

   3. Enter values in the following fields:

      - Name: Enter the Logical name for the Informatica server (for example, INFA_REP_SERVER).

      - Type: Select Repository.

      - Hostname: Enter the host system name where Informatica Server is installed.

      - Server Port: Enter the port number of the Informatica Server or Informatica Repository Server used to listen to requests.

      - Login: Enter the Informatica user login for the Admin user.

      - Password: Enter the Informatica Repository password.

      - Repository Name: Enter the Informatica Repository Name.

   4. Test the connection to verify the settings.

   5. Click Save to save the details.

5. Configure Informatica Integration Service in DAC.

   Note:

   Make sure that you use the same Login and Password that you have used in setting up Informatica.

   1. Click New to display the Edit tab below or select an existing Informatica server from the list.

      If you are configuring a new installation, the Informatica Servers tab will be empty. If you are upgrading an existing installation, the Informatica Servers tab might contain existing Informatica servers.

   2. Enter values in the following fields:

      - Name: Enter the Logical name for the Informatica server (for example, INFA_SERVER).

      - Type: Select Informatica.

      - Service Name: Enter the Informatica Integration service name associated with the Informatica repository added in Step 5.

      - Domain: Enter the Informatica domain name.

      - Login: Enter the Informatica Repository user login (Admin User).

      - Password: Enter the Informatica Repository password.

      - Repository Name: Enter the Informatica Repository Name.

   3. Test the connection to verify the settings.

   4. Click Save to save the details.

6. Configure source databases (Oracle Clinical, Siebel Clinical, and InForm) and the target database (the OHSCDA warehouse). For each database with which DAC will interact for OHSCDA, perform the following steps:

   1. Navigate to the Setup view, and then select the Physical Data Sources tab.

   2. Click New to display the Edit tab below or select an existing database connection from the list.

   3. Enter values in the following fields:

      - Name: Enter the logical name for the database connection.

      - Type: Select Source when you create the database connection for a transactional (OLTP) database. Select Warehouse when you create the database connection for a data warehouse (OLAP) database.

      - Connection Type: Select a connection type for the database connection.

      - Service Name: Enter the Data Mart database service name.

      - Table Owner: Enter the Data Mart schema name.

      - Table Owner Password: Enter the Data Mart schema password.

      - DB Host: Enter the Data Mart host name.

      - Port: Enter the Data Mart host port.

      - Dependency Priority: Enter the user-defined priority of the data source.

      - Data Source Number: Enter the user-defined number of the data source. Make sure the number is less than 100.

      - Num Parallel Indexes Per Table: Enter a number to specify how many indexes are to be created in parallel.

   4. Test the connection to verify the settings.

   5. Click Save to save the details.

   Note:

   By Default, Oracle supports Data Source Number 1, 2, and 3 for Oracle Clinical, Siebel Clinical, and InForm respectively.

   The logical Names of the connections in DAC must be same as the connection names created in Informatica Workflow Manager.

   OHSCDA Warehouse connection must be the same as provided during OHSCDA installation.

   Table 2-3 Sample of Data Source Table W_RXI_DATASOURCE_S

   ROW_WID	DATASOURCE_NUM_ID	DATASOURCE_NAME	DELETE_FLG	INTEGRATION_ID	ENTERPRISE_ID	INFORM_STUDY_GUID
   1	1	ORACLE_CLINICAL	N	ORACLE_CLINICAL	0	-
   2	2	SIEBEL_CLINICAL	N	SIEBEL_CLINICAL	0	-
   3	3	INFORM	N	INFORM	0	{FA5BCD87-B858-4F08-8BF8-1914B61C9DDF}
   4	101	INFORM_1	N	INFORM_1	0	{CC0DBD73-FA40-4943-BDB3-60752C1A2732}

   
   

   Note:

   If InForm is one of your sources and auto merge feature is not used, then the column INFORM_STUDY_GUID must be populated with studyguid for the corresponding InForm study.

   You can find the distinct studyguid from table RXI_STUDYVERSIONS in the consolidation database.

   From DAC, the value passed for the data source parameter is always 3. Since we have one consolidation DB which holds all study data, the guid, when auto merge is set to N, helps resolving individual data source numbers.

   If auto merge is set to Y, then a single entry for data source 3 for INFORM is sufficient and INFORM_STUDY_GUID need not be populated. In this case, the consolidation DB is considered as single source and duplicates are handled by auto merge.

7. Perform the following steps to modify the value for data sources:

   1. Navigate to the Execute view, and then select the Execution Plans tab.

   2. If Oracle Clinical, Siebel Clinical, and InForm are your source systems, select CDA - Complete Warehouse from the list.

      If Oracle Clinical is your only source system, select CDA - Oracle Clinical Warehouse from the list.

      If Siebel Clinical is your only source system, select CDA - Siebel Clinical Warehouse from the list.

      If InForm is your only source system, select CDA - InForm Warehouse from the list.

   3. Click Connectivity Parameters subtab in the bottom pane.

   4. For each row with TYPE equal to DATASOURCE, in the Value field, select the appropriate Physical Data Source Name from the drop-down list for the field.

   5. Select a relevant value from the list for each of the data sources.

   6. Click Save.

Note:

• If Oracle Clinical, Siebel Clinical, and InForm are your source systems, use CDA - Complete Warehouse.

• If Oracle Clinical is your only source system, use CDA - Oracle Clinical Warehouse.

• If Siebel Clinical is your only source system, use CDA - Siebel Clinical Warehouse.

• If InForm is your only source system, use CDA - InForm Warehouse.

2.5.1 DAC Configurable Parameters

Navigate to Design View and select CDA_Warehouse container from drop down. On Source System Parameters tab set values as mentioned in Table 2-4.

Table 2-4 lists the DAC configurable parameters.

Table 2-4 DAC Configurable Parameters

Parameter	Description
START_TS	This is the last refresh time of the source tables minus prune days. (@DAC_SOURCE_PRUNED_REFRESH_TIMESTAMP)
END_TS	Current Execution Plan's actual start time adjusted to source database time zone minus prune days. (@DAC_ETL_START_TIME_FOR_SOURCE)
DATASOURCE_NUM_ID	The ID associated with every source system. The default ID is 1 for Oracle Clinical, 2 for Siebel Clinical, and 3 for InForm.
ENTERPRISE_ID	The ID associated for every tenant. The default value is 0.
DELETE_FLOW	The default value is N and set it to Y if Deletes have to be captured in the data warehouse.
EMAIL_SUFFIX	You can provide domain name as a suffix to username. For example: oracle.com
Prune Days	This is used for setting the END_TS for incremental load.
MPI_AUTHFILE	Currently, not in use.
MPI_USER	Currently, not in use.
AUTO_MERGE_FLG	This is used to enable or disable auto-merge. Y: Enables auto-merge N: Disables auto-merge
$OutputFile_OCDA	Currently, not in use.
$DBConnection_SP_OLAP	Currently, not in use.
$DBConnection_OLAP	Currently, not in use.

2.6 Emplacing the OHSCDA Help and Image Files

You will be using help.zip and images.zip files in this section.

2.6.1 Placement of Files for Oracle WebLogic Managed Server

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

1. Navigate to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\ in Oracle WebLogic Server and create the s_ocda folder.

2. Copy the help.zip file from <OCDA_HOME>\OCDA_Common\Reporting\Help to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\s_ocda\.

3. Unzip the help.zip file such that the contents of help.zip (all htm files and folders) are placed under the <MIDDLEWARE_ HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServices Component\coreapplication_obips1\analyticsRes\s_ocda\help\ folder.

4. Move customMessages and sk_ocda folders from <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\s_ocda\help\ to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\.

5. Replace the tags within the UI tag with the following tags in instanceconfig.xml, present in <MIDDLEWARE_HOME>\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1:

   <DefaultSkin>ocda</DefaultSkin>
   <DefaultStyle>ocda</DefaultStyle>
   

6. Copy the Images.zip file from <OCDA_HOME>\OCDA_Common\Reporting\Images to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\s_ocda.

7. Unzip the Images.zip file such that the contents of Images.zip (all image files and folders) are placed under the <MIDDLEWARE_ HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServices Component\coreapplication_obips1\analyticsRes\s_ocda\images\ folder.

8. Launch Oracle WebLogic Administration Server Console. The following shows the format of the URL:

   https://<hostname>.<domain>:<port>/console
   

   The Oracle WebLogic Server Administration Console screen appears.

9. Log on to Oracle WebLogic Server Administration Console as an Administrator.

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

11. In the left pane, click Lock & Edit.

12. In the right pane, click Install.

    This opens the Install Application Assistant.

13. In the Path field, browse to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1.

14. Select analyticsRes and click Next.

15. Select Install this deployment as an application and click Next.

16. In Available targets for analyticsRes, under Clusters, select bi servers on which you want to deploy OHSCDA.

17. Click Next.

18. Select I will make the deployment accessible from the following location option for <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\ in the Source accessibility section.

19. Click Finish.

    analyticsRes appears in the Deployment section.

20. Click Activate Changes.

21. Select analyticsRes in the Deployment section.

22. Click Start to view the list and select Servicing all requests. The Start Application Assistant page is displayed.

23. In the content pane of the new page, click Yes to start the selected deployment.

    State of analyticsRes should be Active after this deployment. You may confirm the same on Deployments page.

24. Log out from Oracle WebLogic Server Administration Console.

25. Log on to Oracle Enterprise Manager Fusion Middleware Control. The following shows the format of the URL:

    https://<hostname>.<domain>:<port>/em
    

26. Restart the BI components.

27. Log on to OBIEE and verify the branding and help links on the dashboards.

See Also:

• Oracle WebLogic Server Documentation Library

2.7 Preparing the OBIEE Web Catalog and Repository for OHSCDA

1. Copy the OCDA.zip file from <OCDA_HOME>\OCDA_Common\Reporting\Webcat to the OBIEE server.

2. Copy the OCDA.rpd file from <OCDA_HOME>\OCDA_Common\Reporting\RPD to the OBIEE server.

3. Unzip the OCDA.zip file in the <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog directory.

4. In the Oracle BI Administration Tool, select File, then Open, and then Offline.

5. Navigate to the OCDA.rpd file, and then click Open.

   Password: Admin123

6. Click OK.

7. In the Oracle BI Administration Tool, select File, and then select Change Password.

8. Enter the current (old) password.

9. Enter the new password and confirm it.

10. Confirm the new password.

11. Click OK.

12. Modify the connection pools in the RPD as following:

    1. In the physical layer, expand the OCDA Data Warehouse node and double-click the Connection Pool object.

       The Connection Pool dialog box appears.

    2. In the following string under the Data source name field, replace <hostname>, <port_number>, and <SID_NAME> with the host name, port number, and SID name of the database:

       (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<port_number>))(CONNECT_DATA=(SID=<SID_NAME>)))
       

    3. Change the username to the username of the OHSCDA read-only DW RPD schema name.

    4. Change the password to the password of the OHSCDA read-only DW RPD schema password.

    5. Click OK.

    6. Reconfirm the password.

    7. Click OK.

    8. In the physical layer, expand the OCDA Data Warehouse node and double-click the OCDA_CP_InitBlocks object.

    9. Repeat steps b through h.

13. From the File menu, select Save to save the rpd.

14. Click Yes for Do you wish to check global consistency?

15. Click Close in the Consistency Check Manager.

16. Click Save.

17. Click File and then click Close.

18. Click File and then click Exit.

19. Open NQSConfig.INI found at <MIDDLEWARE_HOME>instances\<instancename>\config\OracleBIServerComponent\coreapplication_obis1.

20. Set EVALUATE_SUPPORT_LEVEL =2.

21. Restart the Oracle WebLogic Server and BI components.

22. Open the Fusion Middleware Control URL from the system where you saved the OCDA.rpd in step 13. The URL includes the name of the host and the port number assigned during the installation. The following shows the format of the URL:

    https://<hostname>.<domain>:<port>/em

    The login page appears.

    Note:

    Oracle recommends that you enable HTTPS on middle-tier computers that are hosting the Web services, since otherwise the trusted user name and password that are passed can be intercepted.

23. Enter the Oracle Fusion Middleware administrator user name and password and click Login.

24. Expand the Business Intelligence folder and select the coreapplication node.

    The Overview page displays the current status of the system, by providing information about current availability, performance, and issues identified within the BI domain. The Overview page also enables you to start and stop Oracle Business Intelligence.

25. Navigate to the Repository tab of the Deployment page.

26. Click Lock and Edit Configuration.

27. Click Close.

28. In the Upload BI Server Repository section, click Browse and navigate to select the RPD.

29. Enter the RPD password in the Repository Password and Confirm Password fields.

30. In the BI Presentation Catalog section, enter the following (as applicable) in the Catalog Location field:

    <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\OCDA

31. Click Apply, and then click Activate Changes.

32. Return to the Business Intelligence Overview page and click Restart.

33. Log on to OBIEE Analytics. The following shows the format of the URL:

    https://<hostname>.<domain>:<port>/analytics

    If you get an authentication error, perform the following steps:

    1. Stop all opmn processes. Execute the following command from <MIDDLEWARE_HOME>\instances\<instancename>\bin:

       opmnctl stopall
       

    2. Update the NQSConfig.INI file found at <MIDDLEWARE_HOME>instances\<instancename>\config\OracleBIServerComponent\coreapplication_obis1.

       FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = YES;
       

       By default, the value of FMW_UPDATE_ROLE_AND_USER_REF_GUIDS is No.

    3. Add the following tag within the catalog tag in the instanceconfig.xml file found at <MIDDLEWARE_HOME>\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1:

       <UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
       

    4. Start all opmn processes. Execute the following command from <MIDDLEWARE_HOME>\instances\<instancename>\bin:

       opmnctl startall
       

    5. Stop all opmn processes. Execute the following command from <MIDDLEWARE_HOME>\instances\<instancename>\bin:

       opmnctl stopall
       

    6. Update the NQSConfig.INI file found at <MIDDLEWARE_HOME>instances\<instancename>\config\OracleBIServerComponent\coreapplication_obis1.

       FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO;
       

    7. Delete the following tag within the catalog tag in the instanceconfig.xml file found at <MIDDLEWARE_HOME>\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1:

       <UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
       

    8. Start all opmn processes. Execute the following command from <MIDDLEWARE_HOME>\instances\<instancename>\bin:

       opmnctl startall
       

2.8 Configuring HTML 5

1. Navigate to <MIDDLEWARE_HOME>\instances\<instancename>\config\OracleBIPresentationServicesComponent\coreapplication_obips1.

2. Open instanceconfig.xml.

3. Within the <Views> tag, add the following:

   <Charts>
   <DefaultWebImageType>html5</DefaultWebImageType>
   </Charts>
   

4. Restart the presentation services.

2.9 Configuring Maps

To configure maps:

1. Go to http://www.oracle.com/technetwork/middleware/bi-foundation/obieesamplesarchive-2026956.html.

2. Navigate to OBIEE 11.1.1.3 - Sample Application.

3. Click Documentation Downloads.

4. Click Save.

5. Unzip the folder.

6. Open SampleApp_Deploy_Instructions_825.pdf and see section 6 Deploying SampleApp Mapviewer Content for instructions on how to configure maps.

2.10 Creating Security Groups and Application Roles for OHSCDA

2.10.1 Creating Groups

Perform the following steps to create groups:

1. Launch Oracle WebLogic Server Administration Console.

2. In Oracle WebLogic Server Administration Console, select Security Realms from the left pane and click the realm you are configuring. For example, myrealm.

3. Select Users and Groups tab, then Groups.

4. Click New.

5. In the Create a New Group page, provide the following information:

   • Name: Enter the name of the group. Group names are case insensitive but must be unique. See online help for a list of invalid characters.

   • (Optional) Description: Enter a description.

   • Provider: Select the authentication provider from the list that corresponds to the identity store where the group information is contained. DefaultAuthenticator is the name for the default authentication provider.

6. Click OK.

   The group name is added to the Groups table.

7. Repeat step 4 through 6 with the following values:

   Table 2-5 Security Group Parameters

   Name	Description	Provider
   OCDA-CRA	(Optional)	DefaultAuthenticator
   OCDA-DataManager	(Optional)	DefaultAuthenticator
   OCDA-ExecutiveManager	(Optional)	DefaultAuthenticator
   OCDA-RegionManager	(Optional)	DefaultAuthenticator
   OCDA-StudyManager	(Optional)	DefaultAuthenticator
   OCDA-WebcatAdim	(Optional)	DefaultAuthenticator

   
   

2.10.2 Creating Application Roles

Perform the following steps to create groups:

1. Log on to Oracle Enterprise Manager Fusion Middleware Control. The following shows the format of the URL:

   https://<hostname>.<domain>:<port>/em

2. From the target navigation pane, open Business Intelligence.

3. Right-click coreapplication, then select Security > Application Roles.

   The Application Roles page is displayed.

4. Click Create to display the Create Application Role page. Complete the fields as follows:

   In the General section:

   • Role Name - Enter the name of the Application Role.

   • (Optional) Display Name - Enter the display name for the Application Role.

   • (Optional) Description - Enter a description for the Application Role.

5. In the Members section, click Add.

   1. In the dialog box that appears, click the blue button to search.

      The list containing all groups is displayed.

   2. Select a group from the list.

   3. Click OK.

6. Repeat steps 4 and 5 for all the Roles listed in the following table:

   Table 2-6 Application Roles and Groups

   Role Name	Description	Groups
   OCDA-CRA	(Optional)	OCDA-CRA
   OCDA-DataManager	(Optional)	OCDA-DataManager
   OCDA-ExecutiveManager	(Optional)	OCDA-ExecutiveManager
   OCDA-RegionManager	(Optional)	OCDA-RegionManager
   OCDA-StudyManager	(Optional)	OCDA-StudyManager
   OCDA-WebcatAdim	(Optional)	OCDA-WebcatAdim

   
   

7. Click OK.