User Guide

You should include the following slave definition immediately after the <native
name=”Native Directory”>
declaration:
<slaves>
<slave>
<url>ldap://
<slave_host_name>
:58089</url>
<type>failover</type>
</slave>
</slaves>
Where
<slave_host_name>
is the name of the slave server machine and 58089 is the Native
Directory port.
8 On the master server and then on the slave server, start the Hyperion S9 OpenLDAP service or process.
9 On the master server, start the slurpd replication service or process by performing an action:
On Windows, execute the following command from a command prompt window.
<
openLDAP_Home
>\slurpd -f
<master_slapd_config_file>
Example: C:\Hyperion\SharedServices\9.3.1\OpenLdap\slurpd -f
slapd.conf
On UNIX, execute the following command after navigating to <
openLDAP_Home
>/usr/
local/libexec
:
./slurpd -f <
openLDAP_Home
>/usr/local/etc/openldap/slapd.conf -t
<openLDAP_Home>
/usr/local/var/openldap-slurp —d 1
Example: ./slurpd -f /var/Hyperion/SharedServices/9.3.1/openLDAP/ usr/
local/etc/openldap/slapd.conf -t /app/Hyperion/SharedServices/9.3.1/
openLDAP/usr/local/var/openldap-slurp —d 1
Note:
slurpd
must always be running to synchronize data between the master and slave servers.
Cold Standby Deployment
In cold 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 inactive Native Directory (5) instance. The instances in
primary and standby environments connect to a Native Directory database (6) hosted on the
same physical hard drive that is dual attached to the primary and standby environments.
This deployment uses a hardware load balancer (4) to perform these tasks:
Detect the failure of the Native Directory instance in the primary environment
Start the Native Directory service (Windows) or process (UNIX) in the standby environment
Route all requests to the standby Native Directory instance
96
Managing Native Directory