CA SiteMinder® Federation Standalone can distribute LDAP user directory requests over multiple LDAP servers for failover and load balancing.
For load balancing, the system evenly spreads requests over the specified LDAP servers. Coupled with failover, load balancing provides faster, more efficient access to LDAP user directory information.
For failover, the system uses one LDAP server to fulfill requests until that server fails to respond. When the default server does not respond, the system routes the request to the next server configured for failover. This process can be repeated over multiple servers. After the default server is able to fulfill requests again, requests go back to the original server.
Follow these steps:
The User Directory dialog opens.
The LDAP Server Load-balancing and Failover table displays.
Note: If you are adding a server for failover, the failover directory must use the same type of communication (SSL or non-SSL) as the primary directory. Both directories share the same port number.
If you only have one entry in the table, then only failover is supported.
You can add the same server multiple times for load balancing, which forces a single system to handle more requests. For example, consider two servers in a group: Server1 and Server2. Server1 is a high-performance server and Server2 is a lesser system. You can add Server1 to the load balancing list twice so that it processes two requests for each request processed by Server2.
Example: Load Balancing and Failover
In this example, a SiteMinder environment contains two user directories, A and B, which must meet the following requirements:
The configuration requires two load balancing groups.
The result is two load balancing groups with one server each for failover "A B" and "B A", which load balance each other. If both directories are available, load balancing occurs between the first directories in each group: A and B. If user directory A becomes unavailable, failover occurs to user directory B. This results in user directory B handling all the requests until user directory A becomes available.
|
Copyright © 2013 CA.
All rights reserved.
|
|