Setting Up a Two-Node High Availability

Cluster for Data Integration Hub

1993-2015 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by

any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. All
other company and product names may be trade names or trademarks of their respective owners and/or copyrighted
materials of such owners.

Abstract
This article describes how to set up a Data Integration Hub high availability cluster that consists of two Data Integration
Hub nodes in the following environment:

The Data Integration Hub nodes are running a Linux operating system.

The Data Integration Hub repository, the Data Integration Hub publication repository, and the operational data
store are on an Oracle database.

The repositories and the document store are on a Storage Area Network (SAN) storage system.

Supported Versions

Data Integration Hub 9.6.1 - 9.6.1 HotFix 1

Table of Contents
Setting Up a Two-Node High Availability Cluster for Data Integration Hub Overview. . . . . . . . . . . . . . . . . . 2
Two-Node High Availability Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
PowerCenter Environment for a Data Integration Hub Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Setting Up a High Availability Storage Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Setting Up a Clustered File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Configuring Cluster Management Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Step 1: Install the Document Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Step 2: Install Data Integration Hub on the First Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Step 3: Install Data Integration Hub on the Second Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Step 4: Configure Data Integration Hub Properties for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . 16
Step 5: Configure HTTP Load Balancer Sticky Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Step 6: Configure PowerCenter Settings for Data Integration Hub High Availability. . . . . . . . . . . . . . . . . . 16
Step 7: Configure the Dashboard and Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 8: Restart the Data Integration Hub Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Setting Up a Two-Node High Availability Cluster for Data

Integration Hub Overview
When you use Data Integration Hub to process publications and subscriptions on a large scale, you need to provide
continuous service even if one component fails. You set up a high availability environment with failover mechanisms
that can handle a failed server or service.
This article is intended for Data Integration Hub administrators. It assumes you have working knowledge of all Data
Integration Hub components, PowerCenter Integration Service, and network administration.

Two-Node High Availability Cluster

A two-node cluster consists of two nodes that contain identical installations of Data Integration Hub. Each node in the
cluster can take over in case the other computer fails.

PowerCenter Environment for a Data Integration Hub Cluster

Before you set up the Data Integration Hub high availability cluster, your PowerCenter environment must be ready.
Verify that the machine where the PowerCenter services are installed is accessible to Data Integration Hub.
Setting up a two-node Data Integration Hub cluster does not require you to install Data Integration Hub on each of the
PowerCenter nodes. You can install Data Integration Hub on nodes where the PowerCenter services are installed, or
on different nodes.
For more information, see the Data Integration Hub Installation and Configuration Guide.
Note: The PowerCenter services must be running when you install Data Integration Hub on the cluster nodes.

Prerequisites
Before you set up the high availability environment, verify that your system meets the following prerequisites:

It is recommended that the Data Integration Hub repository is on a high availability database, such as Oracle
Real Application Clusters.

The high availability environment includes a clustered file system, such as Global File System (GFS) or Veritas
Cluster File System (VxCFS ).

The cluster consists of two active Data Integration Hub server nodes.

The PowerCenter real-time workflows are active and running.

A load balancer is installed, such as the F5 Load Traffic Manager or the Apache HTTP Server.

The clocks on all Data Integration Hub nodes are synchronized to within 30 seconds of each other. Use the
Network Time Protocol (NTP) to synchronize the clocks.

Both cluster nodes are installed in the same physical location. Geographically distributed nodes are not
supported.

Setting Up a High Availability Storage Solution

When you set up the high availability environment, you determine which storage solution to use for the Data Integration
Hub repository database and the document store.
To increase reliability, a high availability storage system typically consists of a group of reliable and fast hard drives on
which you install the database or file system. In the environment that is described in this article, a Storage Area
Network (SAN) storage system is used.
In the storage system, you can mount any high-performance hard drives, such as RAID, SSD, or SCSI. To optimize
performance, use RAID 1+0 hard drives.

Setting Up a Clustered File System

