Multiple servers deployed at a single location

You can achieve high availability and fault tolerance (HA/FT) by deploying multiple peers and by utilizing the built-in features of the BMC Atrium Orchestrator components.

  • To achieve HA, a grid must survive the failure of one or more of its components and continue to execute workflows.
  • To achieve HA/FT, you must configure a topology that guarantees the survival of the minimum components required for the grid to execute workflows. You can configure this setup by deploying redundant components, using built-in failover features, and by installing an external database.


To set up high availability using your authentication service, refer to the authentication system instructions.

  • Remedy Single Sign-On HA environment
  • BMC Atrium Single Sign-On HA deployment


    BMC Atrium Single Sign-On is not supported for use with BMC Atrium Orchestrator Platform 7.9.01 and later versions.

In this configuration, the repository, BMC external authentication service (optional - needed if you do not use the embedded authentication service), and the CDP with any optional components reside on separate servers as shown in the following figure. In this setup, the CDP handles all of the grid administration and workflow execution for the grid. The BMC Atrium Orchestrator Development Studio component is installed on a separate computer.

Because the CDP contains the largest number of deployable components and requires a dedicated server, BMC recommends this basic configuration for a production environment.

  • You must install the CDP in a Tomcat instance that is separate from a BMC external authentication system and the repository applications.
  • As an option, you can install the BMC Atrium Orchestrator Operator Control Panel component with the CDP or on separate servers.


If you are installing a non-English version of the Operator Control Panel,  you must install it separately from the CDP. You must install the non-English OCP and CDP on separate Tomcat servers.

In the following figure, each server contains a separate Tomcat instance.

Topology Single Peer New

The following topics describe other deployment use cases for multiple servers deployed at a single location: