Add a secondary server
You can add secondary LDAP servers to your configuration for fail-over purposes. The implementation checks each call to the LDAP server (that fails) and looks for some specific exceptions/errors. When one of the known errors is seen, it is interpreted as a failed server and the session provider switches to the next server in the list. The switch is done in a round-robin fashion, and the state is not saved between restarts of the session provider. Therefore, you must make sure to keep the primary server first in the list.
Note that if a fail-over occurs during an attempted logon, that logon will fail. The new server will be used by the next logon attempt. When a switch happens, an INFO message similar to the following is logged in the SessionProvider log:
2013-03-04 08:12:38,525 INFO SessionProvider SessionProvider: Switching server from
sestw426.corpnet.infor.com to ldapemea.corpnet.infor.com
The configured servers, as well as the currently active server, can be seen by selecting the session provider in the LifeCycle Manager, and selecting Manage Application. If fail-over is configured, a list of the servers is shown, with an asterisk ("*") next to the currently active server
- Locate the LDAPSessionProvider application for the grid in the left pane in LifeCycle Manager.
- Right-click the LDAPSessionProvider application and select Configure Session Provider.
- On the Connection tab, click the Add... button by the Secondary server list field.
- Enter the address to the secondary server you want to add and click OK. After you click OK, a check is made to see if it is possible to connect to the server.
- Click Add... again if you want to add more secondary servers.
- When you are finished adding secondary servers, click Save.
- Switch to the Authentication & Search Base tab and click Validate. This will validate that the username and password are valid on all servers. You might also get additional certificate dialogs if you use any of the SSL-based encryption methods.