This knowledge article cover the steps required to implement  a distributed environment, separated of  the main Control-M/Enterprise Manager and balance the load between several machines.

Applies to:

Control-M/Enterprise Manager 7.0.00 and 8.0.00

For Control-M/Enterprise Manager 9.0.00 and above, please note that there's an additional option during installation called "Additional Distributed Installation", choose this instead of "Custom Installation".

Legacy ID:KA414278

In this example, the following names will be used for the machines involved:

Host 1: Full EM installation - "Main EM"
Host 2: Full EM installation - "Second GSR"

Perform these steps to install and setup a secondary GUI Server:

Step 1. On the "Main EM", environment:

One CORBA Naming Service is up and all GUI Servers will be registered in this Naming Service. This way the clients (Control-M/Enterprise Managers End Users' GUIs) will be able to see several GUI Servers name in the combo box of the login window when they first open the GUI/Desktop Client, and select through which one they want to connect.

Step 2. On the "Second GSR", environment:

To install the GUI Server you should perform a Full EM Server installation. This will install the entire product, there is no option to install only a GUI Server.

Using Graphical User Interface

Step 2a. In "Installation type" screen, select "Control-M Specific component" and "Control-M Enterprise Manager".
Step 2b. In "Setup Type" screen, select "Custom"
Step 2c. In "Database Server type" screen you must choose the same database type as is used on the "Main EM".
Step 2d. In "Database Properties" screen you must leave the "Create a new database" UNCHECKED.

WARNING: If you don't leave the "Create a new database" option UNCHECKED, YOUR "Main EM" DATABASE WILL BE COMPLETELY ERASED. ENSURE YOU HAVE A BACKUP OF YOUR "Main EM" DATABASE PRIOR TO EXECUTING THIS INSTALLATION.

NOTE: When using the "non graphical mode", in "Database Properties" screen you must set the "Create a new database" to NO.

Step 3. On the "Second GSR", environment:

Configure the CORBA client's connection to point to the CORBA which run on "Main EM" CORBA Backup config.xml

Step 3a. Make a copy of the original config.xml file ( located under $HOME/ctm_em/etc/domains).
Step 3b. Make a copy of "default4client.xml" file and rename it to "config.xml"
Step 3c. Edit the new config.xml file and change the host name to the CORBA that run on Main EM:

<variable name="-ORBInitRef" value="NameService=corbaloc::1.2@<Main EM host name>:13075/NameService"/>

Step 3d. Update the "ORBSvcConf" variable with the location of client_server.conf file ("Second GSR")

<variable name="-ORBSvcConf" value="/home/ctm700/ctm_em/etc/client_server.conf"/>

Step 4. On the "Second GSR", environment:

CORBA Naming Service should remain down.
Control-M Configuration Server (CMS) should remain down.
Only CONTROL-M/EM Configuration Agent should be up!

Step 5. The same Fix Pack and patches installed on "Main EM" should be installed on Second GSR.

Step 6. On the "Main EM", environment:

When defining the Second GSR component in the Control-M Configuration Manager, set the Host Name field in the Running On area to "Second GSR" host name.

1. Control-M/Enterprise Manager