The Control-M upgrade process upgrades your current version of Control-M/Enterprise Manager, Control-M/Server, and Control-M/Agent to the latest version (annual or fix pack) on the same computer. This eliminates the need to migrate data and reduces downtime. To minimize downtime, Control-M processes are up during the upgrade preparation process, which prepares all the required files. After the preparation completes, you are prompted to confirm the shutdown of Control-M processes. After the processes are shut down, the upgrade begins and completes with minimum downtime.
NOTE:
After you have upgraded, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
If you are using 9.0.00.100 or higher, you can do this upgrade procedure. However, if you are using a previous version, you must migrate your data, as described in Introduction to Control-M Migration.
The upgrade process supports compatibility across all Control-M components, as follows:
An upgraded Control-M/EM is compatible with lower versions of Control-M/Server (from 8.0.00.000 and higher).
An upgraded Control-M/Server is compatible with lower versions of Control-M/EM (from 9.0.00.000 and higher)
The following is a typical scenario of the upgrade flow:
Control-M/EM server: After the upgrade completes, Control-M/EM is in Compatibility Mode and older Control-M clients that weren't upgraded can still work with the upgraded Control-M/EM server.
