User's Manual

Note:
Native Directory in the standby environment handles all calls until the primary environment is
brought back online and the load balancer is configured to route calls to the primary
environment.
➤ To deploy Native Directory for failover in hot standby mode:
1 Install Shared Services in the primary and standby environments.
Refer to the Hyperion Shared Services Installation Guide for instructions.
2 Configure and deploy Shared Services in the primary environment.
You need not configure or deploy Shared Services in the standby environment.
3 Verify that Hyperion S9 OpenLDAP service or process is running in the primary and secondary
environments.
4 Configure the process monitoring application with the following directive to check if Native Directory service
(Windows) or process (UNIX) is running in the primary environment:
ldapsearch –H ldapurl cn=*. For example, ldapsearch –H ldap://myserver:
58089/dc=css,dc=example,dc=com cn=*
5 Configure the load balancer to reroute all requests to the standby environment on 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.
6 Configure the sync agent (scheduler) to back up Native Directory data from the primary environment and to
update the standby environment.
7 Test the configuration.
Migrating Native Directory
The Native Directory database stores security-related data. You must migrate Native Directory
data as a part of migrating Shared Services. See Hyperion Shared Services Installation Guide for
Migrating Native Directory
99