3 Post Installation Tasks

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

• Creating Informatica Error Logging and Oracle Health Sciences Clinical Development Analytics Auxiliary Tables

• Setting Up Service Locations

• Setting Up Remote Locations in Oracle Life Sciences Data Hub

• Setting Up the Source System

• Managing Source System Specific Requirements

• Loading Oracle Health Sciences Clinical Development Analytics Seed Tables

• Setting Oracle Health Sciences Clinical Development Analytics Repository Password

• Creating Security Groups and Application Roles for CDA

• Emplacing the CDA Help and Image Files

• Preparing the OBIEE Web Catalog and Repository for CDA

• Post Installation Tasks for Deduplication

3.1 Creating Informatica Error Logging and Oracle Health Sciences 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 CDA.

Both the script files are available in the staging area for Windows installer.

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.

3.2 Setting Up Service Locations

The following services must be available in CDA:

• OBIEE services

• Informatica service

See Also:

• Oracle Life Sciences Data Hub System Administrator's Guide (Defining Service Locations section in Chapter 1, Setting Up Services), for more information on setting up service locations in Oracle LSH.

• Oracle Life Sciences Data Hub Installation Guide (Integrating Informatica with the Oracle Life Sciences Data Hub section in Chapter 8, Integrating with Other Systems), for more information on setting up Informatica services in Oracle LSH.

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

You use Oracle LSH to set up the services for CDA. 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.

Ensure that the Number of Service Instances parameter is as given below. In LSH, navigate to Administration > service locations. Following are values for:

Informatica service location:

Table 3-1 Values for Informatica Service Location

Service Type	Priority	Status	Number of Service Instances
Informatica for Development	Normal	Enabled	50
Informatica	Normal	Enabled	150

PLSQL service location:

Table 3-2 Values for PLSQL Service Location

Service Type	Priority	Status	Number of Service Instances
PLSQL for Development	Normal	Enabled	10
PLSQL	Normal	Enabled	30

3.3 Setting Up Remote Locations in Oracle Life Sciences Data Hub

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

• OCDA_OC_OLTP_RL is the remote location using which you connect to the source Oracle Clinical database to extract data. Configure this remote location, if you use Oracle Clinical as your data source.

• OCDA_SC_OLTP_RL is the remote location using which you connect to the source Siebel Clinical database to extract data. Configure this remote location, if you use Siebel Clinical as your data source.

• OCDA_CUSTOM_OLTP_RL is the remote location to RXI schema, which has OCDA-specific tables. Irrespective of the data source, configure this remote location.

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

3.3.2 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-3 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-4 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-5 Connections for OCDA_CUSTOM_OLTP_RL

Name	User Name	Password
RXI	RXI	Password to access the RXI schema.

• Click Apply.

• Repeat for each connection.

