oracle® healthcare analytics data integrationoracle data integrator connectivity and knowledge...

Oracle® Healthcare Analytics Data IntegrationSecure Installation and Configuration Guide

Release 3.0 for Oracle Data Integrator

E29531-09

June 2014

Oracle Healthcare Analytics Data Integration Secure Installation and Configuration Guide, Release 3.0 for Oracle Data Integrator

E29531-09

Copyright © 2011, 2014 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

iii

Contents

Preface ................................................................................................................................................................. v

Audience....................................................................................................................................................... vDocumentation Accessibility ..................................................................................................................... vFinding Documentation on Oracle Technology Network..................................................................... vRelated Documents ..................................................................................................................................... viConventions ................................................................................................................................................. vi

1 Overview

1.1 Introduction ................................................................................................................................. 1-11.2 Technology Stack and System Requirements ......................................................................... 1-11.3 General Security Principles ....................................................................................................... 1-2

2 Getting Started

2.1 Installing the Prerequisite Software ......................................................................................... 2-12.2 Preinstallation Checklist ............................................................................................................ 2-12.3 Limitations of the Installer......................................................................................................... 2-22.4 Preinstallation Steps (Only for Upgrade) ................................................................................ 2-3

3 Setting up the Installation Environment

4 Installing Oracle Healthcare Analytics Data Integration

4.1 Installing Oracle Healthcare Analytics Data Integration ...................................................... 4-14.2 Performing Post-installation Configuration ........................................................................ 4-16

5 Installing Health Language, Inc.

6 Creating a New Oracle Data Integrator Repository Login

6.1 Creating a New OHADI ODI Repository Login .................................................................... 6-16.2 Creating a New HLI ODI Repository Login ........................................................................... 6-36.3 Updating Topology for HLI ..................................................................................................... 6-46.4 Configuring File Physical Schema............................................................................................ 6-56.5 Performing Post-installation Configuration ........................................................................... 6-6

7 Troubleshooting

v

Preface

This guide provides information about how to install Oracle Healthcare Analytics Data Integration (OHADI).

This preface contains the following topics:

■ Audience on page v

■ Documentation Accessibility on page v

■ Finding Documentation on Oracle Technology Network on page v

■ Related Documents on page vi

■ Conventions on page vi

AudienceThis installation guide is intended for those who are responsible for installing Oracle Healthcare Analytics Data Integration. You should be familiar with:

■ Oracle Database

■ Oracle Data Integrator (ODI) application

■ Oracle Healthcare Data Warehouse Foundation (HDWF)

■ UNIX or Windows operating system

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Finding Documentation on Oracle Technology NetworkThe Oracle Technology Network Web site contains links to all Oracle user and reference documentation. To find user documentation for Oracle products:

vi

1. Go to the Oracle Technology Network at

http://www.oracle.com/technetwork/index.html and log in.

2. Mouse over the Support tab, then click the Documentation hyperlink.

Alternatively, go to Oracle Documentation page at

http://www.oracle.com/technology/documentation/index.html

3. Navigate to the product you need and click the link.

For example, scroll down to the Applications section and click Oracle Health Sciences Applications.

4. Click the link for the documentation you need.

Related DocumentsFor more information, see the following documents:

Oracle Data Integrator■ Oracle Data Integrator Release Notes

■ Oracle Data Integrator Getting Started Guide

■ Oracle Data Integrator Installation Guide

■ Oracle Data Integrator Oracle Fusion Middleware Patching Guide

■ Oracle Data Integrator Upgrade Guide

■ Oracle Data Integrator Developer’s Guide

■ Oracle Data Integrator Application Adapters Guide

■ Oracle Data Integrator Knowledge Module Developer's Guide

■ Oracle Data Integrator Connectivity and Knowledge Modules Guide:

Oracle Healthcare Data Warehouse Foundation■ Oracle Healthcare Data Warehouse Foundation Release Notes

■ Oracle Healthcare Data Warehouse Foundation Secure Installation and Configuration Guide

■ Oracle Healthcare Data Warehouse Foundation Programmer's Guide

■ Oracle Healthcare Data Warehouse Foundation Interface Table Programmer's Guide

ConventionsThe following text conventions are used in this document:

boldface - Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic - Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace - Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1

Overview 1-1

1Overview

This chapter contains the following topics:

■ Section 1.1, "Introduction"

■ Section 1.2, "Technology Stack and System Requirements"

■ Section 1.3, "General Security Principles"

This section presents an overview of the Oracle Healthcare Analytics Data Integration (OHADI) requirements. It also describes the tasks that you must complete before you install the OHADI application.

1.1 IntroductionOHADI processes data from diverse source systems and loads the homogenized, consistent, complete, correct, and standardized data into HDWF for analysis.

Figure 1–1 Oracle Enterprise Healthcare Architecture Conceptual Overview

1.2 Technology Stack and System RequirementsThe following hardware and software technology stacks are required for OHADI installation:

■ Oracle Database 11.2.0.4

General Security Principles

1-2 Oracle Healthcare Analytics Data Integration Secure Installation and Configuration Guide

■ Oracle Data Integrator 11.1.1.7

■ Oracle Healthcare Data Warehouse Foundation 6.0

