Post-Control-M/Server Migration Procedures

After you finish upgrading the Control-M/Server, you must do the following:

• Renaming a Control-M/Server Component

• Connecting the Gateway to the New Control-M/Server

• Continuing after Control-M/Server Migration

Renaming a Control-M/Server Component

This procedure describes how to rename the Control-M/Server name if required after you migrate both Control-M/EM and Control-M/Server.

Begin

1. Rename the Control-M/Server, as described in Renaming a Control-M/Server.

2. Start the Control-M/EM processes.

Connecting the Gateway to the New Control-M/Server

This procedure describes how to connect the Gateway to the new Control-M/Server. Perform this procedure if Control-M/EM was not migrated at the same time as Control-M/Server, and you want to reuse the Control-M/Server component in the Configuration domain.

Begin

1. Log in to Control-M/EM via Control-M Web in the new environment.

2. From the icon, select Configuration.

   The Configuration domain opens.

3. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

4. Click the Control-M/Server that was migrated.

   The Control-M/Server Overview dialog box appears.

5. In the left pane, click Communication.

   The Communication settings appear in the main pane.

6. Hover over the Communication area and click .

   The Communication dialog box appears.

7. In the Host and Control-M/EM Port fields, update the hostname and port number to match the new Control-M/Server, and then click Save.

8. Recycle the Gateway.

Continuing after Control-M/Server Migration

This procedure describes how to continue working with existing agents after you have finished the Control-M/Server migration.

Begin

1. To continue working with Agents from the old environment, do one or more of the following:

   • Add the new Control-M/Server host name to the Authorized Servers list for every Agent.

   • Configure the Control-M/Server default communication protocol to match the version of the majority of your connected Agents, as described in Configuring Control-M/Server System Parameters and Communication Parameters.

2. Configure the correct PROTOCOL_VERSION Agent system parameter. You must set the Server-to-Agent protocol version to the lowest version of either the Control-M/Server or Agent. This parameter is defined on both the Agent and the Server for that Agent and they must match. You can use the ctmagcfg Agent configuration utility to define the parameter on the Agent, and the ctm_menu Control-M/Server utility to define it on the server.

   The following table lists the possible values for PROTOCOL_VERSION.

   Control-M/Agent Version	PROTOCOL_VERSION
   9.0.00.300 until 9.0.19.200	12
   9.0.20	13

   If Control-M/Server is version 9.0.21 and the Agent is version 9.0.00.300, then the PROTOCOL_VERSION should be set to 12.

3. If the ctmldnrs.dat file is migrated, copy the ctmldnrs.dat file from the Control-M/Server home folder to the default location (<Control-M/Server_Home>/ctm_server/tmp) or another location, as required.

   On UNIX, the ctmldnrs.dat is deleted from the default location (<Control-M/Server_Home>/ctm_server/tmp) when Control-M/Server is started.

4. After migrating from Linux to Windows, add the SYSTEM user to Control-M/Server security via the ctmsec utility.

   For more information, see Control-M/Server Security.