• 3.3.3 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 through 7 for OCDA_OC_RXC_LS and OCDA_OC_OPA_LS.

  11. Select OCDA_OC_OLTP_RL/RXCand OCDA_OC_OLTP_RL/OPA for their respective load sets.

  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.

  3.4 Setting Up the Source System

  By default, CDA 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:

  3.4.1 Creating Source Configuration Schema and Tables

  The following steps create a user and replica of Oracle Clinical and Siebel Clinical empty source tables:

  1. Log in to Oracle LSH as a system user.

  2. Execute OCDA_SRC_CONFIG_USER_TABS.sql script from the temporary staging location.

     This prompts you to enter the following information:

     • Password for 'OCDA_CONFIG' Schema user: Enter the Password for OCDA_CONFIG schema user.

     • DEFAULT_TABLESPACE: Enter the default tablespace name.

     • TEMP_TABLESPACE: Enter the temporary tablespace name.

  3. Create a new remote location in Oracle LSH with the name OCDA_CONFIG_RL, pointing to the Oracle LSH database. Refer to Configuring Remote Locations for Passthrough Views, for more details.

  4. Follow the steps in Configuring Connections, to create a connection to the schema OCDA_SRC_CONFIG.

  If you are disabling Oracle Clinical, 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_CONFIG_RL/OCDA_CONFIG.

  9. Click Apply.

  10. Repeat step 4 through 7 for OCDA_OC_RXC_LS and OCDA_OC_OPA_LS.

  11. Reinstall the work area containing the load set and passthrough views in Full mode.

  If you are disabling Siebel Clinical, 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 for Remote Location field.

  8. Select OCDA_CONFIG_RL/OCDA_CONFIG.

  9. Click Apply.

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

  To Install the OCDA_UTIL_WA Workarea and Execute the Source Configuration Script

  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 to disable. The possible values are:

       1 - ORACLE CLINICAL

       2 - SIEBEL CLINICAL

       3 - Exit

  3.5 Managing Source System Specific Requirements

  3.5.1 Fine-tuning Oracle Clinical Settings

  To optimize source system integration with CDA, perform the following:

  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 :

     • Oracle Database 11.2.0.2 - alter session set optimizer_features_enable='11.2.0.2'

     • 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")

  3.5.2 Handling Deletions in Siebel Clinical

  CDA provides an optional feature to manage hard deletion of records in Siebel Clinical. You create triggers in the source system to handle deletion of records. To do this:

  1. Navigate to the temporary staging location where the CDA installer copies the installation files.

  2. Connect to the Siebel Clinical data source and run the OCDA_HOME/oracle.pharma.ocda.standard/Delete_Script/ocda_sc_del_triggers.sql script delivered with CDA. This script creates the RXI_DELETE_LOG_S table and triggers on tables provided as input. The following are the tables in Siebel Clinical for which CDA 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

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

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

  3.6 Loading Oracle Health Sciences 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.

  3.7 Executing Oracle Life Sciences Data Hub Workarea Installation Script

  Perform following steps before running the work area install script.

  1. Navigate to OCDA_domain > OCDA_CODE_APP_AREA > OCDA_WORK_AREA

  2. Select table instance W_LOV_D.

  3. Check out the table instance.

  4. Select the Constraints/Indexes tab.

  5. Select W_LOV_D_U2 constraint and remove it.

  6. Navigate to OCDA_domain > OCDA_CODE_APP_AREA > OCDA_WORK_AREA.

  7. Select table instance OCDA_INFA_Party_Dim_SIL_PRG.

  8. Check out the program instance.

  9. Select the Table Descriptors tab.

  10. Select W_HS_MAPPING_S table descriptor and remove it.

  11. Partially install OCDA_INFA_Party_Dim_SIL_PRG program instance and the W_LOV_D table instance.

  Ensure that all the work areas in OCDA_domain are in Status Installable.

  The exception OCDA_DWH_WA can be ignored as this is used to fetch definition and is not used during ETL execution.

  On the Oracle LSH database server, navigate to the directory where OCDA_domain.zip is placed in staging area, and run the following work area (WA) installation script:

  sqlplus apps/<apps_password>@<DB_INSTANCE> @../cdrruwainstall.sql <LSH_APPL_USER> <DB_DIRECTORY> OCDA_domain.zip

  where:

  <DB_INSTANCE> is the service name for the database where Oracle LSH is installed.

  <LSH_APPL_USER> is the LSH user account as created in the Creating an Oracle Life Sciences Data Hub User Account.

  <DB_DIRECTORY> is the logical DB directory name mapped to the Operating System (OS) directory containing the OCDA_domain.zip to be imported.

  Note:

  Use the ocda_domain_import.log file to verify if the script has executed successfully.

  3.8 Setting Oracle Health Sciences Clinical Development Analytics Repository Password

  The default Administrator password for the CDA repository file (rpd) is Admin123. To set this default password in the deployed repository file, you must ensure that you set the Administrator password as Admin123 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 Section 3.8.1, 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 Admin123. Perform steps listed in Section 3.8.2, Creating an OBIEE Remote Location Connection.

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

     Note:

     Ensure that the work area status is Installable, else navigate to Business Area Instance OCDA Data Warehouse. Map table descriptors to their target table instances in OCDA_domain > OCDA_CODE_APP_AREA > OCDA_WORK_AREA.

  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 CDA Business Area. For more information about modifying the CDA repository file, refer to Oracle Health Sciences 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 CDA Business Area.

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

  3.8.2 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 Admin123 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 Administrator Guide (Chapter 3, Implementing Security), for more information on implementing security in CDA.

  3.9 Creating Security Groups and Application Roles for CDA

  3.9.1 Creating Groups

  Perform the following 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 Group table.

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

     Table 3-6 Security Group Parameters

     Name	Description	Provider
     OCDA-CRA	(Optional)	DefaultAuthenticator
     OCDA-StudyManager	(Optional)	DefaultAuthenticator
     OCDA-DataManager	(Optional)	DefaultAuthenticator
     OCDA-ProjectManager	(Optional)	DefaultAuthenticator
     OCDA-WebcatAdmin	(Optional)	DefaultAuthenticator

     
     

  3.9.2 Creating Application Roles

  Perform the following to create groups:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. From the target navigation pane, open Business Intelligence and select coreapplication.

  3. Right-click coreapplication, then select Security to display a submenu with Application Policies and Application Roles as options.

  4. Select Application Roles. The Application Roles page is displayed.

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

  6. In the Members section, select Add Group. To search in the dialog box that displays:

     1. Click the blue button to search. It will display a list of all the groups.

     2. Select from the results returned in the Available box.

     3. Use the shuttle controls to move the desired name to the Selected box.

     4. Click OK to return to the Create Application Role page.

     5. Repeat steps 5 through 9 for all the Roles listed in the following table:

        Table 3-7 Application Roles and Groups

        Role Name	Description	Groups
        OCDA-CRA	(Optional)	OCDA-CRA
        OCDA-StudyManager	(Optional)	OCDA-StudyManager
        OCDA-DataManager	(Optional)	OCDA-DataManager
        OCDA-ProjectManager	(Optional)	OCDA-ProjectManager
        OCDA-WebcatAdmin	(Optional)	OCDA-WebcatAdmin

        
        

  3.10 Emplacing the CDA Help and Image Files

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

  3.10.1 File Placement for Oracle WebLogic Managed Server

  You need to manually deploy CDA'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.

  2. Create the following folders at <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\

     • s_ocda

  3. Unzip help.zip from OCDA_Home\oracle.pharma.ocda.standard\Reporting\Help to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\s_ocda\

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

  5. Add the following tag in instanceconfig.xml:

     <UI><DefaultSkin>ocda</DefaultSkin></UI>

     The file can be found in ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn.

  6. Unzip the Images.zip files from OCDA_Home\oracle.pharma.ocda.standard\Reporting\Images to <MIDDLEWARE_HOME>\instances\<instancename>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\s_ocda

  7. Launch Oracle WebLogic Administration Server Console.

     Example: https://hostname.domain:port/console

     This opens the Oracle WebLogic Server Administration Console.

  8. Log in to Oracle WebLogic Server Administration Console as an Administrator.

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

  10. On the left pane, click Lock & Edit.

  11. In the right pane, click Install.

      This opens the Install Application Assistant.

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

  13. Select analyticsRes and click Next.

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

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

  16. Click Next.

  17. In the Deployment targets, select bi_server1.

  18. Click Next.

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

  20. Click Finish. analyticsRes should appear under the Deployments.

  21. Click Activate Changes.

  22. Select analyticsRes in Deployment section.

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

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

  25. Log out from Oracle WebLogic Server Administration Console.

  26. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  27. Restart the BI components.

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

  See Also:

  • Oracle WebLogic Server Documentation Library

  3.11 Preparing the OBIEE Web Catalog and Repository for CDA

  You will be using OracleClinicalDevelopmentAnalytics.zip and OCDA.rpd files in this section.

  1. Copy OracleClinicalDevelopmentAnalytics.zip from <CDA_Home>\Reporting\Webcat to OBIEE server.

  2. Copy OCDA.rpd files from the location where the RPD was deployed in the sectionSetting Oracle Health Sciences Clinical Development Analytics Repository Password to OBIEE server.

  3. Unzip OCDA.zip in the following folder:

     • Windows32 - <DRIVE>:\<MIDDLEWARE_HOME>\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog

     • UNIX - /<MIDDLEWARE_HOME>/instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog

  4. For fresh installation, create a TNS entry of CDA database in %ORACLE_BI%\network\admin.

  5. Create an ODBC entry (System DSN ) to connect to (RXI) using Oracle Database 11g client driver.

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

  7. Navigate to the OCDA.rpd, and then click Open.

     Password: Admin123

  8. Click OK.

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

  10. Enter the current (old) password.

  11. Enter the new password and confirm it.

  12. Confirm the new password.

  13. Click OK.

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

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

  16. Click Close in the Consistency Check Manager.

  17. Click Save.

  18. Click File and then click Close.

  19. Click File and then click Exit.

  20. Start the Oracle WebLogic Server and BI components.

  21. 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 is displayed.

      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.

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

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