■ Linux or Windows operating system with at least 8 GB RAM

Table 1–1 lists system requirement references:

1.3 General Security PrinciplesThe following principles are fundamental to using any application securely.

Keep Software Up To DateOne of the principles of good security practice is to keep all software versions and patches up-to-date.

Keeping Up To Date on the Latest Security Information Critical Patch UpdatesOracle continually improves its software and documentation. Critical Patch Updates are the primary means of releasing security fixes for Oracle products to customers with valid support contracts. They are released on the Tuesday closest to the 17th day of January, April, July, and October. We highly recommend customers to apply these patches as soon as they are released.

Configure Strong Passwords on the DatabaseAlthough the importance of passwords is well known, the following basic rule of security management is worth repeating:

Ensure all passwords are strong passwords.

You can strengthen passwords by creating and using password policies for your organization. For guidelines on securing passwords and for additional ways to protect passwords, refer to the Oracle® Database Security Guide specific to the database release you are using.

You should modify the following passwords to use your policy-compliant strings:

■ Passwords for the database default accounts, such as SYS and SYSTEM.

■ Passwords for the database application-specific schema accounts, such as HDM, HDI, and HMC.

■ The password for the database listener. You must not configure a password for the database listener as that will enable remote administration. For more information, refer to the section Removing the Listener Password of Oracle® Database Net Services Reference 11g Release 2 (11.2).

Note: All references to media pack server in this document refer to the computer onto which you download the media pack for Oracle Healthcare Analytics Data Integration.

Table 1–1 System Requirements

Product Reference

Oracle Database 11.2.0.4 Database Installation Guide for <platform>

Oracle Data Integrator 11.1.1.7 Oracle Data Integrator Installation Guide

Oracle Healthcare Data Warehouse Foundation 6.0

Oracle Healthcare Data Warehouse Foundation Patch Readme and Release Notes


Overview 1-3

Follow the Principle of Least PrivilegeThe principle of least privilege states that users should be given the least amount of privilege to perform their jobs. Overly ambitious granting of responsibilities, roles, grants — especially early on in an organization's life cycle when people are few and work needs to be done quickly — often leaves a system wide open for abuse. User privileges should be reviewed periodically to determine relevance to current job responsibilities.

Before executing DDL scripts to create HMC schema, a database user should be created with specified limited set of privileges. DBA access should not be given to the user.

Database Security FeaturesThe following principles are fundamental to using any application securely:

■ Database Vault - Oracle Database Vault restricts access to specific areas in an Oracle database from any user, including users who have administrative access. For example, you can restrict administrative access to employee salaries, customer medical records, or other sensitive information.

■ About Audit Vault - Oracle Audit Vault automates the audit collection, monitoring, and reporting process. It turns audit data into a key security resource for detecting unauthorized activity. Consider using this feature to satisfy compliance regulations such as SOX, PCI, and HIPAA, and to mitigate security risks.

■ About Tablespace Encryption - Transparent Data Encryption is one of the three components of the Oracle Advanced Security option for Oracle Database 11.2.0.4 Enterprise Edition. It provides transparent encryption of stored data to support your compliance efforts. Applications do not have to be modified and will continue to work seamlessly as before. Data is automatically encrypted when it is written to disk, and automatically decrypted when accessed by the application. Key management is built in to the Tablespace Encryption feature, eliminating the complex task of creating, managing, and securing encryption keys.

Managing Default User AccountsSchema owner should not be the user for normal production; instead the account should be locked after the installation.

Closing All Open Ports Not in UseKeep only the minimum number of ports open and close all ports that are not in use.

Disabling the Telnet ServiceOracle Healthcare Analytics Data Integration Configuration does not use the Telnet service.

Telnet listens on port 23 by default.

If the Telnet service is available on any computer, Oracle recommends that you disable Telnet in favor of Secure Shell (SSH). Telnet, which sends clear-text passwords and user names through a log-in, is a security risk to your servers. Disabling Telnet tightens and protects your system security.

Disabling Other Unused ServicesIn addition to not using Telnet, the Oracle Healthcare Analytics Data Integration Configuration does not use the following services or information for any functionality:



■ Simple Mail Transfer Protocol (SMTP). This protocol is an Internet standard for E-mail transmission across Internet Protocol (IP) networks.

■ Identification Protocol (identd). This protocol is generally used to identify the owner of a TCP connection on Linux.

■ Simple Network Management Protocol (SNMP). This protocol is a method for managing and reporting information about different systems.

Restricting these services or information does not affect the use of Oracle Healthcare Analytics Data Integration Configuration. If you are not using these services for other applications, Oracle recommends that you disable these services to minimize your security exposure. If you need SMTP, identd, or SNMP for other applications, be sure to upgrade to the latest version of the protocol to provide the most up-to-date security for your system.

Designing for Multiple Layers of ProtectionWhen designing a secure deployment, design multiple layers of protection. If a hacker should gain access to one layer, such as the application server, that should not automatically give them easy access to other layers, such as the database server.

Providing multiple layers of protection may include:

■ Enable only those ports required for communication between different tiers, for example, only allowing communication to the database tier on the port used for SQL*NET communications (1521 by default).

■ Place firewalls between servers so that only expected traffic can move between servers.

