2 Installing Oracle Health Sciences Clinical Development Analytics Standard Configuration

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

This chapter includes the following section:

• Installing Oracle Health Sciences Clinical Development Analytics Standard Configuration

• Managing Source System Specific Requirements

2.1 Installing Oracle Health Sciences Clinical Development Analytics Standard Configuration

This section describes the OHSCDA Installation tasks that you must complete.

Note:

• All references to ${DAC_INSTALL_DIR} in this document refer to DAC installation folder.

OHSCDA application installation consists of seven components:

• Running the OHSCDA Installer

• 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

• Setting Up OHMPI Projects (Optional)

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

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.

4. Review the Oracle Universal Installer Welcome screen and click Next.

   The Welcome screen provides information about the Oracle Universal Installer. The following function buttons appear on the installation screens:

   • Deinstall Products: Deinstall individual components or the entire product. This button appears only on the Welcome screen.

   • About Oracle Universal Installer: View the version number of the installer in use.

   • Help: Access detailed information about the functionality of each screen.

   • Installed Products: View currently installed products or deinstall the entire product or components.

   • Next: Proceed to the next screen.

   • Cancel: Cancel the installation process and exit the installer.

5. Click Next.

6. Specify Home Details screen is displayed.

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

   Example Name: OCDAHome1

   Path: C:\OCDA

7. Click Next.

8. Install or Upgrade OHSCDA screen is displayed.

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

9. Click Next.

10. OHSCDA Data Warehouse Details screen is displayed.

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

    Enter values in the following fields:

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

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

    Default Table Space:

    Temporary Table Space:

11. Click Next and enter. OHSCDA Data Warehouse is displayed. Enter and confirm the System Password of the database where OHSCDA Data Warehouse will be deployed.

12. Click Next and enter and confirm:

    OHSCDA Warehouse Schema (RXI) Password:

13. Click Next and enter and confirm:

    OHSCDA RPD (RXI_RPD) Password:

14. OHSCDA Informatica PowerCenter Details screen is displayed.

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

    Enter values in the following fields:

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

    • Informatica Domain Name: Domain of the Informatica repository.

    • Informatica Hostname: Host name of the Informatica server.

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

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

15. Click Next and enter.

    Informatica Password for Admin user: Password for Informatica User with admin privileges.

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

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

    Example:

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

17. Click Next.

18. Multi Source Integration History screen is displayed only if you are upgrading OHSCDA.

    Select Yes if you previously installed OHSCDA2.1 with MSI, or else select No.

19. Click Next.

20. Multi Source Integration screen is displayed.

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

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

21. Click Next.

22. Oracle Healthcare Master Person Index screen is displayed.

    Enter values in the following fields:

    • Connect String of OHMPI Schemas

    • Default Table Space

    • Temporary Table Space

23. Click Next and enter and confirm:

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

24. Click Next and enter and confirm:

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

25. Click Next and enter and confirm:

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

26. Click Next.

27. Summary screen is displayed.

    Verify setting => details provided in the summary screen.

28. Click Install.

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

    <ocda_home>\install\ocda_install.log.

2.1.2 Setting Up Relational Connections in the Informatica Workflow for OHSCDA

1. For each database that will be a source for extracting data into the OHSCDA warehouse, perform the following to create a Relational Connection in the Informatica Workflow Manager. (If you are using OHMPI, include the OHMPI Master Index database as one of the sources for which you create a Relational Connection):

   1. Launch 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 should be added on Informatica Server.

      Note:

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

2. Connect to Informatica PowerCenter Administration Console.

3. Connect to the Informatica integration service.

4. Navigate to the Custom Properties window.

5. Enter AggSupprtWithNoPartLic in the Name field.

6. Enter Yes in the Value field.

2.1.3 Preparing a DAC Repository for OHSCDA

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 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 the Preparing a DAC Repository for OHSCDA 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 else select only CDA_Warehouse application 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. 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 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.

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 — 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. In this step, you configure source databases (Oracle Clinical, Siebel Clinical) 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. 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.

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

7. 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 2-1 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

   
   

   Note:

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

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

9. 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 and Siebel Clinical 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.

   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. If you plan to implement deduplication, navigate to CDA - Complete Initial De Dup Execution Plan and CDA - Complete Warehouse De Dup Execution Plan.

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

   7. Click Save.

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

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

   10. Click Save.

Note:

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

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

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

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 2-2 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 2.1.9, "Setting Up Informatica Server (Optional)" 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 OHSCDA 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 (OHSCDA Warehouse Target Connect Name you had specified in step 10 of Section 2.1.1, "Running the OHSCDA Installer,").

Note:

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

2.1.4 Emplacing the OHSCDA Help and Image Files

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

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

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, present in <MIDDLEWARE_HOME>\\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1.

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

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

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

2.1.5 Preparing the OBIEE Web Catalog and Repository for OHSCDA

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

1. Copy OracleClinicalDevelopmentAnalytics.zip from OCDA_Home\oracle.pharma.ocda.standard\Reporting\Webcat to OBIEE server.

2. Copy OCDA.rpd files from OCDA_Home\oracle.pharma.ocda.standard\Reporting\RPD to OBIEE server.

3. Unzip OracleClinicalDevelopmentAnalytics.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 OHSCDA 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. Modify the connection pools in the RPD as following:

    1. In the physical layer, expand the OHSCDA Data Warehouse node and double-click Connection Pool object to open Connection Pool dialog box.

    2. Set Data source name field to the ODBC entry for the warehouse you created in step 3.

    3. Change the username to the username of the OHSCDA read-only schema. (RXI_RPD)

    4. Change the password to the password of the OHSCDA read-only schema. (RXI_RPD)

    5. Click OK.

    6. Reconfirm the password.

    7. Click OK.

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

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

