Control-M/EM Windows Cluster Configuration

The Control-M/EM installation automatically recognizes the cluster environment and prompts you to define the Cluster group (cluster aware) or Local install (cluster non-aware). To install, see Installing Control-M/EM on Windows.

  • If a previous version of Control-M/EM was uninstalled on the Windows cluster and you are attempting to install a new Control-M/EM installation on it, you must restart the resource manager or the cluster nodes.

  • You must run setup_em.bat on each node. The batch script checks the version of .NET and installs MDAC2.7.

  • Before you install Control-M/EM on cluster environment, you must define a File Server Role. For more information, see Windows documentation.

  • Automatic installation and automatic upgrade of Control-M/EM is not supported for Microsoft Windows cluster environments.

The Cluster Group installation defines the following Control-M components in the CCM with the Desired state set to Ignore and as a resource in the cluster manager in online status:

  • Control-M-EM GCS (Global Condition Server)

  • Control-M-EM WEB (Tomcat server)

  • Control-M-EM GSR (Default GUI server)

In the Cluster Group installation, the following component are always managed by the Cluster even though these component are set to Up in the CCM:

  • Control-M PostgreSQL (if installed with PostgreSQL)

  • Control-M-EM NS (Naming Service)

  • Control-M-EM CMS (Configuration Server)

The Cluster Group installation defines the Control-M-EM configuration agent resource in the cluster manager in online status.

The CD activation of the following Control-M add-ons define the components in the CCM with a Desired state set to Up and as a resource in the cluster manager in offline status:

  • Control-M-EM SLA Management

  • Control-M-EM Forecast

  • Control-M-EM SLS (Self Service Server)

To avoid a scenario where the Control-M-EM Configuration Agent and the cluster manager control the same component, verify the following:

  • All components managed by the cluster must be set to Ignore in the CCM and in online status in cluster manager.

  • All components managed by the Control-M-EM Configuration Agent must be in offline status in the cluster manager and set with a Desired state to Up or Down in the CCM.

    Control-M/EM Distributed functions the same as a regular Control-M/EM in a cluster. The Cluster Group installation defines the Control-M-EM configuration agent resource in the cluster manager in online status.

The following procedures describe how to configure Control-M/EM in a clustered environment on Windows:

Creating an Additional Control-M/EM Component as a Cluster Resource

This procedure describes how to create an additional Gateway, GUI Server, or Forecast server component as a cluster resource in the cluster manager.

Begin

  1. Define a GUI Server, Gateway, or Forecast component in the CCM, as described in Defining a Control-M/EM component.

  2. Set the desired state of the GUI Server component to Ignore.

    If the component is not set to Ignore, both the cluster manager and the Configuration Agent manage the component.

  3. For each Control-M/EM component defined, define a cluster resource component in the cluster manager using one of the following parameters:

Gateway Cluster Resource Parameters

The following table describes the Gateway cluster resource parameters.

Resource Attribute

Control-M-EM-Gateway (CTM/SRVName)

Description

Control-M/EM Gateway

Resource Type

Generic application

Command Line

<EM_HOME>\bin\emgtw.exe

Parameters

-dc <Control-M name>

Current Directory

<EM_HOME>\bin\

Pending Timeout in Seconds

120

Dependencies

Control-M PostgreSQL (If installed using PostgreSQL)

GUI Server Cluster Resource Parameters

The following table describes the GUI Server cluster resource parameters.

Resource attribute

GUI Server

Description

GUI Server

Resource Type

Generic application

Command Line

<EM_HOME>\bin\emguisrv.exe

Parameters

-name <unique name>

Current Directory

<EM_HOME>\bin\

Pending Timeout in Seconds

120

Dependencies

  • Control-M Naming Service

  • Control-M PostgreSQL (If installed using PostgreSQL)

Control-M/Forecast Cluster Resource Parameters

The following table describes the Forecast cluster resource parameters.

Resource attribute

Control-M/Forecast (CTM/SRVName)

Description

Control-M/Forecast

Resource type

generic application

Group

EMxxx

Command line

<EM_HOME>\bin\emforecastsrv.exe

Parameters

-gsr <GUI server name> -n <unique name>

Current directory

<EM_HOME>\bin

Pending timeout in seconds

120

Dependencies

  • Control-M/EM: Control-M Naming Service

  • Distributed Control-M/EM: Control-M-EM-Configuration-Agent