User guide

High-Performance and High-Reliability System
1-43
Figure 1-31 Load Balancing among Authentication and Repository Servers
The figure above shows the load balancing among authentication and repository servers.
The authentication requests from clients are distributed to each authentication server by a load balancer,
e.g., Interstage Traffic Director, to each authentication server.
When one repository server (update system) and multiple repository servers (reference systems) are
allocated to each authentication server, the authentication server connects to a repository server
(reference system) for the processing of ordinary authentication request. It connects automatically to the
repository server (update system) only when the information in the SSO repository is required to
change(e.g., when the user is locked by the lockout function). When different repository servers
(reference systems) are allocated separately to the authentication servers, the load on repository
servers can be balanced.
When the information in the SSO repository of the repository server (update system) is updated, the
updated content can be reflected in the SSO repository of the repository servers (reference systems)
automatically by using the Smart Repository replication function.
When a different repository server (reference system) is assigned to each authentication server as the
one to be connected preferentially, the load on repository servers can be balanced.