Out of support


This documentation supports the 8.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.

Click here to view the documentation for a supported version of Remedy Single Sign-On.

High Availability deployment

The following figure shows a typical deployment scenario of BMC Atrium Single Sign-On operating in a High Availability (HA) environment. Two BMC Atrium Single Sign-On servers are installed to form a cluster. A load balancer is used as a front end to the cluster, giving the external applications the appearance of a single server. The load balancer distributes requests among BMC Atrium Single Sign-On servers. In the event of a system failure, the load balancer re-directs requests to the remaining servers.

When operating as a cluster, BMC Atrium Single Single Sign-On functions as a single virtual server. Therefore, certain configuration information is shared between nodes. For example, when one node is configured, the other nodes have the same information.

The following information is global to all nodes in the cluster:

  • Administrative accounts
  • Authentication
  • User profiles
  • Data stores
  • User accounts (internal LDAP)

Typical HA deployment

When configured, BMC Atrium Single Sign-On server nodes communicate with each other through the LDAP and HTTPS ports. These ports are specified during installation. The following figure shows the communication between the nodes and the load balancer.

Communication between BMC Atrium Single Sign-On nodes and a load balancer

Was this page helpful? Yes No Submitting... Thank you