This chapter describes the steps required to install the OHF Data Management Assembly for Informatica. There are two ways to install the Data Management Assembly for Informatica, depending on how you create the user schemas. The installer can create the user schemas during the installation or you can create them manually, prior to the installation. After the installation is complete, you must assign the integration service to the workflows:
Installing the Data Management Assembly without Pre-Created User Schemas
Installing the Data Management Assembly with Pre-Created User Schemas
The user is familiar with Oracle Database (DB), Informatica, and Linux OS. | |
The OHF Data Model is installed.
Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 9, "Data Model Upgrade". |
|
Make sure that the database compatible parameter is set to 12.1.0.2.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.1.0.2.0, ask your database administrator to set it. |
|
The Informatica domain is running and no user is connected to the Informatica Admin Console. | |
Informatica services can connect to the Data Model 7.1.1 database mentioned in the Oracle TNS file (TNS entries of the required database must be available in the installation server tnsnames.ora file). | |
You can connect the database using EZCONNECT syntax. For example, sqlplus <user>/<password>@<hostname>:<port>/<service name>. | |
The password expiry notification message does not display for the system user. | |
The installer is run on the system where the Informatica server is installed. | |
The terminology loaders source file location exists. The installer creates an archive directory. For example,
/scratch/home/oemora/TL_Source is the source file location specified during installation, which already exists. /scratch/home/oemora/TL_Archive_Files is created by the installer as the archive directory. |
|
The path of the data file (Configuration schema/Repository schema tablespace) mentioned when creating the tablespace is correct. Make sure that the database user has write privileges. | |
Enough space is available in the installation directory and the Oracle Home directory. | |
The Sqlplus utility is available on the installation server. | |
The impdp utility is available on the repository database server. | |
The installation user has read, write, and execute privileges to the $INFA_HOME/server folder. The installer creates product specific folders and parameter files under this location. | |
For remote installations, where the installation server and the Informatica Repository Database are on different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. | |
Back up the following csv files under $INFORMATICA_HOME/server/infa_shared/SrcFiles if it exists:
|
|
If the Terminology Loaders source folder is shared, make a back up of the following files:
The installer will overwrite any existing files from the list above. |
Extract the contents of the OHF media pack to your system. | |
Navigate to the <media_pack_location>/ folder. | |
Unzip the OHF_V711_Linux-x64.zip file where you want to launch the installer using the following command:
|
|
Navigate to the Disk1/install folder. | |
Change the protection on files as follows:
|
Start the Oracle Universal Installer by running the following command:
If the Informatica repository schemas to be created are on the database instance of the installation server, execute:
sh runInstaller.sh -local
If the Informatica repository database or OHF data model database is on the database instance of another server, execute:
sh runInstaller.sh -local remote_installation=true
where, the -local
option is to install on the local node irrespective of the cluster nodes specified on the installer machine.
Screen | Action | |
---|---|---|
Welcome | Click Next. | |
Select a Product to Install | Select the Oracle Healthcare Foundation Data Management Assembly for Informatica 7.1.1.0.0 option. | |
Specify Home Details | Enter or select the installation home path. | |
Verify Installation Prerequisites | Verify if all the prerequisites are met before proceeding. | |
Oracle Home Configuration | Specify the Oracle client home path. | |
Select the Informatica Home Location | Specify the Informatica home location.
The Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/. |
|
Select Database Server for Informatica Repository Schemas | Select one of the following options for the Informatica repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) | Enter the following mounted directory configuration details in which the remote server directory is mounted:
To obtain the available storage drives, on the Linux machine, execute the <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% /installation server Note:
|
|
Specify Healthcare Data Model Database Instance Details | Enter values for the following fields:
|
|
Specify Informatica Repository Database Instance Details (applicable only if you selected No in the previous screen for Select this database instance for repository schema creation) | Enter values for the following fields:
|
|
Select Terminology Loaders Source Location | Specify the Terminology loaders source file location.
This location is used to read the terminology loaders source data files. You can change this location when required. The installer creates an archive directory at the same level as the source directory. Make sure that the create directory privileges exist for the installation user. |
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Warehouse Integration Loader Details | Enter values for the following fields:
The installer creates a configuration schema if it does not exist. If you provide an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>). The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose all existing objects. |
|
Specify Healthcare Common Data Mart Loader Details | Enter values for the following fields:
The installer creates a configuration schema if it does not exist. If you provide an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>). The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose all existing objects. |
|
Specify Healthcare Cohort Data Mart Loader Details | Enter values for the following fields:
If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>). The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose the existing objects. The configuration schema is not required for CDM. |
|
Specify Tablespace Details (if prompted) | Specify the tablespace names for the configuration schemas. The installer creates these tablespaces if they do not exist.
|
|
Specify Tablespace Details (if prompted) | Specify the tablespace names for repository schemas. The installer creates these tablespaces if they do not exist in the database.
|
|
Specify Tablespace Location for Configuration Schema (if prompted) | Specify the tablespace location for the Configuration schema.
The location should be present in the OHF data model database server with write privileges. If the OHF data model database is not on the installation server, you must enter the location manually. |
|
Specify Tablespace Location for Repository Schema (if prompted) | Specify the tablespace location for the repository schemas.
When the repository database is not on the installation server, you must enter the location manually. The location should be present on the repository database server with write privileges. |
|
Specify Informatica Domain Details | Specify the following parameters:
Contact your Informatica Administrator for the Domain Code Page ID and provide a valid Code Page ID. Make sure that the code page is compatible with the domain code page for creating the Integration Service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows:
|
|
Verify Configuration Parameters | Click Next. | |
Summary | Click Install. | |
End of Installation | Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
The user is familiar with Oracle Database (DB), Informatica, and Linux OS. | |
The OHF Data Model is installed.
Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 9, "Data Model Upgrade". |
|
Make sure that the database compatible parameter is set to 12.1.0.2.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.1.0.2.0, ask your database administrator to set it. |
|
The Informatica domain is running and no user is connected to the Informatica Admin Console. | |
Informatica services can connect to the Data Model 7.1.1 database mentioned in the Oracle TNS file (TNS entries of the required database must be available in the installation server tnsnames.ora file). | |
You can connect the database using EZCONNECT syntax. For example, sqlplus <user>/<password>@<hostname>:<port>/<service name>. | |
The password expiry notification message does not display for the system user or pre-created schemas. | |
The installer is run on the system where the Informatica server is installed. | |
The terminology loaders source file location exists. The installer creates an archive directory. For example,
/scratch/home/oemora/TL_Source is the source file location specified during installation, which already exists. /scratch/home/oemora/TL_Archive_Files is created by the installer as the archive directory. |
|
The path of the data file (Configuration schema/Repository schema tablespace) mentioned when creating the tablespace is correct. Make sure that the database user has write privileges. | |
Enough space is available in the installation directory and the Oracle Home directory. | |
The Sqlplus utility is available on the installation server. | |
The impdp utility is available on the repository database server. | |
The installation user has read, write, and execute privileges to the $INFA_HOME/server folder. The installer creates product specific folders and parameter files under this location. | |
For remote installations, where the installation server and the Informatica Repository Database are on different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. | |
Back up the following csv files under $INFORMATICA_HOME/server/infa_shared/SrcFiles if it exists:
|
|
If the Terminology Loaders source folder is shared, make a back up of the following files:
The installer will overwrite any existing files from the list above. |
Create the following default and temporary tablespaces with appropriate quotas. You can use different tablespace names than the ones listed below.
Note:
The hmc_ts and hmc_temp tablespaces must be created in the Data Model database instance.Tablespace Name | Big File Tablespace | Description | |
---|---|---|---|
infarep_ts | Yes | Default tablespace for the Repository schema | |
infarep_temp | Yes | Temporary tablespace for the Repository schema | |
hmc_ts | Yes | Default tablespace for the Configuration schema | |
hmc_temp | Yes | Temporary tablespace for the Configuration schema |
Create the following user schemas and assign the appropriate default and temporary tablespaces. Refer to Create Default and Temporary Tablespaces for details. If you created tablespaces with different names, use those instead.
Schema Name | Schema Description | Default Tablespace | Temporary Tablespace | |
---|---|---|---|---|
wil_hmc | Warehouse Integration Loader Configuration schema | hmc_ts | hmc_temp | |
hcd_hmc | Healthcare Common Data Mart Configuration schema | hmc_ts | hmc_temp | |
wil_rep_711 | Warehouse Integration Loader Repository schema | infarep_ts | infarep_temp | |
hcd_rep_711 | Healthcare Common Data Mart Repository schema | infarep_ts | infarep_temp | |
cdm_rep_711 | Healthcare Cohort Data Mart Repository schema | infarep_ts | infarep_temp |
Extract the contents of the OHF media pack to your system. | |
Navigate to the <media_pack_location>/ folder. | |
Unzip the OHF_V711_Linux-x64.zip file where you want to launch the installer using the following command:
|
|
Navigate to the <media_pack_location>/Disk1/stage/Components/oracle.hsgbu.hc.dma.infa/7.1.1.0.0/1/DataFiles/Expanded/filegroup1 directory. | |
Unzip the dma_infa_master_install.zip file. | |
Navigate to the dma_infa_master_install/hmc_infa_install/ directory. | |
Connect to the system user and execute the following scripts:
|
|
Navigate to the <media_pack_location>/Disk1/install folder. | |
Change the protection on files as follows:
|
Start the Oracle Universal Installer by running the following command:
If the Informatica repository database or the OHF data model database is on the database instance of the installation server, execute:
sh runInstaller.sh -local dba_tasks=false
If the Informatica repository schemas to be created are on the database instance of another server, execute:
sh runInstaller.sh -local remote_installation=true dba_tasks=false
where, the -local
option is to install on the local node irrespective of the cluster nodes specified on the installer machine.
Screen | Action | |
---|---|---|
Welcome | Click Next. | |
Select a Product to Install | Select the Oracle Healthcare Foundation Data Management Assembly for Informatica 7.1.1.0.0 option. | |
Specify Home Details | Enter or select the installation home path. | |
Verify Installation Prerequisites | Verify if all the prerequisites are met before proceeding. | |
Oracle Home Configuration | Specify the Oracle client home path. | |
Select the Informatica Home Location | Specify the Informatica home location.
The Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/. |
|
Select Database Server for Informatica Repository Schemas | Select one of the following options for the Informatica repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) | Enter the following mounted directory configuration details in which the remote server directory is mounted:
To obtain the available storage drives, on the Linux machine, execute the <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% /installation server Note:
|
|
Specify Healthcare Data Model Database Instance Details | Enter values for the following fields:
|
|
Specify Informatica Repository Database Instance Details (applicable only if you selected No in the previous screen for Select this database instance for repository schema creation) | Enter values for the following fields:
|
|
Select Terminology Loaders Source Location | Specify the Terminology loaders source file location.
This location is used to read the terminology loaders source data files. You can change this location when required. The installer creates an archive directory at the same level as the source directory. Make sure that the create directory privileges exist for the installation user. |
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Warehouse Integration Loader Details | Enter values for the following fields:
Provide the pre-created hmc schema details. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>). If you enter an existing repository schema name, the installer overwrites the content with the new one, and you will lose the existing objects. |
|
Specify Healthcare Common Data Mart Loader Details | Enter values for the following fields:
Provide the pre-created hmc schema details. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>). If you create an existing repository schema name, the installer overwrites the content with the new one, and you will lose the existing objects. |
|
Specify Healthcare Cohort Data Mart Loader Details | Enter values for the following fields:
The configuration schema is not required for CDM. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>). If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose the existing objects. |
|
Specify Informatica Domain Details | Specify the following parameters:
Contact your Informatica Administrator for the Domain Code Page ID and provide a valid Code Page ID. Make sure that the code page is compatible with the domain code page for creating the Integration Service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows:
|
|
Verify Configuration Parameters | Click Next. | |
Summary | Click Install. | |
End of Installation | Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
After the Data Management Assembly for Informatica installation, run the following scripts from System user:
@<OHF_Install_Home>/dma_infa_master_install/hmc_infa_install/dma_directory_drop.sql
@<OHF_Install_Home>/dma_infa_master_install/hmc_infa_install/dma_revoke_privilege.sql <WIL_INFA_REP_DB_USER> <HCD_INFA_REP_DB_USER> <CDM_INFA_REP_DB_USER>
where,
<OHF_Install_Home>
- OHF installation home directory
<WIL_INFA_REP_DB_USER>
- Warehouse integration loader repository schema name
<HCD_INFA_REP_DB_USER>
- Healthcare common data mart loader repository schema name
<CDM_INFA_REP_DB_USER>
- Cohort data mart loader repository schema name
You must assign the integration service manually after the installation is complete. You can assign the integration service for all the workflows from the Workflow Manager:
Open the Workflow Manager. | |
Connect to the repository. | |
Click on any folder in the repository. | |
Under Menu, click on Service and select Assign Integration Service. | |
In the dialog box that opens, choose Integration Service from the drop-down list. | |
Select all the folders and check Select all displayed workflows. | |
Click Assign. |