User Guide

The load balancer must host a monitoring application capable of checking if Native Directory
is running in the primary environment. This can be achieved by using the LDAP ping mechanism
or by using corporate process monitoring tools (for example, Tivoli and UniCenter).
a. Configure the monitoring application to perform these tasks:
● Use the following directive (embedded in a batch or shell file) to look for an active
Native Directory instance in the primary environment.
ldapsearch –H ldapurl cn=*. For example, ldapsearch –H ldap://
myserver:58089/dc=css,dc=example,dc=com cn=*
● Using the following command, start Native Directory in the standby environment if
Native Directory is not active in the primary environment. You must create custom
scripts to start Native Directory.
net start “Hyperion S9 OpenLDAP” (Windows).
b. Configure the load balancer to reroute all requests to the standby environment upon
detecting a failure in the primary environment. You can use DNS name or IP address
redirection for this purpose. See documentation from the load balancer vendor for
information on how to complete this step.
8 Start Hyperion S9 OpenLDAP service or process on primary and standby environments.
9 Test your deployment.
A simple test would be to stop the Hyperion S9 OpenLDAP service or process in the primary
environment. The monitoring application on the load balancer should restart the process or
service in the standby environment.
Hot Standby Deployment
In hot standby deployment (see following illustration), the primary environment consists of
Shared Services (1) including Native Directory (2), and one or more Hyperion products (3).
The standby environment consists of an active Native Directory (5) instance. Each Native
Directory instance connects to its own database (6). A sync agent (7) backs up Native Directory
in the primary environment and updates it in the standby environment to synchronize the
databases at scheduled intervals.
The sync agent is not a part of Hyperion software distribution. The sync agent is similar to a
corporate scheduling agent or workflow tool that enables executing and monitoring jobs.
Customers must use their own sync agent to initiate backup and restore processes.
Hot Standby Deployment uses a hardware load balancer (4) to perform these tasks:
● Detect the failure of the Native Directory instance in the primary environment
● Route all requests to the standby Native Directory instance upon detecting a failed instance
in the primary environment.
98
Managing Native Directory