• Navigate the Repository tab of the Deployment page.

• Click Lock and Edit Configuration.

• Click Close.

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

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

• In the BI Presentation Catalog section, for Catalog Location field, enter<ORACLE_INSTANCE>/bifoundation/OracleBIPresentationServicesComponent/<COMPONENT_NAME>/catalog/OCDA.

• Click Apply, then click Activate Changes.

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

• 3.12 Post Installation Tasks for Deduplication

  Perform the following post installation tasks if you plan to use deduplication:

  3.12.1 Deploying OCDA_PLS_ETL_WORKFLOW_PROC.SQL

  1. Log in using the user account created in Creating Oracle Life Sciences Data Hub Database Accounts.

  2. Execute OCDA_PLS_ETL_WORKFLOW_PROC.SQL script from the temporary staging location for Windows installer.

     This script creates a procedure that invokes OCDA_PLS_ETL_WORKFLOW_PRG using LSH Message-Based Submissions.

  3.12.2 Setting Up Relational Connections in the Informatica Workflow for CDA

  1. Perform the following to create the Relational Connections for Source Databases in Informatica Workflow Manager:

     1. Launch Informatica PowerCenter Workflow Manager.

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

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

     4. Click New to display the Select Subtype dialog.

     5. Select Oracle as database type, 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 should be added on Informatica Server.

  Note:

  You need to repeat step a through d for each required source connection.

• Connect to Informatica PowerCenter Administration Console.

• Connect to the Informatica integration service.

• Navigate to the Custom Properties window.

• Enter AggSupprtWithNoPartLic in the Name field.

• Enter Yes in the Value field.

• 3.12.3 Preparing a DAC Repository for CDA

  You will be using CDA_Warehouse.zip file in this section.

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

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

  3. Import the CDA 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 the Preparing a DAC Repository for CDA section.

     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 System check box.

     6. If you plan to implement deduplication, select all the applications in the ApplicationList.

     7. Click OK.

     8. Enter the verification code and 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. Set task level parameter in DAC to trigger OCDA_PLS_ETL_WORKFLOW_PRG using Message-Based Submissions in Oracle LSH.

     1. Select CDA_Employee_De_Dup application in the ApplicationList.

     2. Click Tasks tab in the top pane.

     3. Select the task PLP_Start_LSH_MasterProgram.

     4. Click Parameters subtab in the bottom pane.

     5. Set values for the following parameters:

        Table 3-8 Individual Parameters

        Parameter	Value
        PIN_DOMAIN	OCDA_domain
        PIN_APP_AREA	OCDA_UTIL_APP_AREA
        PIN_WORKAREA	OCDA_ETL_WORKFLOW_WA
        PIN_PROGRAM	OCDA_PLS_ETL_WORKFLOW_PRG
        PIN_EXESETUP	OCDA_ES This execution setup in Oracle LSH needs to have Property Triggered Under system parameters. This is used to trigger the OCDA master program, OCDA_PLS_ETL_WORKFLOW_PRG, using Message-Based Submissions in Oracle LSH.
        PIN_USERID	[e-mail] This is Oracle LSH application user who has access to OCDA_domain and also has privileges to execute the ETL. Make sure that you have a Oracle LSH User Database Account created for the user.
        PIN_FL	Y Caution: This parameter must be set to N after the initial load else entire warehouse data will be truncated. Only incremental data will be available which is part of the current load.

        
        

  5. Configure Informatica Repository Service in DAC.

     1. Navigate to the Setup view, 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 Informatica Server or Informatica Repository Server use 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.

  6. 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 — 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.

• In this step, you configure source databases (Oracle Clinical, Siebel Clinical) and the target database (the CDA warehouse). For each database with which DAC will interact for CDA, perform the following steps:

  1. Navigate to the Setup view, 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. Select Others when you create the database connection for OHMPI schema.

     Connection Type — Select a connection type for the database connection.

     Instance or TNS Name — Enter the Data Mart database instance 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.

     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 and 2 for Oracle Clinical and Siebel Clinical respectively.

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

  CDA Warehouse connection name should be RXI.