Install and configure a clustered file system on which to store shared components, such as the document store.
A clustered file system is a distributable file system that utilizes the high availability physical storage configuration. The
clustered file system you install depends on the type of high availability storage solution.
When you use an SAN storage solution, you need to install the clustered file system separately. For example, you can
use the Veritas Cluster File System (VxCFS) file system or the Global File System (GFS). The recommended file
system is VxCFS.
Configure the clustered file system to use hardware-based I/O fencing for all of the nodes in the cluster.

Configuring Cluster Management Software

Use cluster management software to monitor the status of the services that run on each node in the cluster and
troubleshoot service failure.
You configure the software to start or stop services on each node in the cluster in case one or more services fail. For
example, if you use an active/passive cluster, you can configure the cluster manager to stop all of the services in the
active node and start all of the services in the passive node in case one of the services in the active node fails.
A cluster manager typically consists of the following components:

Main application that manages the entire cluster and sends commands to start, stop, or verify the availability of
the services. You can install the application anywhere in the cluster. To improve reliability, install the
application outside of the cluster.

Agent that monitors and reports the status of the services in each node to the main application. The agent can
start or stop the services with commands from the main application. You install the agent on each node in the
cluster and define which services to monitor.

Step 1: Install the Document Store

Install the document store on a shared network drive so that it is accessible by all the Data Integration Hub Server
instances.
The Informatica domain nodes that run workflows need use the same file references to access the shared file system.
All Data Integration Hub and Informatica domain nodes require access to the same file server and all nodes must use
the same path to the file server. For example, the path //shared/storage_1/DataIntegrationHub/document_store/
file_one.txt must point to the same file from all nodes.

Step 2: Install Data Integration Hub on the First Node

Install Data Integration Hub on the first node.
Note: The installation of Data Integration Hub on the first node is not identical to the installation on the second node.
Do not perform this procedure on the second node.
1.

Log in to the machine with the user account that you want to use to install Data Integration Hub.
To prevent permission errors, use the same account to install Data Integration Hub and PowerCenter.

2.

Close all other applications.

3.

Run the Install.bin -i console command.

The Introduction section appears.

4.

Read the instructions, and then press Enter.

The Install or Upgrade section appears.

5.

Select to install Data Integration Hub, and then press Enter.

The PowerCenter Version section appears.

6.

Select the PowerCenter version for which you want to install Data Integration Hub, and then press Enter.
The Installation Directory section appears.

7.

Enter the absolute path to the installation directory or accept the default directory, and then press Enter.
The Installation Components section appears and displays a numbered list of the components to install.

8.

Enter a comma-separated list of numbers for the components to install or accept the default components:

1- Data Integration Hub

Installs the core Data Integration Hub application.
Selected by default.
2- Data Integration Hub Dashboard and Reports
Installs the Data Integration Hub Dashboard and Reports component. You must install Data Integration
Hub to install the Dashboard and Reports component.
Cleared by default.
Note: If you install the Dashboard and Reports component, import the operational data store event
loader after you install Data Integration Hub.
3- Data Integration Hub Server Plug-in for PowerCenter
Installs the Data Integration Hub PowerCenter server plug-in component. After the installation, register
the plug-in to the PowerCenter repository.
Selected by default.
4- Data Integration Hub Client Plug-in for PowerCenter
Installs the Data Integration Hub PowerCenter Client plug-in. Install this component on every machine
that runs PowerCenter Client.
Selected by default.
9.

Press Enter.
The Metadata Repository section appears.

10.

Select 1- Create a Data Integration Hub repository and press Enter.

The Metadata Repository Connection section appears.

11.

Enter 1 to select Oracle as the Data Integration Hub metadata repository database type.

12.

Enter the number for the metadata repository database connection type:
1- Database URL
Location of the database. If you select this option, enter values in the following fields:

Database host name. Host name of the machine where the database server is installed.

Database port number. Port number for the database. Default port number is 1521.

Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully
qualified SID.
Note: It is recommended that you enter a ServiceName in this field.

2- Custom Connection String

Connection string to the database. If you select this option, enter values in one of the following fields:

JDBC string. JDBC connection string to the database.

ODBC string. ODBC connection string to the database. Available if you install the PowerCenter client
plug-in. The installer cannot verify the validity of the ODBC string.

3- Database username
Name of the database user account for the Oracle database.
4- Database user password
The password for the database account for the Oracle database. Data Integration Hub stores the
password as an encrypted string.
13.

Press Enter.
The Publication Repository Connection section appears.

14.

Enter values in the following fields:

1- Database URL
Location of the database. Enter values in the following fields:

Database host name. Host name of the machine where the database server is installed.

Database port number. Port number for the database. The default port number is 1521.

Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully
qualified SID.
Note: It is recommended that you enter a ServiceName in this field.

2- Custom Connection String

JDBC Connection String to the database.
3- Database username
Name of the database user account for the Oracle database.
4- Database user password
The password for the database account for the Oracle database. Data Integration Hub stores the
password as an encrypted string.
Note: The type of database to use for the publication repository appears in read-only mode.
15.

Press Enter.
If you selected to install the Data Integration Hub Dashboard and Reports component, the Operational Data
Store section appears. If you did not select to install the Dashboard and Reports component, go to step 19 to
configure user authentication.

16.

In the Operational Data Store section, enter 1- Create an operational data store repository.

17.

Enter values in the following fields:

1- Database URL
Location of the database. If you select this option, enter values in the following fields:

Database host name. Host name of the machine where the database server is installed.

Database port number. Port number for the database. The default port number is 1521.

Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully
qualified SID.
Note: It is recommended that you enter a ServiceName in this field.

2- Custom Connection String

JDBC connection string to the operational data store.
3- Database username
Name of the database user account for the Oracle database.
4- Database user password
The password for the database account for the Oracle database. Data Integration Hub stores the
password as an encrypted string.
18.

Press Enter.
The User Authentication section appears.

19.

Choose the type of user authentication that you want to use.

Choose Informatica domain authentication to manage user credentials in the Informatica domain and
synchronize user information with Data Integration Hub. If your Informatica domain uses Kerberos
authentication, choose the option Informatica domain with Kerberos authentication. Use Informatica
domain authentication for production environments.
If you choose Informatica domain authentication, enter values in the following fields:
Gateway host
Host name of the Informatica security domain server. Data Integration Hub stores the host name in
the pwc.domain.gateway system property.
Gateway port
Port number for the Informatica security domain gateway. Data Integration Hub stores the port
number in the pwc.domain.gateway system property. Use the gateway HTTP port number to connect
to the domain from the PowerCenter Client. You cannot use the HTTPS port number to connect to the
domain.
Password
Password of the Informatica security domain user.
Username
User name to access the Administrator tool. You must create the user in the Administrator tool and
assign the manage roles/groups/user privilege to the user.
Security domain
Name of the Informatica security domain where the user is defined.
Security group
Optional. Security group within the Informatica security domain where Data Integration Hub users are
defined in the following format:
<security group>@<domain>
If you leave the field empty, the Informatica security domain synchronizes only the Data Integration
Hub administrator user account.
Data Integration Hub stores the security group in the dx.authentication.groups system property in the
following format:
<group name>@<security group>[;<groupname>@<security group>]

Choose Informatica domain with Kerberos authentication if your Informatica domain uses Kerberos
authentication.
If you choose Informatica domain with Kerberos authentication, enter values in the following fields:
Kerberos configuration file
File that stores Keberos configuration information, usually named krb5.conf
The installation copies the file to the following location:
<DIHInstallationDir>/shared/conf/security/krb5.conf
Operation Console SPN name
Service Principal Name (SPN) for the Data Integration Hub Operation Console.
Data Integration Hub stores the SPN in the dx-security-config.properties property file, in the
dx.kerberos.console.service.principal.name property.
Operation Console keytab file
Location of the keytab file for the Data Integration Hub Operation Console SPN.

The installation copies the file to the following location:

<DIHInstallationDir>/shared/conf/security/HTTP_console.keytab
Data Integration Hub stores the location of the keytab file in the dx-security-config.properties
property file, in the dx.kerberos.console.keytab.file property.
If you change the property to point to a different file, you must enter the absolute path to the file using
the following format:
file://<full_path>
System Administrator
Data Integration Hub system administrator credentials.
Enter the credentials in the following format:
<username>@<SECURITY_DOMAIN>
Note: You must enter <SECURITY_DOMAIN> in uppercase letters.
Gateway host
PowerCenter domain gateway host.
Gateway port number
PowerCenter domain gateway port number.
Security group
Optional. Security group within the Informatica security domain where Data Integration Hub users are
defined in the following format:
<security group>@<domain>
If you leave the field empty, the Informatica security domain synchronizes only the Data Integration
Hub administrator user account.
Data Integration Hub stores the security group in the dx.authentication.groups system property in the
following format:
<group name>@<security group>[;<groupname>@<security group>]

20.

If you choose Data Integration Hub native authentication, enter the Data Integration Hub administrator
user name. Data Integration Hub uses this value for the user name and password when you log in to the
Operation Console.

Press Enter.
The Document Store section appears.

21.

Enter the directory where Data Integration Hub stores documents and files during processing or accept the
default directory, and then press Enter.
The document store directory must be accessible to Data Integration Hub, PowerCenter services, and Data
Transformation.

22.

Press Enter.
The Web Server section appears.

23.

Configure the Web Server connection.

a.

Enter the number for the network communication protocol or accept the default protocol:
1- Enable HTTPS
Instructs Data Integration Hub to use secure network communication when you open the Operation
Console in the browser.
If you select HTTPS and HTTP, the Operation Console switches existing HTTP connections with
HTTPS connections.
2- Enable HTTP
Instructs Data Integration Hub to use regular HTTP network communication when you open the
Operation Console in the browser.

b.

If you selected Enable HTTPS, enter values in the following fields:

Connector port number
Port number for the Tomcat connector to use when you open the Operation Console with HTTPS.
The default value is 18443.
Use a keystore file generated by the installer
Instructs the installer to generate a keystore file with an unregistered certificate. If you select this
option, ignore the security warning that you receive from the browser the first time you open the
Operation Console.
Use an existing keystore file
Instructs the installer to load an existing keystore file. Enter values in the following fields:

Keystore password. Password for the keystore file.

Keystore file. Path to the keystore file.

The keystore file must be in the Public Key Cryptography Standard (PKCS) #12 format.
c.

If you selected Enable HTTP, enter values in the following fields:

HTTP connector port number
Port number for the HTTP connector. If you clear this field, your browser must connect to the Data
Integration Hub server with HTTPS when you log in to the Operation Console.
The default value is 18080.
Server shutdown listener port number
Port number for the listener that controls the Tomcat server shutdown.
The default value is 18005.

24.

Press Enter.
If you selected to install the Data Integration Hub PowerCenter server plug-in or the Data Integration Hub
PowerCenter Client plug-in components, the PowerCenter Location section appears. If you did not select to
install the PowerCenter server or client components, the PowerCenter Web Services Hub section appears.
Go to step 27 to configure PowerCenter settings.

25.

Enter the directory where you installed PowerCenter or accept the default directory, and then press Enter.

26.

Enter 1 to connect to the PowerCenter Web Services Hub, and then press Enter.

27.

Enter the URL that the PowerCenter Web Services Hub uses to process publication and subscription
workflows or accept the default directory, and then press Enter.
The PowerCenter Repository Service section appears.

28.

Enter the name of the PowerCenter repository service, and then press Enter.

29.

Enter values in the following fields:

Node host name
Host name of the node that runs the PowerCenter Repository Service.
Node port number
Port number of the node that runs the PowerCenter Repository Service.
Username
Name of the PowerCenter Repository Service user.
Password
Password for the PowerCenter Repository Service user. Data Integration Hub stores the password as an
encrypted string.
Security domain
Optional. Name of the Informatica security domain in which the PowerCenter Repository Service user is
stored.
Default is Native.

