Product Documentation

Configuring High Availability on Device Manager

Dec 21, 2015

You can deploy up to three instances of Device Manager to create a high availability pair, which is also called a cluster. You configure one Device Manager instance as the primary role in the cluster and the other Device Manager instances as the secondary role in the cluster. In this deployment, the primary Device Manager listens for requests, and serves user requests. The secondary Device Manager synchronizes its data with the data on the primary. The two instances of Device Manager work as an active-passive pair, in which only one instance of Device Manager is active at a time.

If the current primary Device Manager stops responding for any reason, the current secondary Device Manager takes over and becomes the primary. The new primary Device Manager begins to serve user requests.

Device Manager in a cluster configuration requires a network load balancer to create a high availability pair as well as to distribute the load between Device Manager servers.

You need to configure the following:

  • Windows Server 2008 R2. Install each Device Manager instance on a separate Windows server.
  • Configure the Windows servers as a cluster.
  • Virtual IP address or host name on the load balancer. Device Manager uses this information to route user requests.
  • SSL session persistence for ports 443 and 8443 on the load balancer.
  • SQL Server database accessible from the Device Manager node(s) and user credentials to connect to the database. Each node connects to the same database.
  • Network Time Protocol (NTP) server to synchronize time for all nodes and SQL DB server.

After you install Device Manager and configure the initial settings, there are some additional configuration steps. These include:

  • Editing an xml file to replicate session information on all cluster nodes in the Tomcat cluster.
  • Enabling clustering on Device Manager.
  • Configuring properties on the Tomcat server.
  • Copy certificates from cluster node 1 to cluster node 2.
  • Stopping and starting the Device Manager Windows service.

You can also use the PostGRE SQL database for high availablity. If you use this database, you need to run a utility to import database information to Device Manager.