• If you plan to implement deduplication, create the physical data source connections with following details in DAC:

  Type: Other

  Connection Type: Oracle (Thin)

  Instance: Instance name of the database

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

  Data Source Number: Enter the user-defined number of the data source.

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

  Table 3-9 Physical Data Source Connection Details

  Name	Table Owner
  OHMPI_STUDY	ohmpi_study
  OHMPI_STUDY_SITE	ohmpi_study_site
  OHMPI_STUDY_SUBJ	ohmpi_study_subj
  OHMPI_GEO	ohmpi_geo
  OHMPI_LOV	ohmpi_lov
  OHMPI_SITE	ohmpi_site
  OHMPI_INVESTIGATOR	ohmpi_investigator
  OHMPI_USER	ohmpi_user
  OHMPI_VALDTN_PROC	ohmpi_valdtn_proc
  OHMPI_PRODUCT	ohmpi_product
  OHMPI_PROGRAM	ohmpi_program
  OHMPI_APP_USER	ohmpi_app_user
  OHMPI_STUDY_REGION	ohmpi_study_region
  OHMPI_CRF	ohmpi_crf
  OHMPI_CRF_BOOK	ohmpi_crf_book
  LSH_DB_USER	< Oracle LSH Database User Account>

  
  

  Note:

  Table Owner Password for all the OHMPI_<dim> connections is the same as the Master password provided on OHMPI screen during CDA installation.

  Table Owner for LSH DB USER is the account information which is used to execute the ETL jobs in Oracle LSH. Refer to Creating Oracle Life Sciences Data Hub Database Accountsfor more information about creating the database user.

• If you plan to implement deduplication, create a Flat File connection with the following details:

  Name: FlatFile_Target

  Type: Other

  Connection Type: Flat File

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

  Data Source Number : Enter the user-defined number of the data source.

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

• Perform the following steps to modify the value for data sources:

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

  2. If Oracle Clinical and Siebel Clinical are your source systems, selectCDA - Complete Initial De Dup Execution Plan and CDA - Complete Warehouse De Dup Execution Plan from the list.

     If Oracle Clinical is your only source system, selectCDA - Oracle Clinical Warehouse De Dup from the list.

     If Siebel Clinical is your only source system, selectCDA - Siebel Clinical Warehouse De Dup from the list.

  3. Click 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 dropdown list for the field.

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

  6. Click Save.

  7. If you plan to implement deduplication, navigate to CDA - Complete Warehouse De Dup and set the new Data Source Name from Value list.

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

  9. Click Save.

• Note:

  If Oracle Clinical and Siebel Clinical are your source systems with deduplication, use CDA - Complete Initial De Dup Execution Plan and CDA - Complete Warehouse De Dup Execution Plan.

  DAC Configurable Parameters

  Navigate to each of the containers and make sure that values are set for each of the available parameter.

  Following is the list of DAC configurable parameters:

  Table 3-10 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 and 2 for Siebel Clinical.
  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	Location of the ocda.properties. Refer to Section 3.12.6, "Setting Up Informatica Server" for file details. For example: /u01/oracle/Informatica/9.0.1/server/infa_shared/OCDA_Javalib/ocda.properties
  MPI_USER	Login name of the user who can access EJBs deployed on Oracle WebLogic Server (same user that was provided on WebLogic screen during CDA installation).
  $OutputFile_OCDA	Location of the flat files generated as part of full dedup load on Informatica server.
  $DBConnection_SP_OLAP	Database connection name of the corresponding OHMPI schema.
  $DBConnection_OLAP	Database connection name of the warehouse (CDA Warehouse Target Connect Name you had specified during installation).

  
  

  Note:

  MPI_AUTHFILE, MPI_USER, $OutputFile_OCDA, $DBConnection_SP_OLAP, and $DBConnection_OLAP are used only for deduplication.

  3.12.4 Creating Security Groups and Application Roles for CDA

  3.12.4.1 Creating Groups

  Perform the following 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 Group table.

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

     Table 3-11 Security Group Parameters

     Name	Description	Provider
     OCDA-CRA	(Optional)	DefaultAuthenticator
     OCDA-StudyManager	(Optional)	DefaultAuthenticator
     OCDA-DataManager	(Optional)	DefaultAuthenticator
     OCDA-ProjectManager	(Optional)	DefaultAuthenticator
     OCDA-WebcatAdmin	(Optional)	DefaultAuthenticator

     
     

  3.12.4.2 Creating Application Roles

  Perform the following to create groups:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. From the target navigation pane, open Business Intelligence and select coreapplication.

  3. Right-click coreapplication, then select Security to display a submenu with Application Policies and Application Roles as options.

  4. Select Application Roles. The Application Roles page is displayed.

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

  6. In the Members section, select Add Group. To search in the dialog box that displays:

     1. Click the blue button to search. It will display a list of all the groups.

     2. Select from the results returned in the Available box.

     3. Use the shuttle controls to move the desired name to the Selected box.

     4. Click OK to return to the Create Application Role page.

     5. Repeat steps 5 through 9 for all the Roles listed in the following table:

        Table 3-12 Application Roles and Groups

        Role Name	Description	Groups
        OCDA-CRA	(Optional)	OCDA-CRA
        OCDA-StudyManager	(Optional)	OCDA-StudyManager
        OCDA-DataManager	(Optional)	OCDA-DataManager
        OCDA-ProjectManager	(Optional)	OCDA-ProjectManager
        OCDA-WebcatAdmin	(Optional)	OCDA-WebcatAdmin

        
        

  3.12.5 Setting Up OHMPI Projects (Optional)

  Follow the steps in this section only if you plan to implement deduplication. You must install Oracle client on the system where you intend to carry out OHMPI related cleanser and loader process. To set up OHMPI projects:

  1. Navigate to OCDA Home.

  2. Locate the zipped OHMPI Project files and move all the zipped files to a system where you plan to import and modify projects using Netbeans.

  3. Copy and unzip all the 15 project files.

  4. On the NetBeans toolbar, click Open Project.

  5. Navigate to the folder where the OHMPI projects are unzipped.

  6. Select a project.

  7. Select the check box Open Required Projects and click Open Project.

  8. Once the project is imported, right-click the main project file (OCDA_<dim>) in the Projects window.

  9. Right-click the same project and select Clean.

  10. Right-click and select Generate Master Index Files.

  11. Right-click and select Build.

  12. Navigate to <project_home>/src/DatabaseScript, where project_home is the location of the master person index project files.

  13. Connect to the project specific database schema, for example, for OCDA_Study project use ohmpi_study as username and the master password provided on Oracle Healthcare Master Person Index screen during OHSCDA installationon.

  14. Execute the following files in the following order:

      1. create.sql

      2. systems.sql

         Note:

         The systemcode in systems.sql must be same as data source name provided in W_RXI_DATASOURCE_S. Note that systemcode is case-sensitive.

