Access Manager Session Failover Scenario

The following figure shows an Access Manager session failover deployment scenario that includes these components:

• Three Access Manager instances, running on different host servers on supported web containers. All Access Manager instances access the same Directory Server (not shown in the figure).

• Message Queue brokers, running in cluster mode on different servers.

• Berkeley DB client (amsessiondb), running on the same servers as the Message Queue brokers.

• Load balancer to improve performance and security.

• Client requests can originate from a Web browser, C or Java application using the Access Manager SDK, or a J2EE/Web agent.

Figure 6–1 Access Manager Session Failover Scenario