This procedure describes how to transfer installation packages to existing Control-M/Agents and upgrade them to the current base version or fix pack on UNIX, Windows, or AS400.
NOTE: (Windows only) An upgrade does not begin until all jobs have ended, unless you selected Force Upgrade in a Retry (Control-M/Agent 9.0.00 or earlier).
NOTE: You cannot upgrade more than one Control-M/Agent on the same Windows computer simultaneously.
To upgrade Control-M/Agents:
From the Manage tab, select Deployment.
The Deployment window appears.
Click New Activity > Agent> Upgrade.
The Upgrade Control-M Agents Activity window appears.
Do the following:
In the Activity Name field, type a new name for this activity.
In the Description field, describe the purpose of this activity (optional).
In the E-Mail Notification field, type the email address(es) that you want to receive notifications about this activity (optional).
To receive email notification, you need to define the email server parameters, as described in SMTP parameters.
Select one of the following:
Send Agent Deploy to Control-M Agent(s): Transfers the installation package to specific Control-M/Agent computers. After the package is transfered, you can manually start the upgrade process, at any time, from the Agent Deployment window or upgrade with CLI, as described in ccmcli.
Send and Install Agent Deploy to Control-M Agent(s): Transfers the installation package to specific Control-M/Agent computers and begins the upgrade process automatically.
Use network location to update Control-M/Agent(s): Upgrades the selected Control-M/Agents directly from a network location. This option improves performance, which avoids transferring the installation packages from Control-M/Server to the Control-M/Agents and saves disk space on the Control-M/Agents. To upgrade from a network location, the Control-M/EM system parameter CentralDeployLocation and Control-M/Server system parameters CTM_AUTO_DEPLOY_PACKAGE_LOCATION_WINDOWS and CTM_AUTO_DEPLOY_PACKAGE_LOCATION_UNIX must be defined with the same network location. This option is only available on Control-M/Server 9.0.21 and higher.
NOTE:
The Control-M/Agent installation package is deleted after a successful upgrade. If the upgrade failed or you performed a transfer only, then the installation package remains on the Control-M/Agent computer for 30 days. If you want to change this setting, define the Control-M/Agent system parameter AD_RETAIN_PACKAGES, as described in Defining Control-M/Agent system parameters.
The Control-M/Agent installation package remains on the Control-M/Server computer for 30 days. If you want to change this setting, define the Control-M/Server AD_RETAIN_PACKAGES, as described in Defining Control-M/Server system parameters.
Click Next.
From the Upgrade Agents to Version drop-down list, select the version or fix pack that you want to upgrade to and then select the Control-M/Agent(s) that you want to upgrade.
In the Set Java home directory location for the selected Agents field, type the path that points to the external Java installation for all selected Agents.
If the path is incorrect and the deploy fails, you can update the path in the Properties pane.
NOTE: You can only define one Java home directory for this deployment activity. If you need to deploy Agents to multiple platforms, you must create a separate deployment activity for each platform. For more information about external Java, see Control-M External Java Installation.
Depending on which method you selected, click Transfer, Upgrade or Send.
The transfer process starts and progress messages appear in the right pane of the deployment activity. To view and troubleshoot the internal stages of the upgrade, click Log from the Agent Deployment window. If you selected to transfer the installation package, you can upgrade the Control-M/Agent(s) any time after the transfer is complete. A job runs on the Control-M/Agent(s) to verify that it upgraded successfully.