• codelist.sql

• Important:

  For OCDA_Geography project, execute Create_with_LID_changes.sql instead of create.sql.

  For OCDA_User project, execute create_lidchange.sql instead of create.sql.

• Repeat steps 4 through 14 for each of the 15 OHMPI projects.

• 3.12.5.1 Creating JDBC Data Resources for an MPI Application Project for Oracle

  This section provides instructions for creating the JDBC data resources and defining the JDBC connections for an MPI Application Project for Oracle.

  1. For instructions on how to start and stop Oracle WebLogic Server, see Starting and Stopping Servers: Quick Reference at http://download.oracle.com/docs/cd/E14571_01/wls.htm.

  2. Log in to Oracle WebLogic Server Administration Console.

  3. On the left panel, under Domain Structure, expand Services, and then choose Data Sources.

     Table 3-13 Application Names for Each Project

     Project Name	Application Name
     OCDA_Study Study	Study
     OCDA_Study_Site	Study_Site
     OCDA_Study_Subject	subject
     OCDA_Geography	Geography
     OCDA_LOV	LOV
     OCDA_Site	Site
     OCDA_Investigator	Investigator
     OCDA_User	OCDA_User
     OCDA_Valdtn	OCDA_Valdtn
     OCDA_Product	Product
     OCDA_Program	Program
     OCDA_APP_USER	App_User
     OCDA_Study_Region	Study_Region
     OCDA_CRF	CRF
     OCDA_CRF_BOOK	CRF_BOOK

     
     

     A summary of JDBC Data Sources appears in the right panel.

  4. To create a new JDBC Data Source click New at the bottom of the right panel.

     Settings for a new JDBC Data Source appear in the right panel of the page. It is here that you will create a new JDBC Data Source.

  5. In the Name field, type <Application name>DataSource.

     The name you enter here will propagate elsewhere, so choose a name that is meaningful (for example, StudyDataSource).

  6. In the JNDI Name field, type jdbc/<Application name>DataSource.

     Use the name you entered in step 5 (for example, jdbc/StudyDataSource).

  7. In the Database Type list, choose the appropriate type (for example: Oracle).

  8. In the Database Driver list, choose the appropriate driver; for example: Oracle's Driver (Thin XA) for Instance Connections; Versions: 9.0.1; 9.2.0; 10, 11.

  9. Click Next.

  10. Click Next.

      Connection Properties appears on the Create a New JDBC Data Source panel. Use it to define the connection properties.

  11. In the Database Name field, type a name for the database to which you want to connect (for example: OCDA_Study).

  12. In the Host Name field, type the name or the IP address of the database server (for example: localhost).

  13. In the Port field, type the port on the database server that is used to connect to the database (for example: 1521).

  14. In the Database User Name field, type the database account user name you want to use to create database connections (for example: ohmpi_study).

  15. In the Password field, type a password for your database account to use to create database connections.

  16. In the Confirm Password field, re-type the password to confirm it.

  17. Click Next.

      The Settings for StudyDataSource page appears in the right panel.

  18. Click the Connection Pool tab, click Test Configuration, and then click Next.

      Select Targets window appears on the Create a New JDBC Data Source page in the right panel. You can select one or more targets to deploy the new JDBC data source.

  19. In the Servers check list, select one or more target servers and click Finish.

      Note:

      If you do not select a target, the data source will be created but not deployed. You will need to deploy the data source at a later time.

