This procedure describes how to upgrade from Control-M/Agent 8.0.00.500 and higher to the latest version of Control-M/Agent on UNIX. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.
NOTE: This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.
NOTE: The default upgrade is interactive and uses a GUI display. XServer must be running and configured using the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console upgrade or perform an automatic upgrade.
Before You Begin
Ensure that you have met the following requirements:
To upgrade Control-M/Agent on UNIX:
If you are upgrading Control-M/Agent in non-root mode, log out user root and log in as the Control-M/Agent user.
<source_path>/setup.sh
NOTE: There is no confirmation to shut down Control-M/Agent processes. It is done automatically.
A confirmation message appears.
<source_path>/Setup_files/components/agent/setup.sh -silent <xml_path>/<filename.xml>
The upgrade log can be found at the following location:
<$HOME>/BMCINSTALL/log/BMC_Control-M_Agent_<date-time>.log
After you have upgraded Control-M/Agent, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
Parent Topic |