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:
If the target version is 9.0.20, you can upgrade from Control-M/EM 9.0.00.500, Control-M/Server 9.0.00.400. If the target version is 9.0.20.200, you can upgrade from version 9.0.18 or higher.
After you have upgraded, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
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 9.0.18 and higher).
An upgraded Control-M/Server is compatible with lower versions of Control-M/EM (from 9.0.18 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.
If you are using the BMC dedicated PostgreSQL database, after you have upgraded Control-M/EM or Control-M/Server, the PostgreSQL database server version remains the same and must be upgrade, as described in Upgrading the PostgreSQL database server.