30.

Press Enter.
If you selected to install the Data Integration Hub server plug-in for PowerCenter component, the Informatica
Domain section appears. If you did not select to install the PowerCenter server component, go to step 33.

31.

Enter values in the following fields:

Domain name
Name of the Informatica domain that contains the PowerCenter Integration Service that runs Data
Integration Hub workflows.
Node name
Node in the Informatica domain on which the PowerCenter Integration Service runs.
Domain administrator user name
Name of the Informatica domain administrator.
Domain administrator password
Password for the Informatica domain administrator. Data Integration Hub stores the password as an
encrypted string.

32.

Press Enter.
The PowerCenter pmrep Command Line Utility Location section appears.

33.

Enter the location of the pmrep command line utility, and then press Enter.
The location of the utility depends on the machine where the PowerCenter services are installed.
Environment

Location of the pmrep command line utility

Data Integration Hub installed on the

machine where the PowerCenter
services are installed

<PowerCenter_services_installation_folder>
\<PowerCenter_version>\tools\pcutils
\<PowerCenter_version>
Note: pmrep must be executable.

10

Environment

Location of the pmrep command line utility

Data Integration Hub and PowerCenter

services installed on different machines

<PowerCenter_client_utility_directory>/
PowerCenter/server/bin
Note: pmrep must be executable.

34.

Press Enter.
The PowerCenter Repository Access section appears.

35.

Enter values in the following fields:

Use direct access to the PowerCenter repository
Read PowerCenter metadata information directly from the PowerCenter repository database instead of
using the PowerCenter Repository Service API. When this option is selected, you need to provide the
PowerCenter repository details in the PowerCenter Repository Access section.
Note: Direct access to the PowerCenter repository improves the system performance. It is therefore
recommended that you use this option. If you disable this option, Data Integration Hub reads the
information from the PowerCenter Repository Service API, which causes some latency in operations
against the PowerCenter repository.
Database type
Choose Oracle.
Database URL
Location of the PowerCenter repository. If you select this option, enter values in the following fields:

Database host name. Host name of the machine where the PowerCenter repository is installed.

Database port. Port number for the PowerCenter repository. The default port number is 1521.

Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully
qualified SID.
Note: It is recommended that you enter a ServiceName in this field.

Custom Connection String

JDBC connection string to the PowerCenter repository.
Database username
Name of the database user account.
Database user password
Password for the database account. Data Integration Hub stores the password as an encrypted string.
36.

Press Enter.

37.

Verify that the installation information is correct, and then press Enter.
During the installation process, the installer displays progress information.

38.

If you installed the Data Integration Hub PowerCenter server plug-in, follow the on-screen instructions to
register the plug-in to the PowerCenter repository, and then press Enter.

39.

To view the log files that the installer generates, navigate to the following directory: <DIHInstallationDir>
\logs

40.

Perform the required post-installation tasks. For more information, see the section "Post-Installation Tasks" in
the Data Integration Hub Installation and Configuration Guide.
Note: Perform only the tasks that are relevant for your environment.

11

41.

Optionally, perform additional configuration tasks. For more information, see the section "Optional Data
Integration Hub Configuration" in the Data Integration Hub Installation and Configuration Guide.

Step 3: Install Data Integration Hub on the Second Node

Install Data Integration Hub on the second node.
Note: The installation of Data Integration Hub on the second node is not identical to the installation on the first node.
Do not perform this procedure on the first node.
1.

Log in to the machine with the user account that you want to use to install Data Integration Hub.
To prevent permission errors, use the same account to install Data Integration Hub and PowerCenter.

2.

Close all other applications.

3.

Run the Install.bin -i console command.

The Introduction section appears.

4.

Read the instructions, and then press Enter.

The Install or Upgrade section appears.

5.

Select to install Data Integration Hub, and then press Enter.

The PowerCenter Version section appears.

6.

Select the PowerCenter version for which you want to install Data Integration Hub, and then press Enter.
The Installation Directory section appears.

7.

