Control-M/Agent deployment

The Control-M/Agent Deployment tool enables you to automatically upgrade multiple Control-M/Agents from one single point of access.

From the CCM, you can transfer Control-M/Agent software packages to multiple Control-M/Agents. After the transfer, you can then upgrade the Control-M/Agents to version 9.0.20 and higher on UNIX and Windows, and to version 7.0.01 and higher on AS400.

The following procedures describe how to set up the software packages, upgrade, and downgrade Control-M/Agents:

• Copying Control-M/Agent installation packages
• Upgrading Control-M/Agents
• Rolling back Control-M/Agents

For a description of configurable deployment parameters, see Deployment parameters, Control-M/Agent deployment parameters, and Control-M/EM general parameters.

NOTE:

• Control-M/Agent 9.0.20 supports Control-M/Sever 9.0.18 and higher. This enables you to upgrade Control-M/Agents to version 9.0.20 before upgrading Control-M/Server. However, there are additional Control-M/Server patches that you need to install to enable this functionality. For more information and the list of patches, see 000372195.
• After you have upgraded Control-M/Agent, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
• If the Control-M/Agent windows service is set to Log on as > This account, the upgrade must be performed with this user.
• To run a deploy activity in the CCM or in a CLI, you must have full access level in the Configuration and Operation privileges, as described in Privileges.
• To upgrade to Control-M/Agent 9.0.20, Control-M/Agent 8.0.00 or higher must be installed.
• You cannot upgrade more than one Control-M/Agent on the same Windows computer simultaneously.
• BMC recommends to perform the Agent deployment in groups. By default, you can upgrade/downgrade 5 Control-M/Agents simultaneously. To change this configuration, see the DEPLOYMENT_THREADS parameter, as described in Deployment parameters.
• In Windows, when deploying on Control-M/Agent with a very high load of jobs, deployment may fail. You must run the upgrade at a later stage, when the Control-M/Agent is not loaded or install with downtime. If you deploy, upgrade fails with the following message:

  -------------------------------Pay Attention--------------------------------------------

  Installation with no downtime cannot be executed at this moment.

  1. Check communication between Control-M/Agent and Control-M/Server.

  2. Run the ctmagcfg utility. In Advanced parameters, verify that the Logical Agent Name value matches the Control-M/Agent Name defined in the Control-M/Server and rerun the installation again.

  3. To install with downtime, shut down the Control-M/Agent processes and rerun the installation again.