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.
NOTE: 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.
NOTE: You must run setup_em.bat on each node. The batch script checks the version of .Net and installs MDAC2.7.
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:
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:
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:
To avoid a scenario where the Control-M-EM Configuration Agent and the cluster manager control the same component, verify the following:
NOTE: 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:
Parent Topic |