Enter the absolute path to the installation directory or accept the default directory, and then press Enter.
The Installation Components section appears and displays a numbered list of the components to install.

8.

Enter a comma-separated list of numbers for the components to install or accept the default components:
1- Data Integration Hub
Installs the core Data Integration Hub application.
Selected by default.
2- Data Integration Hub Dashboard and Reports
Installs the Data Integration Hub Dashboard and Reports component. You must install Data Integration
Hub to install the Dashboard and Reports component.
Cleared by default.
Note: If you install the Dashboard and Reports component, import the operational data store event
loader after you install Data Integration Hub.
3- Data Integration Hub Server Plug-in for PowerCenter
Installs the Data Integration Hub PowerCenter server plug-in component. After the installation, register
the plug-in to the PowerCenter repository.
Selected by default.
4- Data Integration Hub Client Plug-in for PowerCenter
Installs the Data Integration Hub PowerCenter Client plug-in. Install this component on every machine
that runs PowerCenter Client.
Selected by default.

9.

Press Enter.
The Metadata Repository section appears.

10.

12

Select Use an existing Data Integration Hub repository, and then click Next.

The Metadata Repository Connection section appears.

11.

Enter the same values that you entered in the fields when you installed Data Integration Hub on the first
node.

12.

Press Enter.
The Publication Repository Connection section appears.

13.

Enter the same values that you entered in the fields when you installed Data Integration Hub on the first
node.

14.

Press Enter.
If you selected to install the Data Integration Hub Dashboard and Reports component, the Operational Data
Store section appears. If you did not select to install the Dashboard and Reports component, go to step 18 to
configure the Web Server connection.

15.

In the Operational Data Store section, enter 1- Use an existing operational data store repository.
The Operational Data Store Database Connection section appears.

16.

Enter the same values that you entered in the fields when you installed Data Integration Hub on the first
node.

17.

Press Enter.
The Web Server section appears.

18.

Configure the Web Server connection.

a.

Enter the number for the network communication protocol or accept the default protocol:
1- Enable HTTPS
Instructs Data Integration Hub to use secure network communication when you open the Operation
Console in the browser.
If you select HTTPS and HTTP, the Operation Console switches existing HTTP connections with
HTTPS connections.
2- Enable HTTP
Instructs Data Integration Hub to use regular HTTP network communication when you open the
Operation Console in the browser.

b.

If you selected Enable HTTPS, enter values in the following fields:

Connector port number
Port number for the Tomcat connector to use when you open the Operation Console with HTTPS.
The default value is 18443.
Use a keystore file generated by the installer
Instructs the installer to generate a keystore file with an unregistered certificate. If you select this
option, ignore the security warning that you receive from the browser the first time you open the
Operation Console.
Use an existing keystore file
Instructs the installer to load an existing keystore file. Enter values in the following fields:

Keystore password. Password for the keystore file.

Keystore file. Path to the keystore file.

The keystore file must be in the Public Key Cryptography Standard (PKCS) #12 format.

13

c.

If you selected Enable HTTP, enter values in the following fields:

HTTP connector port number
Port number for the HTTP connector. If you clear this field, your browser must connect to the Data
Integration Hub server with HTTPS when you log in to the Operation Console.
The default value is 18080.
Server shutdown listener port number
Port number for the listener that controls the Tomcat server shutdown.
The default value is 18005.

19.

Press Enter.
If you selected to install the Data Integration Hub server plug-in for PowerCenter or the Data Integration Hub
client plug-in for PowerCenter components, the PowerCenter Location section appears. If you did not select
the PowerCenter server or client components, go to step 27.

20.

Enter the directory where you installed PowerCenter or accept the default directory, and then press Enter.

21.

Enter 2 to skip the Web Services Hub URL option, and then press Enter.
If you selected to install the Data Integration Hub server plug-in for PowerCenter component, the Informatica
Domain section appears. If you did not select to install the PowerCenter server component, go to step 27.

22.

Enter values in the following fields:

