Installing BMC Atrium Orchestrator Platform with BMC Atrium Single Sign-On high availability clusters

This topic describe how to install and configure BMC Atrium Orchestrator Platform with BMC Atrium Single Sign-On high-availability clusters. 

BMC Atrium Single Sign-On in a High Availability (HA) cluster environment is implemented as a redundant system with session failover. In this model, if a node fails, the BMC Atrium Single Sign-On load is transitioned to the remaining servers with minimal interruption. When multiple BMC Atrium Single Sign-On servers are installed and configured to operate as a cluster, a system failure is absorbed by the remaining cluster nodes.

The BMC best practice is to run BMC Atrium Single Sign-On cluster behind a firewall to protect the communications channels, such as replication, BMC Atrium Single Sign-On sessions, and administrative communications, between the nodes. The communications are encrypted; however, the ports must be exposed for connections from the other clustered machines.

• • Before you begin
  • High-level tasks for configuring BMC Atrium Orchestrator Platform with BMC Atrium Single Sign-On cluster
  • Where to go from here

The following figure describes a high-level overview of configuring BMC Atrium Single Sign-On cluster with BMC Atrium Orchestrator Platform by using a load balancer.

Before you begin

Ensure that you install the following versions of BMC Atrium Single Sign-On and Apache Load Balancer server:

• BMC Atrium Single Sign-On 8.1.x
• Apache Load Balancer server: [httpd] Version 2.2.17 server with openssl_0.9.8o

High-level tasks for configuring BMC Atrium Orchestrator Platform with BMC Atrium Single Sign-On cluster

The following table describes the end-to-end tasks required to set up BMC Atrium Orchestrator Platform with a BMC Atrium Single Sign-On cluster with more than one node. 

Where to go from here

Installing-BMC-Atrium-Single-Sign-On-in-a-cluster