Configuring Secure SQL NET

If the Oracle Data Integrator (ODI) repository is installed in a database server other than the server having HDWF schema, the data transfer will take place between two different database servers over a network. As HDWF contains sensitive clinical and healthcare data, you must secure the communication between database servers. Use Oracle® Net Manager to configure encryption to secure communication between database servers. Oracle provides different encryption algorithms to secure communication. Select an appropriate encryption algorithm. For more information, refer to Oracle® Database Advanced Security Administrator's Guide 11g Release 2 (11.2).

2

Getting Started 2-1

2Getting Started

This chapter contains the following topics:

■ Section 2.1, "Installing the Prerequisite Software"

■ Section 2.2, "Preinstallation Checklist"

■ Section 2.3, "Limitations of the Installer"

■ Section 2.4, "Preinstallation Steps (Only for Upgrade)"

2.1 Installing the Prerequisite SoftwareOracle expects that you have good knowledge of concepts and commands of operation system (Linux or Windows), Oracle Data Integrator (ODI), and Oracle Database (DB).

Before you can install the OHADI application, you must complete the following pre-installation tasks:

1. Install Oracle Database 11.2.0.4. Follow the instructions in Database Installation Guide for <platform>.

2. Install Oracle Data Integrator 11.1.1.7. Follow the instructions in ODI Installation Guide.

3. Install Oracle Healthcare Data Warehouse Foundation 6.0. Follow the instructions in Oracle Healthcare Data Warehouse Foundation Patch Readme and Release Notes.

4. Ensure the DB used in the installation has the corresponding TNS entry in the tnsnames.ora file (on the installation server).

5. Installation server should be of 64 –bit operating system (OS).

2.2 Preinstallation Checklist■ Ensure that you have set the NLS_LENGTH_SEMANTICS parameter of the

session creating Metadata Configuration (HMC) schema to either CHAR or BYTE as per your requirements.

■ Ensure that you have set a consistent default date format setting across HDWF, OHADI, and Rules Metadata Configuration.

■ Ensure that you have set a consistent time zone setting across HDWF, OHADI, and Rules Metadata Configuration.

■ Ensure that Temp Temporary Tablespace is available in the Database where the Metadata Configuration schema and Repository schemas are created.

Limitations of the Installer


■ If needed, create a separate permanent tablespace in DB for ODI repository DB schema creation.

■ Ensure that at least 2 GB space is available in the OHADI installation directory on Windows or Linux platform.

■ If the ODI repository DB is present in the remote server, and if you are installing on the Linux or Unix machine, mount the directory (datapump) of the remote DB server to the installation server with appropriate read and write privileges. Also, ensure the remote directories are accessible after mounting. The linux user of the remote server, who executes the Oracle process, must have minimum privilege of '444' (read access to any users) to the files (logs), which are created by the IMPDP command

If you are installing on the Windows machine, ensure the directory (datapump) is shared from the remote DB machine with appropriate read and write privileges to the installation server. Also, ensure that the password is not prompted while accessing the shared directory from the installer machine.

■ If the repository DB exists in the Exadata machine, you must add the repository DB single node (the node which is mounted) TNSENTRY in the tnsnames.ora file in the installation server. After installing, you must revert the TNSENTRY to muti-node.

■ Ensure the DB TNS entry for the HDWF DB or Repository DB has the same connection string name as the SID of the respective database.

■ Ensure that the System, HDWF, and Interface schema users do not display the Password expiry notification when you log in to the database.

■ Ensure that you have already installed HDWF 6.0 to install OHADI ODI 3.0 (fresh or upgrade install option). If it is not installed, do so by following the respective installation guides.

2.3 Limitations of the Installer

■ This installer is for a fresh or upgrade installation of the OHADI or HLI (Health Language, Inc.) product.

■ The installation scripts are coded in Linux and Windows OS. Ensure the installation server is compatible with these OS.

■ The installer is a 64-bit OS and hence the installation server should be the same.

■ The Linux X-Windows should be used for the Linux Oracle Universal Installer (OUI) installation (Linux graphical user interface).

■ Only one installer instance should be executed at a time. Oracle does not recommend running multiple instances of the installer.

■ The installer exits when the script encounters an error. You must check for errors manually before restarting the installer.

■ While entering installation details, do not leave any space before or after the input details in the test box.

Note: In the following sections, the text enclosed within <> indicate parameters and you need to provide the parameter values as per your system.

Preinstallation Steps (Only for Upgrade)

Getting Started 2-3

■ OUI throws an error on entering an invalid path in the installation server. Do not enter any space before path declaration or after the path configuration or in between paths.

■ Installation folder names should not have any spaces.

■ Do not leave any text box in the OUI blank. The OUI throws an error and does not let you traverse through the OUI screen.

■ For Linux installation, if any install script fails, an installer status email is sent to the configured email address (specified during installation).

■ The OUI installer can be re-executed multiple times but the installed script is skipped from re-execution.

■ The OUI installer does not fix any issues automatically. If the installation fails, you must manually verify and fix the issues.

■ For Linux, if you click Stop Installation during installation, the OUI installer stops. However, the current script execution (if any), runs in the server, which needs to be stopped manually.