Domain name
Name of the Informatica domain that contains the PowerCenter Integration Service that runs Data
Integration Hub workflows.
Node name
Node in the Informatica domain on which the PowerCenter Integration Service runs.
Domain administrator user name
Name of the Informatica domain administrator.
Domain administrator password
Password for the Informatica domain administrator. Data Integration Hub stores the password as an
encrypted string.

23.

Enter the location of the pmrep command line utility and then press Enter.
The location of the utility depends on the machine where the PowerCenter services are installed.
Environment

Location of the pmrep command line utility

Data Integration Hub installed on the

machine where the PowerCenter
services are installed

<PowerCenter_services_installation_folder>
\<PowerCenter_version>\tools\pcutils
\<PowerCenter_version>
Note: pmrep must be executable.

Data Integration Hub and PowerCenter

services installed on different machines

<PowerCenter_client_utility_directory>/
PowerCenter/server/bin
Note: pmrep must be executable.

24.

Press Enter.
The PowerCenter Repository Access section appears.

14

25.

Enter values in the following fields:

Use direct access to the PowerCenter repository
Read PowerCenter metadata information directly from the PowerCenter repository database instead of
using the PowerCenter Repository Service API. When this option is selected, you need to provide the
PowerCenter repository details in the PowerCenter Repository Access section.
Note: Direct access to the PowerCenter repository improves the system performance. It is therefore
recommended that you use this option. If you disable this option, Data Integration Hub reads the
information from the PowerCenter Repository Service API, which causes some latency in operations
against the PowerCenter repository.
Database type
Choose Oracle.
Database URL
Location of the PowerCenter repository. If you select this option, enter values in the following fields:

Database host name. Host name of the machine where the PowerCenter repository is installed.

Database port. Port number for the PowerCenter repository. The default port number is 1521.

Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully
qualified SID.
Note: It is recommended that you enter a ServiceName in this field.

Custom Connection String

JDBC connection string to the PowerCenter repository.
Database username
Name of the database user account.
Database user password
Password for the database account. Data Integration Hub stores the password as an encrypted string.
26.

Press Enter.

27.

Verify that the installation information is correct, and then press Enter.
During the installation process, the installer displays progress information.

28.

If you installed the Data Integration Hub PowerCenter server plug-in, follow the on-screen instructions to
register the plug-in to the PowerCenter repository, and then press Enter.

29.

To view the log files that the installer generates, navigate to the following directory: <DIHInstallationDir>
\logs

30.

Perform the required post-installation tasks. For more information, see the section "Post-Installation Tasks" in
the Data Integration Hub Installation and Configuration Guide.
Note: Perform only the tasks that are relevant for your environment.

31.

15

Optionally, perform additional configuration tasks. For more information, see the section "Optional Data
Integration Hub Configuration" in the Data Integration Hub Installation and Configuration Guide.

Step 4: Configure Data Integration Hub Properties for High

Availability
Configure Data Integration Hub properties on both of the cluster nodes.
1.

On both of the cluster nodes, open the Data Integration Hub properties configuration file from the following
location:
<DIHInstallationDir>/conf/dx-configuration.properties

2.

Add a comment indicator to the dx.jms.multicastAddress property.

3.

Remove the comment indicator from the dx.AMQ.discovery property.

4.