• Repeat the above steps to create jdbc/StudySequenceDataSource.

• 3.12.5.2 Creating JMS Resources for an MPI Application Project

  JMS servers act as management containers for the queues and topics in the JMS modules that are targeted to them.

  The following procedure includes instructions for creating JMS resources, which includes a:

  • JMS Server

  • JMS Module

  • JMS Connection Factory in the specific JMS Module

  • JMS Topic in the specific JMS Module

  3.12.5.2.1 To Create JMS Server

  1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Servers.

     A Summary of JMS Servers appears in the right panel. It includes a table that summarizes the JMS servers that have been created in the current WebLogic Server domain.

  2. In the table of previously created JMS Servers, click New.

     The Create a New JMS Server panel appears.

  3. In the Name field, type the name for your new JMS Server.

     Note:

     This name already exists in the table of previously created JMS Servers (in the example, StudyJMSServer).

• Click Next.

  Select Targets appears in the right panel under Create a New JMS Server.

• From the Target list select a target server instance or migratable target on which you want to deploy the JMS Server.

  Note:

  The default server instance is exampleServer.

• Click Finish.

• 3.12.5.2.2 To Create JMS Module

  1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

     The JMS Modules panel appears.

  2. In the JMS Modules table, click New to add a new JMS Module.

     The Create JMS System Module panel appears.

  3. In the Name field, type the new JMS Module name.

     Note:

     Remain consistent to the name chosen for the JDBC Data Source and the JMS Server (in the previous examples the key word was Study, making this name StudyJMSModule).

• Click Next.

  Select Targets appears in the right panel under Create a New JMS System Module.

• In the Servers area, select the server or cluster on which you want to deploy this JMS system module.

  Note:

  Retain the default, examplesServer.

• Click Finish.

• 3.12.5.2.3 To Create JMS Connection Factory

  1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

  2. Choose the JMS Module (in the example, StudyJMSModule) from the table of JMS Modules.

     The Settings for StudyJMSModule page appears in the right panel.

  3. In the Summary of Resources table, click New.

  4. Under the Type column in the Summary of Resources table choose Connection Factory and click Next.

     Another panel of Create a New JMS System Module Resource appears.

  5. In the Name field, type StudyOutBoundSender.

  6. In the JNDI Name field, type jms/StudyOutBoundSender.

  7. Click Next

  8. In the Target field, retain the default server instance, which is exampleServer, and click Finish.

  9. Click the Transaction tab for a newly created connection factory.

  10. Select XA Connection Factory Enabled and click Save.

  3.12.5.2.4 To Create JMS Topic

  1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

  2. In the right panel, choose the JMS Module you created (in the example, StudyJMSModule) from the table of JMS Modules.

     Settings for StudyJMSModule appear in the right panel with a Summary of Resources table.

  3. In the Summary of Resources table, click New, select Topic, and then click Next.

     The Create a New JMS System Module Resource panel appears on the right side of the window. Use this panel to set the properties that identify the new topic.

  4. In the Name field, under JMS Destination Properties, type <name>Topic (for example, StudyTopic).

  5. Set jms/StudyTopic as the JNDI Name and click Next.

     The Create a New JMS System Module Resource page appears in the right panel. Use this page to set the properties that will be used to target your new JMS system module resource.

  6. In the Subdeployments list, select None and click Create a New Subdeployment.

  7. In the Subdeployment Name field, type <name>Topic (for example, StudyTopic), and click OK.

  8. In the Targets table of JMS Servers, select <name>JMSServer (for example, StudyJMSServer).

  9. Click Finish.

  3.12.5.3 Deploying and Running Applications on Oracle WebLogic Server

  This procedure leads you through the steps to deploy and run an MPI Application on Oracle WebLogic Server.

  3.12.5.3.1 To Deploy and Run Applications on an Oracle WebLogic Server

  1. On the left panel of the WebLogic Server Administration Console, under Domain Structure, select Environment and then choose Deployments.

     The Summary of Deployments panel appears.

  2. On the right side of the panel under Deployments, click Install.

     A Summary of Deployments panel with a Deployments table containing a list of EAR files appears.

  3. Locate your application EAR and click Next.

     The Install Application Assistant page appears in the right panel.

  4. Locate the deployment you want to install and prepare for deployment.

     Tip:

     Select the file path that represent the application root directory, archive file, exploded archive directory, or application module descriptor that you want to install. You can also enter the path of the application directory or file in the Path field.

  Note:

  Only valid file paths are displayed. If you cannot find your deployment files, upload your file(s) and/or confirm that your application contains the required deployment descriptors.