17. Click Close in the Consistency Check Manager.

18. Click Save.

19. Click File and then click Close.

20. Click File and then click Exit.

21. Open NQSConfig.xml found at <MIDDLEWARE_HOME>instances\instance1\config\OracleBIServerComponent\coreapplication_obis1.

22. Set EVALUATE_SUPPORT_LEVEL = 2.

23. Start the Oracle WebLogic Server and BI components.

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

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

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

27. Navigate the Repository tab of the Deployment page.

28. Click Lock and Edit Configuration.

29. Click Close.

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

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

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

33. Click Apply, and then click Activate Changes.

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

2.1.6 Configuring Maps

You will need to have a database with the sample map data set. Perform the following steps to download the sample map data set:

1. Go to http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html.

2. Navigate to OBIEE 11.1.1.3 - Sample Application.

3. Click NAVTEQ Data Bundle for OBIEE.

4. Click Save.

Perform the following steps to configure maps:

1. Open the Map Viewer console available at http://<server>:9704/mapviewer.

2. Click Admin.

3. Login with the user ID and password provided during the installation.

4. Click Configuration. This will launch the mapViewerConfig.xml file.

5. In the <security_config> property of the file, make the following changes:

   1. Change <proxy_enabled_hosts> property to hostname, IP address and port to correct values.

      Note:

      There are 4 entries — 2 pointing to hostname and 2 pointing to IP address of BI server. Ensure that all 4 entries point to the right server.

      For example,

      <proxy_enabled_hosts>
      http://localhost:9704/mapviewer,http://localhost:9704/,http://10.10.10.10:9704/,http://10.10.10.10:9704/mapviewer
      </proxy_enabled_hosts>
      

   2. Update or add the following entries:

      <disable_direct_info_request> true </disable_direct_info_request> 
      <disable_info_request> true </disable_info_request> 
      <disable_csf>true</disable_csf> 
      <enforce_security_role> true </enforce_security_role>
      

6. In the 'Predefined Data Sources' section, add the following entry:

   <map_data_source name="OBIEE_NAVTEQ_Sample"
   jdbc_host="10.153.228.125"
   jdbc_sid="cda22dv"
   jdbc_port="1521"
   jdbc_user="obiee_navteq"
   jdbc_password="!obiee_navteq " 
   jdbc_mode="thin"
   number_of_mappers="6"
   allow_jdbc_theme_based_foi="false"
   />
   

7. Click Save and Restart to save the changes and restart the services.

2.1.7 Creating Security Groups and Application Roles for OHSCDA

2.1.7.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 2-3 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.1.7.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 2-4 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

      
      

2.1.8 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 installation.

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.

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

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

2.1.8.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 2-5 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. Click Next.

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

10. Click Next.

11. Click Next.

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

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

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

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

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

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

18. Click Next.

    The Settings for StudyDataSource page appears in the right panel.

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

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

21. Repeat the above steps to create jdbc/StudySequenceDataSource.

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

2.1.8.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).

4. Click Next.

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

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

6. Click Finish.

2.1.8.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).

4. Click Next.

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

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

   Note:

   Retain the default, exampleServer.

6. Click Finish.

2.1.8.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. Select XA Connection Factory Enabled and click Save.

8. Click Next

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

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

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

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

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

6. Click Finish.

7. Launch Master Index Data Manager (MIDM).

8. From a web browser, enter the following:

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

9. Log in using your user name and password.

2.1.8.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 2.1.8.1, "Creating JDBC Data Resources for an MPI Application Project for Oracle", Section 2.1.8.2, "Creating JMS Resources for an MPI Application Project", and Section 2.1.8.3, "Deploying and Running Applications on Oracle WebLogic Server" for each of the 15 OHMPI projects.

2.1.9 Setting Up Informatica Server (Optional)

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

   CDA_STORE_URL=/u01/oracle/Informatica/9.0.1/server/infa_shared/OCDA_Javalib/CDA_SEC_STORE

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

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

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

   index-core.jar

   net.java.hulp.i18n.jar

4. Navigate to OCDA_HOME folder locate, copy and unzip CDA_SEC_STORE.zip to $PMRootDir/OCDA_Javalib on Informatica server.

5. Create Secret Store Wallet and User Management.

   OHSCDA needs to store the OHMPI username and password that is used to set the Context and call the OHMPI EJB during incremental dedup ETL execution. This user name and password is encrypted and stored in secret store wallet files. Following are the steps to store this information.

   1. Navigate to the CDA_SEC_STORE directory; execute CDA_OHMPI_CREATE_SSTORE.sh

   2. Enter the User ID and password that are used for the OHMPI MIDM login.

      Note:

      To change the password for an existing user entry in the wallet file, re-enter the same User ID with a new password. This updates the password in the wallet file.

   3. Provide read and execute privileges to Operating system user that starts Informatica server services.

2.2 Managing Source System Specific Requirements

2.2.1 Fine-tuning Oracle Clinical Settings

To optimize source system integration with OHSCDA, 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.2.0.3—alter session set optimizer_features_enable='11.2.0.3'

   • Oracle Database 11.1.0.7—alter session set optimizer_features_enable='11.1.0.7'

3. Create the following indexes:

   • 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.2.2 Handling Deletions in Siebel Clinical

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

   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, and 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's Guide (Chapter 2, Extract Transform Load Programs).