Remove the comment indicator from the dx.AMQ.static.discovery.address property and replace the
syntax example with real values. Each node in the cluster requires two entries.
For example:
dx.AMQ.static.discovery.address=static:(tcp://node1:18100,tcp://node1:18050,tcp://
node2:18100,tcp://node2:18050)?jms.prefetchPolicy.queuePrefetch=1

5.

Save the file on both cluster nodes.

6.

On both of the cluster nodes, perform steps 2 to 5 in the the following file:
<DIHInstallationDir>/ DataIntegrationHub/apache-tomcat-version/shared/classes/dxconfiguration.properties

7.

In the Data Integration Hub Operation Console, from the Navigator, open Administration > System
Properties.

8.

Change the value of the dx.console.url property to the load balancer URL, in the following format: http://
<load_balancer>:<load_balancer_port>/dih-console .
For example: http://host1:80/dih-console

Step 5: Configure HTTP Load Balancer Sticky Sessions

Configure HTTP load balancer sticky sessions on both of the cluster nodes.
1.

On both of the cluster nodes, create a backup of the following file:

<DIHInstallationDir>/ DataIntegrationHub/apache-tomcat-version/conf/server.xml
Name the backup file server.xml.bak

2.

On both of the cluster nodes, in the file server.xml, change the value of the attribute jvmRoute in the
element Engine to the physical computer name, for example, Tomcat-A. The value of the jvmRoute attribute
must be unique for each Tomcat instance.

3.

Remove the comment indicator from the line <connection port="18009" enableLookup="false"
redirectPort="18443" protocol="AJP/1.3"/>.

4.

Save the file on both cluster nodes.

Step 6: Configure PowerCenter Settings for Data Integration

Hub High Availability
Configure PowerCenter settings for Data Integration Hub high availability. You configure the settings once for the entire
cluster.
1.

16

Open the Informatica Administrator tool, and then open the Processes tab of the PowerCenter Integration
Service.

2.

In the environment variable list, in the DX_SERVER_URL variable, enter an address and port number for each of
the Data Integration Hub cluster nodes in the following format:
rmi://<node1_address>:<port>[;rmi://<node2_address>:<port>]
For example: rmi://node1:18095;rmi://node2:18095
Verify that the port number matches the value in the dx.rmi.port configuration property.

3.

Configure any other node-dependent PowerCenter Integration Service properties, such as the Java system
properties, to use the IP addresses and port numbers of the Data Integration Hub cluster nodes.

Step 7: Configure the Dashboard and Reports

If you installed the Dashboard and Reports component, perform this task on both of the cluster nodes.
1.

In the Data Integration Hub Operation Console, from the Navigator, open Administration > System
Properties.

2.

In the dx.dashboard.url system property, enter the load balancer URL in the following format: http://
<load_balancer>:<load_balancer_port>/dih-dashboard
For example:
http://host1:80/dih-dashboard

3.

Open the following file:

<DIHInstallationDir>/ DataIntegrationHub/apache-tomcat-version/shared/classes/
dx_dashboard_configuration.xml

4.

In the dx_dashboard_configuration.xml file, configure the following properties:

Property

Description

DX_CONSOLE_URL

Load balancer URL in the following format: http://

<load_balancer>:<load_balancer_port>/dih-console
For example: http://host1:80/dih-console

DASHBOARD_SAVEFOLDER

Shared folder for the saved Dashboard applications. You must create the folder before
you configure this property.
For example: //NetworkDir/SavedDashboards

AuthenticationClientAddresses

Load balancer IP addresses separated by commas. Enter IPv4 and IPv6 addresses.
For example:
10.40.0.135,192.178.147.1,192.268.30.1,127.4.0.1,193.168.147.1

LogonFailPage

Load balancer URL in the following format: http://<load

balancer>:<dih_port>/dih-console/logout.jsp
For example: http://host1:80/dih-console/logout.jsp

5.

In the _Settings.lgx file, add a SecureKeySharedFolder property to the Security element and set the value
of SecureKeySharedFolder to the path of a shared location on the network to store the SecureKey file.
For example: SecureKeySharedFolder="//NetworkDir/SecureKeys"
Note: You must create the folder before you add this property.

6.

Configure the operational data store (ODS) workflow file with the standard PowerCenter high availability
configuration. The workflow file resides in the following location:
<DIHInstallationDir>/powercenter/ETL/DX_ETL.xml

7.

17

Restart the Tomcat server.

8.

If you customized the Dashboard, deploy the customization on all of the machines in the cluster.

Step 8: Restart the Data Integration Hub Services

Restart the Data Integration Hub services on both cluster nodes.
For more information, see the section "Starting and Stopping Data Integration Hub" in the Data Integration Hub
Installation and Configuration Guide.

Authors
Lior Mechlovich
Manager, Development
Rachel Aldam
Senior Technical Writer

18