■ The OUI installer does not validate the system space requirement of the installation server. Ensure that there is enough space in the installation directory and Oracle home directory.

■ The installer must run on the system where only ODI is installed.

■ When you are re-executing the installer due to a failure, enter the same details in the question prompting phase at all times. Do not delete any objects in the installation folder.

■ For re-installing the code on a different server path, delete all the files in $ORACLE_BASE/oraInventory/ContentsXML/ directory, before executing the installer. This is applicable if the product is installed on a different DB environment.

2.4 Preinstallation Steps (Only for Upgrade)

■ Interface tables must not be loaded during installation or data migration process.

■ Ensure that existing interface data is processed to HDM (using OHADI 2.0.1 or 2.0.2).

Preinstallation Steps (Only for Upgrade)


3

Setting up the Installation Environment 3-1

3Setting up the Installation Environment

To set up the installation environment, perform the following steps. This is common for both OHADI and HLI installation.

For Windows:1. Download and unzip the media pack.

2. Locate and unzip the OHADI_V3_ODI_Windows-x64.zip file from the media pack files.

3. Navigate to the /install/directory and double-click setup.exe to begin installation. Ensure that you have taken care of the Preinstallation checklist (see Section 2.2) before executing the installer.

For Linux:1. Download and unzip the media pack file into the Windows OS.

2. Create a directory in Linux installation server for copying OHADI 3.0 installation package files. For example, OHADI_INSTALL_DIR.

3. Locate and transfer the installer file OHADI_V3_ODI_Linux-x64.zip in the binary mode from Windows OS to the OHADI installation directory in the Linux server (for example, OHADI_INSTALL_DIR).

4. Convert the installer execution shell to SH shell as the installer script gets executed in SH shell of Linux or Unix OS.

5. Extract the contents of the OHADI_V3_ODI_Linux-x64.zip file in the <OHADI_INSTALL_DIR> directory using the following command:

unzip -a OHADI_V3_ODI_Linux-x64.zip

6. Provide execute permission for all the scripts as per the following commands:

