Upgrade requirements and considerations

Before you upgrade, review the following requirements and considerations to ensure that your environment is ready for the changes.

• During the upgrade, the Client Distribution feature is disabled. After the upgrade, you can only distribute Control-M client version 9.0.18 and higher.
• Ensure that all of your existing Control-M Reporting Facility reports and data are migrated and converted into Control-M Reports, as described in Control-M Reporting Facility migration.
• To benefit from the new features of the upgrade, both Control-M/EM and Control-M/Server must be upgraded to the latest version. For Application Pack deployment, Control-M/Agent must be upgraded to the latest version as well.
• After the client upgrade, you need to set the correct Host and port in the promotion environments. Control-M client 9.0.19 with Compatibility on can promote to all 9.0.19 environments. Control-M client 9.0.19 with Compatibility off can only promote to 9.0.19 environments with compatibility mode turned off. After the client upgrade you cannot promote to Control-M 9.0.00.
• The Control-M client connects to the Control-M/EM server via the Control-M Web Server. If you have upgraded from version 9.0.00, verify that the Web Server hostname and port number are correct. After the upgrade, if HTTPS is not configured on the Control-M Web Server, all Control-M clients communicate with HTTP (not secured).
• If your environment is encrypted with SSL, you need to verify that the Control-M Web Server is configured with SSL and save the Windows keystore before you upgrade the client or use Control-M/EM API, as described in Configuring Control-M/EM Web Server to work with HTTPS.
• If you are upgrading in a high availability environment, see High availability requirements.
• If you are working in a Control-M/EM Distributed environment, you must install the same version on both the Control-M/EM server and Control-M/EM Distributed hosts, as described in Upgrading Control-M/EM on UNIX and Upgrading Control-M/EM on Windows.
• The Workload Archiving server is upgraded automatically during the Control-M/EM Distributed upgrade.
• Control-M automatically collects information on your product usage patterns. This information helps BMC to identify trends, enhance Control-M capabilities, and improve the quality. BMC does not collect any of your personal or organizational identifiable data. Your participation in the usage collection is optional. You can opt-out at any time by changing the values of the UsageCollectionDisabled system parameter to 1, as described in CMS parameters.
• During the upgrade procedure, site standard entities, that were created in the original version before you upgraded are backed up to a file name def_items_table_backup.dat. If you want to downgrade to the same version you had before, you can restore the original site standards by running one of the following commands:
  • Windows: util.exe –U <dbo user> -P <dbo password> -import -replace -type wcm -file "<installation location>\install\def_items_table_backup.dat"
  • UNIX: em util –U <dbo user> -P <dbo password> -import -replace -type wcm -file <installation_account_home_directory>/ctm_em/install/def_items_table_backup.dat"

  If a new site standard was created in the new version and is attached to a folder, then after the downgrade is completed, this folder must be manually set to one of the restored site standard entities or defined without any site standard. To change the link, you need to open that folder in a temporary Workspace and change the site standard in the Workspace. This change cannot be done from the Folder Manager.

• If modified demo scripts from previous versions are stored in the $HOME/ctm_em/bin directory, they are overwritten during the upgrade and need to be recreated. It is recommended to back up the scripts separately, or modify the new demo scripts that are placed in the directory as part of the upgrade.
• If you want to you downgrade to a previous version, you perform the uninstall procedure, as described in Control-M uninstall. However, after a downgrade, Control-M components are up and running.
• Promotion from one environment to another is only available when both Control-M/Servers are the same version. Consider this limitation before upgrading.
• After you have upgraded, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.