How to Install OHADI

8/21/2019 How to Install OHADI

1/52

Oracle Healthcare Analytics Data Integration

Secure Installation and Configuration Guide

Release 2.0.2 for Oracle Data Integrator

E29531-07

May 2013


2/52

Oracle Healthcare Analytics Data Integration Secure Installation and Configuration Guide, Release 2.0.2 forOracle Data Integrator

E29531-07

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

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense 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. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou 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 iton behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical datadelivered 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. Assuch, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions andlicense terms set forth in the applicable Government contract, and, to the extent applicable by the terms ofthe Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer SoftwareLicense (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 managementapplications. It is not developed or intended for use in any inherently dangerous applications, includingapplications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and othermeasures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused 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 trademarksof their respective owners.

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


3/52

iii

Contents

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

Audience....................................................................................................................................................... v

Documentation Accessibility..................................................................................................................... v

Finding Documentation on Oracle Technology Network.................. ............... ................ ............... ..... v

Related Documents ............... .............. ................ .............. ............... .............. ............... .............. ................ vi

Conventions .............. ............... .............. ............... .............. ................ .............. ................ ............... ............ vi

1 Overview

1.1 Technology Stack and System Requirements .............. ............... ............... ............... .............. 1-1

1.2 General Security Principles ....................................................................................................... 1-1

2 Installing Oracle Healthcare Analytics Data Integration

2.1 Installing the Prerequisite Software ............. ................ ............... .............. ................ ............... 2-1

2.2 Setting Up the Database............................................................................................................. 2-1

2.2.1 Preinstallation Checklist ............. .............. ............... ............... ............... ............... .............. 2-2

2.2.2New Installation of Oracle Healthcare Analytics Data Integration ODI 2.0.2............

2-3

2.3 Setting Up ODI Repositories ............. ................ ............. ................ .............. ............... .............. 2-6

2.3.1 Creating a New Oracle Data Integrator Repository Login............................................ 2-7

2.3.2 Importing Master Repository............................................................................................. 2-9

2.3.3 Creating a New Oracle Data Integrator Work Repository ......................................... 2-11

2.3.4 Importing Scripts .............................................................................................................. 2-14

2.4 Configuring ODI Repositories ............................................................................................... 2-18

2.5 Installation Verification........................................................................................................... 2-21

3 Installing Oracle Enterprise Healthcare Analytics Health LanguageInternational Integration

3.1 Setting Up ODI Repositories ............. ................ ............. ................ .............. ............... .............. 3-13.2 Configuring ODI Repositories ............................................................................................... 3-10

3.2.1 Post Installation Steps ...................................................................................................... 3-14

Index


4/52

iv


5/52

v

Preface

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

This preface contains the following topics:

Audienceon page v

Documentation Accessibilityon page v Finding Documentation on Oracle Technology Networkon page v

Related Documentson page vi

Conventionson page vi

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

Oracle Database

Oracle Data Integrator (ODI) application Oracle Healthcare Data Warehouse Foundation (HDWF) application

UNIX or Windows operating system

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

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. Forinformation, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=infoorvisit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearingimpaired.

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


6/52

vi

1. Go to the Oracle Technology Network at

http://www.oracle.com/technetwork/index.htmland log in.

2. Mouse over the Support tab, then click the Documentationhyperlink.

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 HealthSciences Applications.

4. Click the link for the documentation you need.

Related DocumentsFor more information, see the following documents in the Oracle Data IntegratorRelease 7.0 documentation set or in the Oracle Other Product Two Release 6.1documentation set:

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 Developers 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 ConfigurationGuide

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 anaction, or terms defined in text or the glossary.

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

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


7/52

1

Overview 1-1

1Overview

This chapter contains the following topics:

Technology Stack and System Requirementson page 1

General Security Principleson page 1

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

1.1 Technology Stack and System RequirementsThe following hardware and software technology stacks are required for OHADIinstallation:

Oracle Database 11.2.0.2 (64-bit)

Oracle Data Integrator 11.1.1.6

Oracle Healthcare Data Warehouse Foundation 5.0.2

UNIX or Window operating system with at least 8 GB RAM

The following table lists system requirement references.

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

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

Table 11 System Requirement References

Product Reference

Oracle Database 11.2.0.2 (64-bit) Database Installation Guide for

Oracle Data Integrator 11.1.1.6 Oracle Data Integrator Installation Guide

Oracle Healthcare Data Warehouse Foundation5.0.2

Oracle Healthcare Data Warehouse FoundationPatch Readme and Release Notes


8/52

General Security Principles

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

Keep Software Up To Date

One of the principles of good security practices is to keep all software versions andpatches up to date.

Keeping Up To Date on the Latest Security Information Critical Patch Updates

Oracle continually improves its software and documentation. Critical Patch Updates

are the primary means of releasing security fixes for Oracle products to customerswith valid support contracts. They are released on the Tuesday closest to the 17th dayof January, April, July and October. We highly recommend customers to apply thesepatches as soon as they are released.

Configure Strong Passwords on the Database

Although the importance of passwords is well known, the following basic rule ofsecurity management is worth repeating:

Ensure all passwords are strong passwords.

You can strengthen passwords by creating and using password policies for yourorganization. For guidelines on securing passwords and for additional ways to protectpasswords, 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 thedatabase listener as that will enable remote administration. For more information,refer to the section "Removing the Listener Password" of Oracle Database NetServices Reference 11g Release 2 (11.2).

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

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

Database Security Features

The 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, customermedical records, or other sensitive information.

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


9/52


Overview 1-3

About Tablespace Encryption - Transparent Data Encryption is one of the threecomponents of the Oracle Advanced Security option for Oracle Database 11gRelease 2 Enterprise Edition. It provides transparent encryption of stored data tosupport your compliance efforts. Applications do not have to be modified and willcontinue to work seamlessly as before. Data is automatically encrypted when it iswritten 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 Accounts

Schema owner should not be the user for normal production; instead the accountshould be locked after the installation.

Closing All Open Ports Not in Use

Keep only the minimum number of ports open and close all ports that are not in use.

Disabling the Telnet Service

Oracle Healthcare Analytics Data Integration Configuration does not use the Telnetservice.

Telnet listens on port 23 by default.

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

Disabling Other Unused Services

In addition to not using Telnet, the Oracle Healthcare Analytics Data IntegrationConfiguration does not use the following services or information for any functionality:

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

Identification Protocol (identd). This protocol is generally used to identify theowner of a TCP connection on UNIX.

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

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

Designing for Multiple Layers of Protection

When designing a secure deployment, design multiple layers of protection. If a hackershould gain access to one layer, such as the application server, that should notautomatically 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, forexample, only allowing communication to the database tier on the port used forSQL*NET communications (1521 by default).


10/52



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

Configuring Secure SQL NET

If the Oracle Data Integrator (ODI) repository is installed in a database server otherthan the server having HDWF schema, the data transfer will take place between twodifferent database servers over a network. As HDWF contains sensitive clinical and

healthcare data, you must secure the communication between database servers. UseOracle Net Manager to configure encryption to secure communication betweendatabase servers. Oracle provides different encryption algorithms to securecommunication. Select an appropriate encryption algorithm. For more information,refer to Oracle Database Advanced Security Administrator's Guide 11g Release 2 (11.1).


11/52

2

Installing Oracle Healthcare Analytics Data Integration 2-1

2Installing Oracle Healthcare Analytics DataIntegration


Installing the Prerequisite Softwareon page 2-1

Setting Up the Databaseon page 2-1

Setting Up ODI Repositorieson page 2-6

Configuring ODI Repositorieson page 2-18

Installation Verificationon page 2-21

2.1 Installing the Prerequisite SoftwareOracle expects that you have good knowledge of concepts and commands of UNIX,Oracle Data Integrator (ODI), and Oracle Database.

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

1. Install Oracle Database 11.2.0.2 (64-bit). Follow the instructions in DatabaseInstallation Guide for .

2. Install Oracle Data Integrator 11.1.1.6. Follow the instructions in ODI InstallationGuide.

3. Install Oracle Healthcare Data Warehouse Foundation 5.0.2. Follow theinstructions in Oracle Healthcare Data Warehouse Foundation Patch Readme andRelease Notes.

2.2 Setting Up the DatabaseThis patch contains the following files required to install the physical data modelportion of OHADI ODI 2.0.2 and the associated documentation:

Table 21 Media Pack Contents

File Name Contains

doc\iguide Secure Installation and Configuration Guide

software\repository XML files for OHADI ODI 2.0.2 (zip format)

software\batchscripts .sh and .bat scripts for the OHADI ODI 2.0.2 installation

software\database SQL scripts for OHADI ODI 2.0.2 installation


12/52

Setting Up the Database


2.2.1 Preinstallation Checklist

Ensure that you have set the NLS_LENGTH_SEMANTICS parameter of thesession creating Metadata Configuration (HMC) schema to either CHAR or BYTEas 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, andRules Metadata Configuration.

Ensure that you have already installed HDWF 5.0.2 to install OHADI ODI 2.0.2. Ifnot already installed, do so by following the respective installation guides.

To install on UNIX, perform the following steps:

1. Download the media pack on to Windows operating system and unzip the mediapack file in the \*.* directory before transferring anyobjects to UNIX operating system.

2. Create a directory in UNIX installation server for copying OHADI ODI 2.0.2installation package files. For example, OHADI_INSTALL_DIR.

3. On the installation server, create four directories inside the for placing SQL scripts, batch scripts, XML files, and log files that will begenerated. For example:

/ohadi_sqls/

/ohadi_xmls/

/ohadi_scripts//ohadi_logs/

4. Transfer the XML files (ODIExport.zip andOHADI_MASTER_REPOSITORY.zip)inbinarymode and other files in textmode from the following locations in Windowsoperating system to OHADI installation directory in UNIX server (for example,OHADI_INSTALL_DIR).

software\batchscripts\*.sh to /ohadi_scripts/

software\database\*.* to /ohadi_sqls/

software\repository\*.* to /ohadi_xmls/

Extract the contents of the ODIExport.zip files in the \ohadi_xmls\ directory using the following command:unzip ODIExport.zip

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

Note: In the following sections, the text enclosed within indicateparameters and you need to provide the parameter values as per yoursystem.

Note: No error message should be prompted upon the execution ofunzip command. Ensure that you can view the list of .xml files in theohadi_xmls directory after they are extracted.


13/52



chmod 755 /ohadi_sqls/*

chmod 755 /ohadi_scripts/*

chmod 755 /ohadi_xmls/*

6. The .sh scripts mentioned in the following installation steps should be executedfrom directory where the scripts are placed. For example, /ohadi_scripts/

To install on Windows, perform the following steps:

1. Download the media pack to Windows operating system and unzip the mediapack file in the \*.* directory.

2. Navigate to the\software\repositorydirectory. Unzipand extract the contents of ODIExport.zip file in the same directory using WinZipapplication.

3. Enter sqlplusin the command prompt and press Enter.

If the following message is displayed in the console:

SQL*Plus: Release 11.2.0.2.0 Production on Wed Jan 16 18:27:47 2013

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Enter user-name:

Exit the command prompt and proceed to the section 2.2.2.

If the following message is displayed in the console:

sqlplus is not recognized as an internal or external command,

operable program or batch file

Right-click on My Computerand select Properties. Click Advancedand thenclick Environment Variables. The Environment Variables window isdisplayed.

Edit the PATH variable from the System Variables window.

Verify if \bin is configured.

For example, if your oracle home directory is:

D:\app\pdogipar\product\11.2.0\dbhome_1, then verifyD:\app\pdogipar\product\11.2.0\dbhome_1\bin exists in PATH variable ornot.

2.2.2 New Installation of Oracle Healthcare Analytics Data Integration ODI 2.0.2

For a fresh installation of OHADI ODI 2.0.2, perform the following steps:

Note: If it does not exist, add the same to PATH variable and keepclicking OKuntil the dialog box is closed and go to step 3.

If it does exist, remove the same from PATH variable and keep

clicking on OKuntil the dialog box is closed and go to step 3.

Note: The following three steps are common for both UNIX andWindows installations.


14/52



1. Log in as SYSTEM user in database by executing the following command in thecommand prompt.

sqlplus /@

(or)

connect to the SYSTEM user using Oracle SQL developer.

2. Create a HMC user with appropriate default tablespace with requisite quotas andtemporary tablespace, and grant the user session privilege.

To create a HMC user:

CREATE USER IDENTIFIED BY DEFAULT

TABLESPACE TEMPORARY TABLESPACE QUOTA ON ;

grant create session to ;

For example:

CREATE USER HMC IDENTIFIED BY DEFAULT TABLESPACE

users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users;

grant create session to HMC;

3. Disconnect SYSTEM user by executing the following command:

SQL>exit;

(or)

Disconnect Oracle SQL developermanually.

To install on UNIX, perform the following steps:

1. Update the environment file /ohadi_scripts/OHADI_ODI_SETENV.sh with appropriate values for SYS_USR, SYS_SID, HDI_USR, HDI_SID, HDM_USR, HDM_SID, HMC_USR, HMC_SID, ORACLE_HOME, SQL_DIR,

BIN_DIR, LOG_DIR, and NOTIFICATION_EMAIL_LIST parameters. Forremaining parameters (ODI_WORK_REP, ODI_HOME, and ODI_XML_DIR),provide blank values (erase the given syntax).

2. After successful completion of step 1, execute the OHADI_ODI_DATABASE_SETUP.sh script from the command prompt by using the following commands:

cd /ohadi_scripts/

sh OHADI_ODI_DATABASE_SETUP.sh

Note: Do not put a slash symbol (/) at the end of the directorydeclaration.


15/52



The execution status of the script can be verified in the $LOG_DIR/OHADI_ODI_DATABASE_SETUP_INSTALL_SUMMARY.log file. Individual SQL file logs also

will be generated in $LOG_DIR/.If any errors are found during the database setup, look for the errors in thecorresponding individual log file and fix them. Execute the failed step manually asper the command used in the script and proceed with further installation.

To install on Windows, perform the following steps:

1. Update the environment file \software\batchscripts\OHADI_ODI_SETENV.bat with appropriate valuesfor the parameters SYS_USR, SYS_SID, HDI_USR, HDI_SID, HDM_USR, HDM_SID, HMC_USR, HMC_SID, SQL_DIR, BIN_DIR, and LOG_DIR. For remainingparameters (ODI_WORK_REP, ODI_HOME, and ODI_XML_DIR) provide blankvalues (erase the given syntax).

2. After successful completion of step 1, execute the OHADI_ODI_DATABASE_SETUP.bat script from the command prompt by using the following commands:

cd \software\batchscripts

OHADI_ODI_DATABASE_SETUP.bat

Note: The script prompts for password to connect to database duringexecution. Password entry is hidden in console. Enter correctpassword and press Enter.

If the password entered is NULL or wrong, the script will display anerror and the script has to be restarted again by providing correctlogin credentials.

The script also prompts for parameters to be passed to the seed dataprocedures. The possible values are Yor N.

Y- Non-EHA_User versioned seed data record will be replaced byEHA_User versioned seed data.

N- Recommended, non-EHA_User versioned seed data record willnot be replaced by EHA_User versioned seed data. Correspondingrecord will be rejected and a log will be entered in the log table.

Note: Do not put a backslash symbol (\) at the end of the directorydeclaration. If any directory name contains spaces, specify the wholepath in double quotation marks. For example, "".


16/52

Setting Up ODI Repositories


If any errors are found during the database setup, look for the errors in thecorresponding individual log file and fix them. Execute the failed step manually as

per the command used in the script and proceed with further installation.

2.3 Setting Up ODI Repositories

The media pack contains the following files used to setup ODI repositories:

Perform the following steps:

1. Create a database schema for ODI master repository and another for ODI workrepository with the following privileges:

a. Log in to database using system user.

CREATE USER IDENTIFIED BY DEFAULT TABLESPACE

TEMPORARY TABLESPACE

QUOTA ON ;

For example:

CREATE USER ohadi_master IDENTIFIED BY ohadi_master DEFAULT

TABLESPACE users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON

users;

Note: The script prompts for password to connect to database duringexecution. Password entry is hidden in console. Enter correctpassword and press Enter.

If the password entered is NULL or wrong, the script can not beexecuted and the script has to be restarted again by providing correctlogin credentials.

The script also prompts for parameters to be passed to the seed dataprocedures. The possible values are Yor N.

Y- Non-EHA_User versioned seed data record will be replaced byEHA_User versioned seed data.

N- Recommended, non-EHA_User versioned seed data record willnot be replaced by EHA_User versioned seed data. Correspondingrecord will be rejected and a log will be entered in the log table.

Note: This section is common for both UNIX and Windowsinstallations.

Table 22 Files for ODI Repositories

File Name Commentssoftware\repository\OHADI_MASTER_REPOSITORY.zip

ODI master repository zip for OHADI ODI 2.0.2.

software\repository\ODIExport.zip Contains all the ETLs along with the import scripts.

software\database\OHADI_WORK_REPOSITORY_UPDATE.sql

Contains SQL statements for work repository schema.


17/52



CREATE USER ohadi_work IDENTIFIED BY ohadi_work DEFAULT TABLESPACE

users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users;

b. Disconnect from system user.

2. Log in to database using sys user with sysdbarole.

a. GRANT ALTER SESSION, CREATE DATABASE LINK, CREATE INDEXTYPE, CREATE

JOB, CREATE MATERIALIZED VIEW, CREATE PROCEDURE, CREATE SEQUENCE,

CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE TRIGGER,

CREATE TYPE, CREATE VIEW to ;

For example:

GRANT ALTER SESSION, CREATE DATABASE LINK, CREATE INDEXTYPE, CREATE



CREATE TYPE, CREATE VIEW to ohadi_master;

GRANT ALTER SESSION, CREATE DATABASE LINK, CREATE INDEXTYPE, CREATE



CREATE TYPE, CREATE VIEW to ohadi_work;

b. GRANT EXECUTE ON DBMS LOCK TO ;

For example:

GRANT EXECUTE ON DBMS_LOCK to ohadi_master;

GRANT EXECUTE ON DBMS_LOCK to ohadi_work;

c. Disconnect from sys user.

Perform the following steps to create an ODI master repository.

2.3.1 Creating a New Oracle Data Integrator Repository Login

Perform the following steps to create a new ODI repository login:

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

Note: The repository names provided in the screenshot are forexplanation of examples. The same naming convention for thescreenshots can be followed if there are no users or connections ofexisting name exists, or follow the own naming convention forrepositories and proceed with the following steps accordingly.


18/52



Figure 21 Create a New ODI Repository Login

2. Click OK. The Repository Connection Informationscreen is displayed.


19/52



Figure 22 Repository Connection Information

Enter the following values:

Login Name: OHADI_MASTER_REPOSITORY

User: SUPERVISOR

Password: SUNOPSIS (you can change it once import is completed successfully)

User:

Password:

Driver List: Select Oracle JDBC Driver from the list.

Driver Name: oracle.jdbc.oracledriver

Url: Set appropriate values based on your database details.

3. Click OK. A login name is created with the name given in the first property (forexample, OHADI_MASTER_REPOSITORY here).

2.3.2 Importing Master RepositoryPerform the following steps to import a master repository:

1. Navigate to ODI> File> New> Master Repository Import Wizard.


20/52



Figure 23 Importing a Master Repository

2. Click OK. The Master Repository Import Wizardscreen is displayed.

Figure 24 Master Repository Import Wizard



21/52



Login: Select the login created in step 2.

JDBC Driver: Will be populated automatically.

JDBC Url: Will be populated automatically.

Userand Password: Will be populated automatically. Leave them as is.

DBA Userand DBA Password: Enter appropriate values.

Id: Enter a number.

Use a Zip file: Check this box. Navigate to software> repositoryfolder and select

the OHADI_Master_Repository.zip file.3. Click Finish. The master repository will be created.

2.3.3 Creating a New Oracle Data Integrator Work Repository

Perform the following steps to create a new ODI work repository:

1. To create a new ODI work repository, open an ODI console window and log intoOHADI_MASTER_REPOSITORY login that was created in Step 1 in Section 2.3.1.

2. Connect to the master repository and navigate to Topology> Repositories> WorkRepositories. Right-click Work repositoriesand select New Work Repository. TheCreate Work Repositoryscreen is displayed:

Note: ODI does not support single ID system for repository IDs. TheIDs used in one repository cannot be used in another repository whileimporting that particular repository.

The repository provided contains repository IDs 321, 999, and 100 forthe master repository. Ensure that you provide an ID other than theseIDs in the text box of Idfield.


22/52



Figure 25 ODI Work Repository Connection Properties

Enter the following values in the screen:

Technology: Select Oracle from the list.

JDBC Driver: As per your database details

JDBC Url: As per your database details

User: Database schema created for work repositoryPassword: Database schema password created for work repository

3. Click Test Connectionto check if the connection is successful.

4. Click Next. The Specify ODI Work Repository Propertiesscreen is displayed.


23/52



Figure 26 ODI Work Repository Properties

Enter the following details:

Name: Enter the name of the work repository. For example, OHADI_WORK_REPOSITORY.

Password: It is optional to enter a value in this field.

Id: Enter a number.

5. Click Finish. The work repository will be created. You will be prompted to create alogin for the same work repository as shown below.


Ensure that you provide an ID other than these values (1, 2, 3, 4, 5, 6,7, 11, 39, 61, 67, 86, 123, 131, 201, 327, 440, 499, 645) in the text box of Idfield.


24/52



Figure 27 Create a Login for the New Work Repository

6. Click Yes. The login screen is displayed.

Figure 28 Login to Work Repository

7. Specify the login name and Click OK.

8. Disconnect from the master repository by selecting ODIand then Disconnect"OHADI_MASTER_REPOSITORY"from the menu bar.

2.3.4 Importing Scripts

Perform the following steps to import scripts to the work repository:

1. Log in to OHADI_WORK_REPOSITORY.

Figure 29 ODI Login

2. Open ODI Studio Login and enter the following details:

Login Name: Select OHADI_WORK_REPOSITORY

User: Supervisor

Password: SUNOPSIS


25/52



To import the ODI objects on Linux environment, follow these steps:

1. Modify odiparams.sh file present in \oracledi\agent\bindirectory with the necessary credentials to connect to the ODI repository. You needto set the following parameters:

ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver

ODI_MASTER_URL=jdbc:oracle:thin:@::

ODI_MASTER_USER=

ODI_MASTER_ENCODED_PASS=

a. To provide the encoded password, from the command prompt, navigate tothe \oracledi\agent\bin directory and enterthe following command:

sh encode.sh

b. Copy and paste the output value returned by the command for the aboveparameter.

ODI_SUPERVISOR=SUPERVISOR

ODI_SUPERVISOR_ENCODED_PASS=

a. To provide the encoded password, from the command prompt, navigate tothe \oracledi\agent\bin directory and enterthe following command:

sh encode.sh SUNOPSIS

b. Copy and paste the output value returned by the command for the aboveparameter.

c. ODI_SECU_WORK_REP=

Enter the name of the work repository created in section Section 2.3.3.

ODI_MAX_HEAP=1024m

2. Modify $ODI_HOME/bin/odiparams.sh to add timeout parameter by changingfollowing line:

ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy

-Doracle.security.jps.config=./jps-config.xml $ODI_PARAMS_JAVA_OPTION"

to

ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy

-Doracle.security.jps.config=./jps-config.xml

-Doracle.odi.jdbc.connection.timeout=300 $ODI_PARAMS_JAVA_OPTION"

3. Update appropriate values for the following parameters in OHADI_ODI_SETENV.sh located at OHADI_INSTALL_DIR>/ohadi_scripts/.

ODI_WORK_REP, ODI_XML_DIR, ODI_HOME

4. Navigate to /ohadi_scripts/and run OHADI_ODI_MASTER_IMPORT.shusing the following command:

nohup sh OHADI_ODI_MASTER_IMPORT.sh &

Note: Save the file once all the parameters are set properly.


26/52



The status of the import process can be checked in $LOG_DIR/ OHADI_ODI_IMPORT_INSTALLSUMMARY.log file.

The summary log file looks as follows:

NO OF XMLS IMPORTED SUCCESSFULLY:

NO OF XMLS FAILED TO IMPORT:

5. If there are any failures (indicated by NO OF XMLS FAILED TO IMPORT: ,where n is the number of failed ETL imports) in the summary log file, fix theissues and execute the following retry script:

nohup sh OHADI_ODI_IMPORT_RETRY.sh &

Status of the retry script can be checked in $LOG_DIR/OHADI_ODI_INSTALLSUMMARY.log file.

The summary log file looks as follows:

NO OF XMLS IMPORTED SUCCESSFULLY:

NO OF XMLS FAILED TO IMPORT:

6. Run the following SQL file against the work repository schema:

/ohadi_sqls/OHADI_WORK_REPOSITORY_UPDATE.sql

Execute the following commands:

cd /ohadi_sqls/

. /ohadi_scripts/OHADI_ODI_SETENV.sh

$ORACLE_HOME/bin/sqlplus /@ @/ohadi_sqls/OHADI_WORK_

REPOSITORY_UPDATE.sql

To import the ODI objects on Windows environment, perform the followingsteps:

1. Ensure the following environment variables are set:

a. Right-click on My Computerand select Properties. Click Advancedand thenclick Environment Variables. The Environment Variables window is

displayed. Configure the following three environment variables (2 system, 1user variables):

Add system environment variable ODI_HOMEthat points to \oracledi\agent directory.

Update system environment variable PATHto ;\oracledi\agent\bin directory.

Add user environment variable %classpath%pointing to %classpath%.

Note: No further retry script will be generated if failure occurs inOHADI_ODI_IMPORT_RETRY.sh. The failed ETL has to be importedby executing the individual import.


27/52



b. Once these three variables are added, keep clicking OK until the EnvironmentVariables window is closed.

2. Modify odiparams.bat file present in \oracledi\agent\bindirectory with the necessary credentials to connect to the ODI repository. Set thefollowing parameters:

set ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver

set ODI_MASTER_URL=jdbc:oracle:thin:@::

set ODI_MASTER_USER=

set ODI_MASTER_ENCODED_PASS=

a. To provide the encoded password, from the command prompt, navigate tothe \oracledi\agent\bin directory and enter thefollowing command:

encode.bat

b. Copy and paste the output value returned by the command carefully forthe parameter.

set ODI_SUPERVISOR=SUPERVISOR set ODI_SUPERVISOR_ENCODED_PASS=

a. To provide the encoded password, from the command prompt, navigate tothe \oracledi\agent\bin directory and enter thefollowing command:

encode.bat SUNOPSIS

b. Copy and paste the output value returned by the command carefully forthe above parameter.

Set ODI_SECU_WORK_REP=

Enter the name of the work repository created in step 4 in Section 2.3.3.

set ODI_MAX_HEAP=1024m

3. Modify $ODI_HOME/bin/odiparams.bat to add timeout parameter by changingfollowing line:

SET ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy""-Doracle.security.jps.config=./jps-config.xml" %ODI_PARAMS_JAVA_OPTION%

to

SET ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy-Doracle.security.jps.config=./jps-config.xml-Doracle.odi.jdbc.connection.timeout=300" %ODI_PARAMS_JAVA_OPTION%

Save the file once all the parameters are set.

4. Update appropriate values for the following parameters in OHADI_ODI_SETENV.bat located at /software/batchscripts/: ODI_WORK_REP, ODI_XML_DIR, ODI_HOME

5. From the command prompt, navigate to the path /software/batchscripts/ and run OHADI_ODI_MASTER_IMPORT.bat using thefollowing command:

OHADI_ODI_MASTER_IMPORT.bat


28/52

Configuring ODI Repositories


The status of the import process can be checked in %LOG_DIR%/ OHADI_ODI_VALIDATE_IMPORT.log. The success count and failure count are displayed at theend of the log file as follows:

SUCCESS_COUNT = 3662

FAILURE_COUNT = 0

Additionally, individual log files will also be created in the same directory.6. Run the following SQL file against the work repository schema:

/ohadi_sqls/OHADI_WORK_REPOSITORY_UPDATE.sql

Execute the following commands:

cd /software/batchscripts/

OHADI_ODI_SETENV.bat

sqlplus /@

@/software/database/OHADI_WORK_REPOSITORY_

UPDATE.sql

2.4 Configuring ODI RepositoriesThis section is common for both UNIX and Windows installations.

Configuring Physical Data Server

When the master repository is imported, three Physical Data Servers will be createdwith following names:

HDI connects to HDWF Interface database schema

HDWF connects to HDWF database schema

HMC connects to Metadata Configuration database

1. Connect to work repository by selecting OHADI_WORK_REPOSITORY as yourlogin name.

Figure 210 Log into Work Repository


Login Name: OHADI_WORK_REPOSITORY

User: Supervisor

Password: SUNOPSIS


29/52



2. Navigate to Topology> Physical Architecture> Expand Technology. Expand theOraclenode and double-click the physical data server created for HDI.

Figure 211 Navigate to Physical Data Server

3. In the Definitiontab, update the values for the properties:

User: Database schema user of HDWF Interface schema

Password: Database schema password for HDWF interface schema

Instance/dblink (data Server): Connect string, for example, orcl.

Figure 212 Connection Properties

4. In theJDBCtab, update the values of host, port, and sid in the JDBC URLconnection, "jdbc:oracle:thin:@::" for HDWF interface schema.

5. Click Savefrom the menu bar. The existing Physical Data Server HDI will beupdated.

6. In addition, you can also verify whether the provided values are correct or not byusing the Test Connectionoption.

7. Now repeat steps 2 through 6 for HDWF and HMC physical data servers.


30/52



Configuring Physical Schema

1. To update the existing physical schema for HDI, navigate to HDI data server in theTopologytab and expand the HDIdata server node as configured above.Double-click HDI.HDI_ODI_202as displayed in the following figure:

Figure 213 Select Physical Schema

2. In the Definitiontab, select the HDWF interface schema name from the dropdown menus for the Schema (Schema)and Schema (work Schema) optionsaccordingly.

Figure 214 Configure the Physical Schema

Note: This screenshot is only for information purpose. You may seedifferent physical schema name in your system.


31/52

Installation Verification


3. Click Savefrom menu. The existing physical schema will be updated.

4. Repeat steps 1 through 3 for HDWF and HMC physical data servers.

5. Review all the above configurations again before going to next section.

For more information on configuring the Topology, refer to ODI documentation.

2.5 Installation VerificationFor installing on UNIX, perform the following steps to validate your OHADIinstallation:

1. Run the following script to drop foreign key constraints.

sh OHADI_ODI_DROP_IDX_VALIDATION.sh

If prompted, enter valid HDM schema password. Password entry is hidden inconsole, so type correct password and press Enter. The script will display an errorif wrong credentials are entered. Then the script has to be restarted again byentering correct credentials.

The status of the script can be verified in $LOG_DIR/OHADI_ODI_DROP_IDX_VALIDATION_SUMMARY.log

The summary log looks as follows:

### START OF SCRIPT EXECUTION###

OHADI_DROP_IDX_VALIDATION.sql : success

### SCRIPT COMPLETED ###

2. Execute the following validation script:

sh OHADI_ODI_INSTALL_VERIFICATION.sh

When prompted, enter valid HDI schema password and HDM schema password.Password entry is hidden in console, so type correct password and press Enter.The script will display an error if wrong credentials are entered. Then the scripthas to be restarted again by entering correct credentials.

3. The status of the execution of step 2 can be verified in the following file:

Note: Before proceeding to install verification, ensure all thepreceding steps are completed successfully.

Note: All the scripts have to be executed from /ohadi_scripts/ directory.

Note: The above script contains three script executions internally insequential order.

The first script loads test data in HDWF interface tables.

The second script runs corresponding ETLs to load the data in HDM.

The third script checks and notifies if the data is being loaded toHDWF tables or not.


32/52



$LOG_DIR/OHADI_ODI_INSTALL_VERIFICATION_SUMMARY.log


#### STARTED THE SCRIPT EXECUTION ##

OHADI_INSTALLTEST_TESTDATA_CREATION.sql :

OHADI_INSTALLTEST_EXECUTE_INITIALLOAD_ETLS.sh :

OHADI_INSTALLTEST_VALIDATERESULT.sql :

#### END OF SCRIPT EXECUTION ##

4. After OHADI ODI 2.0.2 has been successfully installed, execute the followingscript to delete test data inserted into HDI tables and loaded to HDM tables.

sh OHADI_ODI_DELETE_TEST_DATA.sh

When prompted, enter valid HDI schema password and HDM schema password.Password entry is hidden in console, so type the correct password and press Enter.The script can not be executed if wrong credentials are entered. Then the script hasto restarted again by entering correct credentials.

The script status can be checked in $LOG_DIR/OHADI_ODI_DELETE_TEST_DATA_SUMMARY.log

5. Run the following script to create foreign key indexes:

sh OHADI_ODI_CREATE_IDX_VALIDATION.sh

When prompted, enter valid HDM schema password. Password entry is hidden inconsole, so type the correct password and press Enter. The script can not beexecuted if wrong credentials are entered. Then the script has to restarted again byentering correct credentials.

The status of the script can be checked in $LOG_DIR/OHADI_ODI_CREATE_IDX_VALIDATION_SUMMARY.log



OHADI_CREATE_IDX_VALIDATION.sql : success


6. Run the following script to revert the load date value in the configuration table:

sh OHADI_ODI_RESET_LOADDATE.sh

When prompted, enter valid HMC schema password. Password entry is hidden inconsole, so type the correct password and press Enter. The script can not beexecuted if wrong credentials are entered. Then the script has to restarted again byentering correct credentials.

Note: You must verify the following files for any errors:

$LOG_DIR/OHADI_INSTALLTEST_TESTDATA_CREATION.log

$LOG_DIR/OHADI_INSTALLTEST_VALIDATERESULT.log

If the validation script OHADI_INSTALL_VERIFICATION.sh has tobe rerun, first execute the delete script OHADI_DELETE_TEST_DATA.sh and then proceed from step 1.


33/52



The status of the script can be verified in $LOG_DIR/OHADI_ODI_RESET_LOADDATE_SUMMARY.log



OAHDI_RESET_LOADDATE.sql : success


To install on Windows, perform the following step:

From the command prompt, navigate to the /software/batchscripts directory and run the script OHADI_ODI_

INSTALLTEST.bat by using the below command:OHADI_ODI_INSTALLTEST.bat

The script will display the status of the installation in the %LOG_DIR%\OHADI_INSTALLTEST_VALIDATE_RESULT.log file.

The following message is displayed in the file if the installation is successful:

INSTALLATION SUCCEEDED: TARGET TABLES LOADED!

If installation contains any errors then the following message is displayed in thefile:

ERROR: TARGET TABLES NOT LOADED

Note: If the install verification has to be re-executed, then performthe following steps:

Execute step 6 first.

Execute from step 1 through step 5.


34/52




35/52

3

Installing Oracle Enterprise Healthcare Analytics Health Language International Integration 3-1

3Installing Oracle Enterprise HealthcareAnalytics Health Language International

Integration


Setting Up ODI Repositorieson page 3-1

Configuring ODI Repositorieson page 3-10

3.1 Setting Up ODI RepositoriesThe following files for ODI repositories are present in software> repositoryfolder.

1. You must create a database schema for ODI master repository and for ODI workrepository with the privileges mentioned in Section 2.3, "Setting Up ODIRepositories".

2. Get the master repository and work repository zip files from installation package.The file names of repository are:

EHA_HLI_Master_Repository.zip

EHA_HLI_Work_Repository.zip

To create the ODI Master repository, perform the following steps:

1. To create a new ODI repository, log into ODI and navigate to File> New> Createa new ODI repository Login.

Table 31 Files for ODI Repositories

File Name Contains

EHA_HLI_Master_Repository.zip ODI master repository zip for EHA HLI Integration

EHA_HLI_Work_Repository.zip ODI work repository zip for EHA HLI Integration

Note: The repository names provided in the screenshot are forexplanation of examples. The same naming convention for thescreenshots can be followed if there are no users or connections ofexisting name exists, or follow the own naming convention forrepositories and proceed with the following steps accordingly.


36/52



Figure 31 Creating a new ODI Repository

2. Click OK. The Repository Connection Information screen is displayed. You mustprovide necessary values for all properties.

Figure 32 Repository Connection Details


37/52




Login Name: EHA_HLI_MASTER_REPOSITORY

User: SUPERVISOR

Password: SUNOPSIS

User:

Password:

Driver List: Select Oracle JDBC Driver from the list.

Driver Name: oracle.jdbc.oracledriver

Url: Set appropriate values based on your database details.

3. Click OK. A login name is created with the name given in the first property (forexample, EHA_HLI_MASTER_REPOSITORY).

4. To import the master repository, navigate to ODI> File> New> MasterRepository Import Wizard.

Figure 33 Importing the Master Repository

5. Click OK. The Master Repository Import Wizard screen is displayed.


38/52



Figure 34 Repository Connection Information


Login: Select the login created in step 2.

JDBC Driver: Will be populated automatically.

JDBC Url: jdbc:oracle:thin: Will be populated automatically.

Userand Password: Will be populated automatically. Leave them as is.

DBA Userand DBA Password: Enter appropriate values.

Id: Enter a number.

Use a Zip file: Select this check box. Navigate to software> repositoryfolder andselect the EHA_HLI_Master_Repository.zip file.

6. Click Finish. The master repository will be created.

7. To create a new ODI work repository, open an ODI console window and log in toEHA_HLI_MASTER_REPOSITORY login that is created in Step 1.

8. Connect to the master repository and navigate to Topology> Repositories> WorkRepositories. Right-click Work repositoriesand select New Work Repository. TheCreate Work Repository screen is displayed.


The existing installation zip file already contains certain repositoryIDs 33, 321, 999 for the master repository. Ensure that you provide anID other than these values in the ID field whenever a warningappears.


39/52



Enter the following values in the screen:

Technology: Select Oracle from the list.

JDBC Driver: As per your database details

JDBC Url: As per your database details

User: Database schema created for work repository

Password: Database schema password created for work repository9. Click Test Connectionto check if the connection is successful.

10. Click Next. The Specify ODI Work Repository Properties screen is displayed.


40/52



Figure 35 Specify ODI Work Properties


Id: Enter a number.

Name: Enter EHA_HLI_WORK_REPOSITORY.

Password: It is optional to enter a value in this field.

11. Click Finish. The work repository will be created. You will be prompted to create alogin for the same work repository as shown:

Note: ODI does not support single ID system for repository IDs. TheIDs used in one repository cannot be used in another repository while

importing that particular repository.The existing installation zip file already contains certain repositoryIDs 1, 2, 3, 4, 5, 33, 100, 102, 201, 222, 322, 624, 625, 626, 785 for thework repository. Ensure that you provide an ID other than thesevalues in the ID field.


41/52



Figure 36 Create a Login for Work Repository

12. Click Yes. The login screen is displayed.

Figure 37 Login Name

13. Specify the login name and Click OK.

14. Disconnect from the master repository.

15. To import a work repository into ODI from a zip file, connect to work repositoryby selecting EHA_HLI_WORK_REPOSITORY as your login name.

Figure 38 Log in to Work Repository


Login Name: EHA_HLI_WORK_REPOSITORY

User: Supervisor

Password: SUNOPSIS

16. To import a work repository into ODI from EHA_HLI_Work_Repository.zip file,navigate to Designer> Import.


42/52



Figure 39 Select Import

17. The Selection screen is displayed. Select Import the Work Repository.

Figure 310 Import Work Repository

18. In the Import Work Repository screen:

Select Synonym Mode INSERT_UPDATEas the Import Mode.

Select Import From a Zip File.

Enter the path to EHA_HLI_Work_Repository.zip.


43/52



Figure 311 Import from Zip File

19. A Confirmation dialog box is displayed for each ID used in zip file. Click Yesonall dialog boxes until you see Import is in Progressdialog box.

Figure 312 ID Declaration Confirmation Screen

20. Once the import is completed, the Import Report screen is displayed. In the ImportReport screen, scroll down to the end. The last four sections should have zeroobjects if the import is successful as shown:

Figure 313 Import Report Screen


44/52



3.2 Configuring ODI Repositories

Configuring Physical Data Server

When the master repository is imported, the following Physical Data Servers will becreated with these names:

HDI - connects to HDWF Interface database

HMC - connects to Metadata Configuration database

HLI_DATA - connects to the Physical folder location having HLI Data Files

1. Open ODI studio and click Connect To Repositoryand select the loginEHA_HLI_WORK_REPOSITORYand click OK.

Figure 314 Log in to Work Repository


Login Name: EHA_HLI_WORK_REPOSITORY

User: Supervisor

Password: SUNOPSIS

2. Navigate to Topology> Physical Architecture> Technologies> Oracle.

Double-click HDI.

3. In the Definitiontab, update the values for the following properties:

User: Database schema user of HDWF Interface schema


45/52



Password: Database schema password for HDWF interface schema

Instance/dblink (data Server): Connect string, for example, ORCL.

Figure 315 Enter Details for HDI

4. In theJDBCtab, update the values of the JDBC system connection, which containsHDWF interface schema.

5. Click Savefrom the menu. The existing Physical Data Server HDI will be updated.

6. Click Test Connectionon the top. Click Testin the next screen to verify if theconfiguration is correct.

7. Repeat steps 1 through 6 for HMC physical data server.

Configuring Database Physical Schema

1. To update the existing physical schema for HDI, navigate to Topology> Oracle>HDI. Expand HDI and double-click HDI.HDI_V502.


46/52



Figure 316 Select the Physical Schema

2. In the Definitiontab, select the appropriate values accordingly.

Select the actual physical database schema name of HDI from the drop-down lists.

Figure 317 Update the Schema Properties

3. Click Savefrom menu. The existing physical schema will be saved.

4. Repeat steps 1 through 3 for HMC physical data server.

HLI_DATA File Data Server

1. Navigate to Topology> Physical Architecture> Technologies> File. Double-clickHLI_DATA.


47/52



Figure 318 HLI_DATA File Data Server

2. In theJDBCtab, update the values of the JDBC Driver and JDBC URL as shown:

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

JDBC URl: jdbc:snps:dbfile

Figure 319 Update Values in JDBC Tab

Configuring File Physical Schema

1. To update the existing physical schema for HLI_DATA, navigate to Topology>Physical Architecture> Technologies> File> HLI_DATA. Double-click the

physical schema.


48/52



Figure 320 Update the Physical Schema for HLI_Data

2. In the Definitiontab, specify the actual physical folder location of the HLI DataFiles for the properties Directory (Schema) and Directory (Work Schema).

3. Click Savefrom menu. The existing physical schema will be saved.

4. For Windows machine, perform the following steps (for UNIX machineinstallation, skip this step).

a. Disconnect from the work repository (EHA_HLI_WORK_REPOSITORY).

b. Run the following query against the HLI work repository schema:

UPDATE SNP_TABLE

SET FILE_SEP_ROW='\u000D\u000A'

WHERE RES_NAME IN (

'#EHA_HLI_INTEGRATION.VAR_CODE_FILE_NAME',

'#EHA_HLI_INTEGRATION.VAR_RELATED_ENTITY_FILE_NAME',

'#EHA_HLI_INTEGRATION.VAR_CODE_HIERARCHY_FILE_NAME',

'#EHA_HLI_INTEGRATION.VAR_RELATIONSHIP_TYPE_FILE_NAME',

'#EHA_HLI_INTEGRATION.VAR_CODE_DESCRIPTION_FILE_NAME');

c. Connect to the work repository back (EHA_HLI_WORK_REPOSITORY) and

proceed with the post installation steps.

3.2.1 Post Installation Steps

The following post installation steps are mandatory for OHADI to work:

1. Open ODI studio.

Note: For further references on Topology configuration, see ODIdocumentation.

Note: If the source file are transferred from Windows to UNIXmachine, transfer it using the TEXT mode.


49/52



2. Click Connect to Repository, select the login EHA_HLI_WORK_REPOSITORY,and click OK.

3. In the Designertab:

a. Navigate to the project EHA HLI Integration, select the Globalfolder.

b. Select the package GENERATE ALL SCENARIOS, right-click on the package,

and select Execute.The Execute dialog box is displayed.

c. Click OK.

d. Click OKin the Information dialog box.

4. In the Designertab, click the Load Plans and Scenariostab. Select and execute thescenario LOAD_GLOBAL Version 001.

5. Create a flat file Code.txt with the following two records in the configured folderlocation:

"ConceptId"~`^"Code"~`^"Description"~`^"CodeSystem"~`^"CodeVersion"~`^"

EffectiveDate"~`^"ExpirationDate"~`^"CreationDate"~`^"LastModifiedDate"

~`^"Status"

"ID123456"~`^"CODE1234"~`^"Code Description testing"~`^"CD_TEST_

SYSTEM"~`^"CD_TEST_SYS_VER_

1:2:3"~`^"01/10/2000"~`^"01/10/2999"~`^"01/10/2003"~`^"02/01/2999"~`^"C

URRENT"

6. In the Designertab, click the Load Plans and Scenariostab. Select and execute the

scenario LOAD_HDI_CD_SYS Version 001.A record should be loaded in HDI_CD_SYS.

7. Delete the file Code.txt from the configured folder location.

To delete the test record inserted into HDI_CD_SYS, perform the following steps:

a. Login to the HDI schema using sqlplus.

For connecting to sqlplus, see Section 2.2, "Setting Up the Database".

b. Execute the following command:

DELETE FROM HDI_CD_SYS WHERE INT_ID='CD_TEST_SYSTEM~CD_TEST_SYS_

VER_1:2:3';

This command will delete a record.

c. Commit the transaction by running the following command:

COMMIT;

Note: Ensure only two lines are showing up in the flat file. If therecords split into multiple lines, rearrange the records to show onlytwo lines.


50/52




51/52

Index-1

Index

C

configuring ODI repositories, 2-18

H

health language international, 3-1hli, 3-1

configuring ODI repositories, 3-10setting ODI repositories, 3-1

P

prerequisite software, 2-1

R

related documents, vi

S

security, 1-1

setting updatabase, 2-1ODI repositories, 2-6

T

technology stack, 1-1


52/52

How to Install OHADI

Documents

Transcript of How to Install OHADI