chmod 755 <OHADI_INSTALL_DIR>/install/*

7. Create a directory ohadi_oui in the path <OHADI_INSTALL_DIR>/ as per the following command:

cd <OHADI_INSTALL_DIR>/

mkdir ohadi_oui

chmod 777 ohadi_oui

Note: No error message must be prompted upon execution of the unzip command.


8. Start the following OUI from the path <OHADI_INSTALL_DIR>/install/ by executing the command in Linux X-Windows prompt. Ensure that you have taken care of the Preinstallation checklist (see Section 2.2) before executing the installer.

cd <OHADI_INSTALL_DIR>/install/

./runInstaller

4

Installing Oracle Healthcare Analytics Data Integration 4-1

4Installing Oracle Healthcare Analytics DataIntegration

This chapter describes how to install OHADI on Linux and Windows OS. It contains the following sections:

■ Section 4.1, "Installing Oracle Healthcare Analytics Data Integration"

■ Section 4.2, "Performing Post-installation Configuration"

4.1 Installing Oracle Healthcare Analytics Data IntegrationTo install OHADI, perform the following steps:

1. The OUI Welcome screen appears on running the installer on the supported platform.

Note: Values in the following graphics are examples. You can change these values.

Installing Oracle Healthcare Analytics Data Integration


Figure 4–1 The OUI Installation Screen

Click Next to continue the installation.

2. Select the product to install and click Next.

Figure 4–2 Select a Product to Install



3. Select the required installation type and click Next:

■ Complete - Install a fresh OHADI 3.0

■ Upgrade - Upgrades installation from OHADI 2.0.2 to OHADI 3.0

Figure 4–3 Select the Installation Type

4. Specify the following home details:

■ Name - Select OUIHome1 from the drop-down list.

■ Path - Provide the complete path of ohadi_oui. For example, <OHADI_INSTALL_DIR>/ohadi_oui.



Figure 4–4 Specify Home Details

5. Click Next.

6. Select or specify the path where Oracle is installed on the installation server and click Next.

Note: Do not modify the value in the Name field. If you are restarting the installer for installation failures, select OUIHome1 from the drop-down box.

Also, enter the same installation directory for the Path field.



Figure 4–5 Select the Location of the Oracle Home

7. Select or specify the ODI Agent Home Directory path where ODI is installed in the installation server and click Next.

Figure 4–6 Select the ODI Agent Home Directory



8. Enter the OHADI ODI repository database details where the OHADI Work and Master repository needs to be installed.

Figure 4–7 Enter the OHADI ODI Repository Database Details

9. Click Next. The OHADI ODI Repository Details screen is displayed, which shows the ODI work repository name details for the ETL.

Note:

■ The DB system schema password is case-sensitive. Ensure to enter the correct password.

■ You cannot leave any text box field blank. The installation displays an error and you will not be able to proceed with the installation.

■ The OHADI ODI master repository and work repository DB schema users are created during runtime execution. Hence, provide an unique schema name for each repository. Do not use an existing OHADI master or work repository DB schema names.

■ Enter the DB permanent tablespace for schema creation of ODI repository (see Section 2.2), that is, master repository and work repository schemas.



Figure 4–8 OHADI ODI Repository Details

10. Click Next.

11. Enter the HDWF 6.0 Database (source and target database) configuration details and click Next.



Figure 4–9 Source and Target Database Configuration

12. Enter the ETL metadata configuration schema details.

Note:

■ The DB schema password is case-sensitive. Ensure to enter the correct password.




Figure 4–10 Enter the ETL Metadata Configuration Schema Details

13. Click Next.

The next two screens prompt for the seed data configuration on the Interface and HDWF schema. Select the required option. Oracle recommends you to select No.

Note: The metadata configuration schema is created during runtime execution of fresh OHADI installation.

For the upgrade option, ensure to use the metadata configuration details of the previous version. This schema is created in the database where HDWF is installed.



Figure 4–11 Seed Data for Interface Source

Figure 4–12 Seed Data for HDWF Source

14. Click Next. The Installation Server Configuration screen is displayed.



15. Click Yes if the installation server and ODI repository DB server are different else, click No.

Figure 4–13 Installation Server Configuration

16. Click Next. If you have selected Yes in step 15, the screens in step 17 are displayed.

17. For Linux, the following screen is displayed. Enter the following mounted directory configuration details in which remote server directory is being mounted:

■ Mounted Directory of Repository DB server - Enter the remote server path.

■ Mounted Directory in Installation server - Enter the path in the installation server where mounting is done.



Figure 4–14 Mounted Directory Configuration

For example, you can obtain all storage drives available in the OHADI installation Linux machine by executing the df –h command. If the remote server directory is mounted on the installation server, the mounting is displayed as follows:

<Remote Server name>:<Remote server path> <total size> <used up space> < Available space> <use%> <Path in installation server where mounting was done>

For example,

abc:/scratch/dump 191G 138G 44G 76% /slc03jpg

For Windows, the following screen is displayed:

Note: If the remote server mounted path is displayed as '/', you must provide the absolute mounted path of the remote server.



Figure 4–15 Shared Directory Configuration

For example, if the OHADI_DUMP directory is shared from the remote repository server with the same name, then:

■ Shared Directory of Repository DB Server: D:\OUI\ODI\OHADI_DUMP (absolute directory path that is shared in the Repository DB server)

■ Shared Directory of Installation Server: \\REMOTE_HOST_NAME\OHADI_DUMP (URL used to access the Repository DB server shared folder from the installation server)

18. Click Next. The Installation Email Configuration screen is displayed.

19. Enter the following email notification configuration details for installation summary details.

■ Notification Email List - Provide the email list for the installation notification.

■ Notification Email Subject - Retain the value as is.

Note: Shared path must have full permissions to the user accessing from the installation server.

You must access the path before providing the values in the installer. If any credentials are prompted, enter the credentials, and save it so that it does not prompt while accessing from installer.



Figure 4–16 Installation Email Configuration

20. Click Next.

21. The next screen displays the data entered during the installation question phase. Verify these values. If there are any incorrect values, click Back to make the changes.

22. Click Next.

If the configuration is successful, the Summary screen is displayed, with all installation details.

Note: This screen is not available for Windows as it does not send any mail notifications while installing.



Figure 4–17 Summary

23. Click Install to install OHADI product.

24. Once the installation is completed, the End of Installation screen is displayed.

Figure 4–18 End of Installation

Performing Post-installation Configuration


25. Click Exit to exit the installer.

26. For the Exadata server DB, before executing the ETL:

a. Revert the TNS entry to multi-node.

b. Update the multi-node Exadata server name in the ODI Repository Connection and Topology connections manually, which is created during installation.

4.2 Performing Post-installation ConfigurationPerform the following steps:

1. Create performance indexes on selected HDM tables.

Navigate to the ohadi_sql directory under OHADI Installation folder and run the OHADI_HDWF_PERF_INDEX_CREATE_DDL.sql file in the HDWF schema (HDM) manually upon successful installation of OHADI.

2. Interface data migration for multi-valued attributes.

Navigate to the ohadi_sql directory under OHADI Installation folder and execute the UPGD_OHADI_INTERFACE_ODI_MIGRATION_SCRIPT_202_TO_30.sql file in the interface schema (HDI) manually after the OHADI upgrade installation is completed.

3. Drop the data dump directory. Connect to the repository DB system schema and execute the following command:

DROP DIRECTORY OHADI_DUMP_DIR;

4. Revoke privileges on the repository schemas. Connect to the repository DB system schema and execute the following command:

REVOKE CREATE ANY SYNONYM FROM <master repository user>, <work repository user>;

5. Unmount or unshare the mounted or shared directory for remote installation.

Note: The following steps are applicable for both fresh and upgrade installations, except step 2, which is applicable only for upgrade installation.

Note: This step might take a considerable amount of time based on the volume of data present in HDM tables. Check the spool file for script execution status.

Note: This step might take a considerable amount of time based on volume of data, number of multi-valued tables, and attribute present in interface tables. Check the spool file for script execution status.

Note: Use the same values entered in Figure 4-7 for master repository schema and work repository schema users.



If you are installing HLI, perform this step after the HLI installation is complete.

5

Installing Health Language, Inc. 5-1

5Installing Health Language, Inc.

This chapter describes how to install Health Language, Inc. (HLI) on Linux and Windows OS.

The HLI product has a dependency on the metadata configuration schema of OHADI. Hence, OHADI 3.0 must be available in the system for the HLI 3.0 installation.

To install HLI, perform the following steps:

1. The OUI Welcome screen appears on running the installer on the supported platform.

Figure 5–1 The OUI Installation Screen

Click Next to continue the installation.

Note: Values in the following graphics are examples. You can change these values.


2. Select the product to install and click Next.

Figure 5–2 Select a Product to Install

3. Select the required installation type and click Next:

■ Complete - Install a fresh HLI 3.0

■ Upgrade - Upgrades installation from HLI 2.0.x to HLI 3.0


Figure 5–3 Select the Installation Type

4. Specify the following home details:

■ Name - Select OUIHome1 from the drop-down list.

■ Path - Provide the complete path of ohadi_oui. For example, <OHADI_INSTALL_DIR>/ohadi_oui.


Figure 5–4 Specify Home Details

5. Click Next.

6. Select or specify the path where Oracle is installed on the installation server and click Next.

Note: Do not modify the value in the Name field. If you are restarting the installer for installation failures, select OUIHome1 from the drop-down box.

Also, enter the same installation directory in the Path field.


Figure 5–5 Select the Location of the Oracle Home Directory

7. Select or specify the ODI Agent Home Directory path where ODI is installed in the installation server and click Next.

Figure 5–6 Select the ODI Agent Home Directory


8. Enter the ODI repository database details where the HLI work and master repository needs to be installed.

Figure 5–7 Enter the HLI ODI Repository Database Details

9. Click Next. The HLI ODI Repository Detail screen is displayed, which shows the HLI work repository details for the ETL.

Note:

■ The DB system schema password is case-sensitive. Ensure to enter the correct password.


■ The ODI master repository and work repository DB schema users are created during runtime execution. Hence, provide unique schema name for each repository. Do not use an existing master or work repository DB schema names.

■ Enter the permanent tablespace for ODI DB schema (see Section 2.2) for schema creation of ODI repository, that is, master repository and work repository schema).


Figure 5–8 HLI ODI Repository Detail

10. Click Next.

11. Enter the HDWF 6.0 Database (target and metadata database) configuration details.


Figure 5–9 Target and Metadata Database Configuration Details

12. Click Next. The Installation Server Configuration screen is displayed.

13. Click Yes if the installation server and ODI repository DB server are different else, click No.


Figure 5–10 Installation Server Configuration

14. Click Next. If you have selected Yes in step 13, the screens in step 15 are displayed.

15. For Linux, the following screen is displayed. Enter the following mounted directory configuration details:

■ Mounted Directory of Repository DB server - Enter the remote server path.

■ Mounted Directory in Installation server - Enter the path in the installation server where mounting is done.


Figure 5–11 Mounted Directory Configuration

For example, you can obtain all storage drives available in the OHADI installation Linux machine by executing the df –h command. If the remote server directory is mounted on the installation server, the mounting is displayed as follows:

<Remote Server name>:<Remote server path> <total size> <used up space> < Available space> <use%><Path in installation server where mounting was done>

For example,

abc:/scratch/dump 191G 138G 44G 76% /slc03jpg

For Windows, the following screen is displayed:

Note: If the remote server mounted path is displayed as '/', provide the absolute mounted path of the remote server.


Figure 5–12 Shared Directory Configuration

For example, if the HLI_DUMP directory is shared from the remote repository server with the same name, then:

■ Shared Directory of Repository DB Server: D:\OUI\ODI\HLI_DUMP (absolute directory path that is shared in the Repository DB server)

■ Shared Directory of Installation Server: \\REMOTE_HOST_NAME\HLI_DUMP (URL used to access the Repository DB server shared folder from the installation server)

16. Click Next. The Installation Email Configuration screen is displayed.

17. Enter the following email notification configuration details for installation summary details.

■ Notification Email List - Provide the email list for the installation notification.

■ Notification Email Subject - Retain the value as is.

Note: For Windows:

Shared path should have full permissions to the user accessing from the installation server.

You must access the path before providing the values in the installer. If any credentials are prompted, enter the credentials, and save it so that it does not prompt while accessing from installer.


Figure 5–13 Installation Email Configuration

18. Click Next.

19. The next screen displays the data entered during the installation question phase. Verify these values. If there are any incorrect values, click Back to make the changes.

20. Click Next.

If the configuration is successful, the Summary screen is displayed with all installation details.

Note: This screen is not available for Windows as it does not send any mail notifications while installing.


Figure 5–14 Summary

21. Click Install to install HLI product.

22. Once the installation is completed, the End of Installation screen is displayed.

Figure 5–15 End of Installation

23. Click Exit to exit the installer.

24. For the Exadata server DB, before executing the ETL:


a. Revert the TNS entry to multi-node.

b. Update the multi-node Exadata server name in the ODI Repository Connection and Topology connections manually, which is created during installation.

6

Creating a New Oracle Data Integrator Repository Login 6-1

6Creating a New Oracle Data IntegratorRepository Login

This chapter contains the following sections:

■ Section 6.1, "Creating a New OHADI ODI Repository Login"

■ Section 6.2, "Creating a New HLI ODI Repository Login"

■ Section 6.3, "Updating Topology for HLI"

■ Section 6.4, "Configuring File Physical Schema"

■ Section 6.5, "Performing Post-installation Configuration"

6.1 Creating a New OHADI ODI Repository LoginPerform the following steps to create a new OHADI ODI repository login:

1. Navigate to ODI > File > New > Create a New ODI Repository Login.

Figure 6–1 Create a New ODI Repository Login

Creating a New OHADI ODI Repository Login


2. Click OK. The Repository Connection Information screen is displayed.

3. Enter the following values:

■ Login Name: For example, OHADI_30_LOGIN

■ User: SUPERVISOR

■ Password: SUNOPSIS (you can change it once you login successfully)

■ User: <database schema created for the master repository>

■ Password: <database schema password created for the master repository>

■ Driver List: Select Oracle JDBC Driver from the drop-down list.

■ Driver Name: oracle.jdbc.oracledriver

■ Url: Set appropriate values based on your database details

■ Work Repository - Select the Work Repository option, browse and select OHADI_WORK_REPOSITORY from the Work Repositories List, and click OK.

Figure 6–2 Repository Connection Information

4. Click OK. The login name is created with the name specified in step 3.

5. Navigate to ODI > Connect > ODI Studio.

6. Enter the following details:

■ Login Name: Select OHADI_30_LOGIN

■ User: Supervisor

■ Password: SUNOPSIS

Creating a New HLI ODI Repository Login


Figure 6–3 Oracle Data Integrator Login for OHADI

6.2 Creating a New HLI ODI Repository LoginPerform the following steps to create a new HLI ODI repository login:

1. Navigate to ODI > File > New > Create a New ODI Repository Login.

2. Click OK. The Repository Connection Information screen is displayed.

3. Enter the following values:

■ Login Name: For example, HLI_30

■ User: SUPERVISOR

■ Password: SUNOPSIS (you can change it once you login successfully)

■ User: <database schema created for the master repository>

■ Password: <database schema password created for the master repository>

■ Driver List: Select Oracle JDBC Driver from the drop-down list.

■ Driver Name: oracle.jdbc.oracledriver

■ Url: Set appropriate values based on your database details

■ Work Repository - Select the Work Repository option, browse and select EHA_HLI_WORK_REPOSITORY from the Work Repositories List, and click OK.

Updating Topology for HLI


Figure 6–4 Repository Connection Information

4. Click OK. The login name is created with the name specified in step 3.

5. Navigate to ODI > Connect > ODI Studio.

6. Enter the following details:

■ Login Name: Select HLI_30

■ User: Supervisor

■ Password: SUNOPSIS

Figure 6–5 Oracle Data Integrator Login for HLI

6.3 Updating Topology for HLI To override the path updated during installation for the source file, perform the following steps:

1. Open ODI studio and click Connect to Repository.

2. Select the HLI login (created in Section 6.2 and click OK.

Configuring File Physical Schema


3. Navigate to Topology > Physical Architecture > Technologies > File. Double-click HLI_DATA.

Figure 6–6 HLI_DATA File Data Server

4. In the JDBC tab, update the following values:

■ JDBC Driver: com.sunopsis.jdbc.driver.file.FileDriver

■ JDBC URl: jdbc:snps:dbfile

Figure 6–7 Update JDBC Values

6.4 Configuring File Physical SchemaTo update the existing physical schema for HLI_DATA, perform the following steps:

1. Navigate to Topology > Physical Architecture > Technologies > File > HLI_DATA.

2. Double-click physical schema.

3. In the Definition tab, specify the actual physical folder location of the HLI Data Files for the properties Directory (Schema) and Directory (Work Schema).



Figure 6–8 Update the Physical Schema for HLI_Data

4. Click Save from the menu bar. The existing physical schema is saved.

6.5 Performing Post-installation ConfigurationThe following steps are applicable for both fresh and upgrade installations:

1. Drop the data dump directory. Connect to the system schema and execute the following command:

DROP DIRECTORY HLI_DUMP_DIR;

2. Revoke privileges on the repository schemas. Connect to the system schema and execute the following:

REVOKE CREATE ANY SYNONYM FROM <master repository user>, <work repository user>;

Note: For references on Topology configuration, see Oracle Data Integrator documentation.

Note: Use the same values entered in Figure 5-7 for master repository schema and work repository schema users.

7

Troubleshooting 7-1

7Troubleshooting

■ During the OHADI installation, the OUI generates the following log files:

– installActions<timestamp>.log - This log file records the action of the installer and helps in diagnosing problems with the installation.

– oraInstall<timestamp>.out - This output file records all the output of SQL scripts that are run by the installer.

– oraInstall<timestamp>.err - This error file records all the errors from the scripts run by the installer. You must include the above log file if you report any problems while installing OHADI. The log files are time stamped and each installation session creates a new log file.

For Windows, the log files are located at \Oracle\Inventory\logs.

For example, C:\Program Files\Oracle\Inventory\logs

For Linux, the log files are located at $ORACLE_BASE/oraInventory/logs.

For example, /u01/app/oraInventory/logs

■ The following is the order of execution of the installation scripts using the installer:

1. OHADI_ODI_SETENV_CREATE.sh/bat

2. OHADI_ODI_FOLD_FILE_PERMISSION.sh

3. OHADI_ODI_DATABASE_SETUP.sh/bat

4. OHADI_ODI_MASTER_WORK_CREATE.sh /bat

5. OHADI_ODI_DATADUMP_CREATE.sh/bat

6. OHADI_SCHEMA_ENC_PASWD.sh/bat

7. OHADI_ODI_UTIL_FILE_CREATE.sh/bat

8. OHADI_ODI_MASTER_IMPORT.sh/bat

9. OHADI_ODI_WORK_REP_UPDATE.sh/bat

10. OHADI_ODI_REPO_TOPOLOGY_UPDATE.sh/bat

11. OHADI_ODI_INSTALL_VERIFICATION.sh/bat

12. OHADI_ODI_DELETE_TEST_DATA.sh/bat

13. OHADI_ODI_RESET_LOADDATE.sh/bat

■ In the backend, the installer creates the following directories:


For OHADI - ohadi_xmls, ohadi_sql, ohadi_scripts, and ohadi_logs

For HLI - hli_xmls, hli_sql, hli_scripts, and hli_logs

These directories are created under the path:

Windows:

<OHADI_INSTALL_DIR>/

Linux:

OHADI path: <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/

HLI path: <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.hli/

■ The scripts OHADI_ODI_SETENV_CREATE.sh/bat and OHADI_ODI_FOLD_FILE_PERMISSION.sh are mandatory. You cannot skip the execution of these scripts for any installer.

■ When the installation completes, a zero byte file is created in the log directory:

■ For a successful execution of script, a done file (<script_name>.done) for every script is created.

Linux X-Windows:

cd <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/ls -lrt *.donels -lrt OHADI_DATABASE_SETUP.done

■ Windows:

cd <OHADI_INSTALL_DIR>/ ohadi_logs/Dir *.doneDir OHADI_DATABASE_SETUP.done

■ For an unsuccessful execution of script, an error file is created.

Linux X-Windows:

cd <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/ls -lrt *.errorls -lrt OHADI_DATABASE_SETUP.error

Windows:

cd <OHADI_INSTALL_DIR>/ ohadi_logs/Dir *.errorDir OHADI_DATABASE_SETUP.error

■ When the installer is re-executed, the presence of *.done file skips the corresponding script execution and re-executes the remaining scripts.

■ To re-execute a particular step, remove the corresponding .done file from the log directory.

■ To skip a particular step, create a zero byte done file in the log directory (<OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/) and execute the following command:

Linux X-Windows:

For example, touch <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/OHADI_DATABASE_SETUP.done

Windows:

Troubleshooting 7-3

For example, REM. ><OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/OHADI_DATABASE_SETUP.done

■ If the installation fails in OHADI_ODI_MASTER_IMPORT.sh or OHADI_ODI_ETL_IMPORT.sh for incorrect configuration of the remote server path, delete the <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/ OHADI_ODI_DATADUMP_CREATE.done file, before restarting the installer.

■ For other script failures, the installer displays an error and exits. You have to manually check for the error in the log directory <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/ohadi_logs/, and fix the error before restarting the installer.

■ The following is a sample of the e-mail notification for the installation status:

****** OHADI INSTALLATION START TIME : 10-25-13 03:41:01 ****** OHADI_ODI_DATABASE_SETUP.sh (OHADI DATAMODEL & SEED DATA SETUP) : SUCCESSOHADI_ODI_MASTER_WORK_CREATE.sh (OHADI ODI MASTER & WORK REPSOSITORY USER CREATION) : SUCCESSOHADI_ODI_DATADUMP_CREATE.sh ( OHADI ODI XML DATA DIRECTORY UPDATION) : SUCCESSOHADI_SCHEMA_ENC_PASWD.sh (OHADI ODI SCHEMA PASSWORD ENCRYPTION) : SUCCESSOHADI_ODI_UTIL_FILE_CREATE.sh (OHADI ODI INSTALL UTILTIY FILE CREATION) : SUCCESSOHADI_ODI_MASTER_IMPORT.sh (OHADI ETL DUMP IMPORT) : SUCCESSOHADI_ODI_WORK_REP_UPDATE.sh (OHADI WORK REPOSITORY UPDATION) : SUCCESSOHADI_ODI_REPO_TOPOLOGY_UPDATE.sh (OHADI RELATION CONNECTION UPDATION IN REPOSITORY) : SUCCESSOHADI_ODI_INSTALL_VERIFICATION.sh (OHADI FEW ETL TEST FOR VALIDATION) : SUCCESSOHADI_ODI_DELETE_TEST_DATA.sh (OHADI TEST DATA DELETION) : SUCCESSOHADI_ODI_RESET_LOADDATE.sh (OHADI ETL RUN DATE RESETING) : SUCCESS ****** OHADI INSTALL END TIME : 10-25-2013 03:44:28 ******

■ To reinstall the code with a different server path, delete all the files in <$ORACLE_BASE>/oraInventory/ContentsXML/ directory before the executing the installer. For example, /u01/app/oraInventory/ContentsXML/.

Note: This is applicable when the product has to be reinstalled for different installation requirement on the same installation server (not applicable for failure restart).