• Click Next.

  Note:

  When deploying an MPI EAR file through the WebLogic Admin Console, under Security make sure that you choose DD Only. If you choose one of the other options, you will not be able to log into the MIDM.

• Click Finish.

• Launch Master Index Data Manager (MIDM).

• From a web browser, enter the following:

  • For MPI Application: https://localhost:7001/StudyMIDM

• Log in using your user name and password.

• 3.12.5.4 Setting Up the User

  In this step you create the MasterIndex.Admin and Administrator groups, and then create a new user within the two groups.

  1. On the left panel, under Domain Structure, expand Services, and then choose Security Realms.

  2. In the table on the Summary of Security Realms panel, click myrealm that is the name of the realm.

     The Settings for myrealm panel appears.

  3. Select the Users and Groups tab and then click Groups.

  4. In the Groups table, click New.

  5. In the Name field, type MasterIndex.Admin and click OK.

  6. In the Groups table, click New.

  7. In the Name field, type Administrator and click OK.

  8. On the Settings for myrealm panel, select Users and Groups and then Users.

  9. In the Users table, click New.

  10. Type a name and a password for the new user you are creating and click OK.

  11. Select User Group.

  12. To add the two groups you created to the user you created, from the Available list, drag MasterIndex.Admin to the Chosen list, and then drag Administrator to the Chosen list.

  Note:

  Repeat steps in Section 3.12.5.1, "Creating JDBC Data Resources for an MPI Application Project for Oracle", Section 3.12.5.2, "Creating JMS Resources for an MPI Application Project", and Section 3.12.5.3, "Deploying and Running Applications on Oracle WebLogic Server" for each of the 15 OHMPI projects.

  3.12.6 Setting Up Informatica Server

  Follow the steps in this section only if you plan to implement deduplication. Perform the following steps at the Informatica server:

  1. Set the OHMPI project related Jar files on Informatica Server:

     1. Navigate to $PMRootDir on Informatica server and create a folder OCDA_Javalib to store common Jar files. For example, /u01/oracle/Informatica/9.0.1/server/infa_shared/OCDA_Javalib

     2. Copy wlfullclient.jar file from <Weblogic home>/server/lib folder to folder created in the step 1.

        If wlfullclient.jar is not available, run the following command from <Weblogic home>/server/lib dir to generate wlfullclient.jar

        java -jar wljarbuilder.jar

  2. Create a file ocda.properties file with the following settings to store connection information of Oracle WebLogic server and place it under OCDA_Javalib.

     INITIAL_CONTEXT_FACTORY=weblogic.jndi.WLInitialContextFactory

     PROVIDER_URL= <URL> of the Oracle WebLogic server

     SECURITY_PRINCIPAL=<username> same username as provided on Weblogic Details Screen during CDA installation

  3. Navigate to $PMRootDir on Informatica server and create 15 OHMPI project specific folders. For example, /u01/oracle/Informatica/9.0.1/server/infa_shared/OCDA_Javalib/OCDA_Study.

     Following are the folder names:

     • OCDA_INVESTIGATOR

     • OCDA_SITE

     • OCDA_CRF_BOOK

     • OCDA_USER

     • OCDA_VALDTN

     • OCDA_CRF

     • OCDA_STUDY

     • OCDA_PROGRAM

     • OCDA_STUDY_REGION

     • OCDA_APP_USER

     • OCDA_GEOGRAPHY

     • OCDA_LOV

     • OCDA_STUDY_SITE

     • OCDA_PRODUCT

     • OCDA_STUDY_SUBJECT

  4. Copy the following jar files from OHMPI Projects lib folder to the respective folders created in step 3.

     • index-core.jar

     • mpi-client-ocda_study.jar (Project name will be the part of this Jar file)

     • net.java.hulp.i18n.jar