Start the Directory Server instance (ds1.example.com) on the first machine only. Add the Access Manager indexes to the first Directory Server instance, as described in Indexing Access Manager Attributes in Directory Server.
Log in as or become superuser (root) on the server where Access Manager is installed.
Backup the serverconfig.xml file.
The serverconfig.xml file is in the following directory, depending on your platform:
Solaris systems: /etc/opt/SUNWam/config
Linux and HP-UX systems: /etc/opt/sun/identity/config
Windows systems: C:\Program Files\Sun\JavaES5\identity\config
In the serverconfig.xml file, add the secondary Directory Server instance. For example:
... <iPlanetDataAccessLayer> <ServerGroup name="default" minConnPool="1" maxConnPool="10"> <Server name="Server1" host=" ds1.example.com" port="389" type="SIMPLE" /> <Server name="Server2" host=" ds2.example.com" port="389" type="SIMPLE" /> ...
Login to the Access Manager Legacy Mode Console as amadmin.
Click Directory Management > Organizations organization-name.
Click Configuration > Authentication Service Name – LDAP.
After you have performed the changes on both Access Manager instances, restart the Access Manager web container on both host servers.
On the secondary Directory Server instance, add the Access Manager indexes as follows:
Start the secondary Directory Server instance.
Add the Access Manager indexes using either the Directory Server 6.0 Directory Service Control Center (DSCC) or the ldapmodify utility.
For information about adding indexes, see Indexing Access Manager Attributes in Directory Server.
Restart the secondary Directory Server instance.