Overview

This topic provides an overview of a clustered environment for high availability for Configuration Hub. It does not cover SCADA Enhanced Failover. iFIX Failover should not be used on a node participating in this High Availability configuration. See Special Considerations for SCADA Enhanced Failover for details on SCADA Enhanced Failover with Configuration Hub.

High availability (HA) is the ability of a system to operate continuously without failing for a designated period of time. HA works to ensure a system meets an agreed-upon operational performance level. The following sections describe how high availability works with Configuration Hub.

About Failover Cluster

In a cluster environment, multiple servers are installed, which share the same data. Each of these servers is called a node. One of them acts as the primary node, while the others are standby nodes. If the primary node is down, one of the standby nodes is used.

For example, if Configuration Hub on the primary node is unable to connect to the server, then the user session on the standby node is activated. Therefore, you will still be able to connect to the server using Configuration Hub installed on the standby node.

Configuration Hub works with Microsoft Failover Cluster Manager to ensure high availability of web-based clients. The following services are shared between the primary and standby nodes in a cluster. Using Failover Cluster Manager, you must add these services to the cluster.

  • ConfighubContainerService
  • ConfigHubHttpdService

Refer to Configure High Availability for Configuration Hub.

For additional information on Windows failover clustering, visit the following links: