Control-M Upgrade

You can upgrade any Control-M component to a higher version on the same host to avoid downtime from data migration to a new host. For the full Control-M component version compatibility list, see Control-M Compatibility for Version 9.0.22.

Control-M processes stay up during file preparation. You must only stop the processes briefly for the actual component upgrade.

  • You can only upgrade from Control-M/EM and Control-M/Server version 9.0.20 or higher. For lower versions, you must first upgrade to 9.0.20, as described in Control-M Upgrade, and then upgrade to 9.0.02.

  • You must install and maintain an external Java package to operate Control-M. Control-M does not come with Java because of the frequency of Java library updates. An external Java package ensures that Java libraries remain updated to their latest versions to enable Control-M to operate as efficiently as possible. For more information, see Control-M External Java Installation.

Upgrading Control-M

This procedure describes how to upgrade Control-M components.

Before You Begin

Begin

  1. Upgrade Control-M/EM.

  2. Upgrade Control-M clients with one of the following procedures:

  3. Upgrade Control-M/Server.

  4. Upgrade the relevant database server with one of the following procedures:

  5. Upgrade Control-M/Agent.

Upgrade Requirements and Considerations

The following table lists requirements and considerations to review prior to the upgrade.

Component or Topic

Requirement

Authorizations

Control-M authorizations are only assigned to roles. To upgrade from any version lower than 9.0.21, you must assign all users to a role. Previous user authorizations are migrated in an upgrade but cannot be modified. Therefore, BMC recommends that you move all user authorizations to a role and assign the role to specific users to ensure that all user attributes can be managed. For more information, see User and Role Authorizations.

PostgreSQL Database Server

See Control-M Database Server Upgrade.

Promotion

  • Promotion from one environment to another is only possible if the source and target Control-M/EM hosts are the same version of Control-M/EM.

  • Check whether any of your promotion rules involve changes to fields in plug-ins that are deprecated and discontinued. These promotion rules must be deleted.

HTTPS Protocol

  • The Control-M client connects to the Control-M/EM server via the Control-M Web Server. After the upgrade, BMC recommends that you use the HTTPS protocol with a secured port as opposed to the insecure HTTP protocol.

  • For Control-M Web, you are automatically redirected to an HTTPS protocol with the secured port.

Control-M Workflow Insights

To avoid any Kafka configuration issues when you perform a full Control-M installation, you must do the following:

  • Shut down both Control-M/EM and Control-M/Server before you upgrade.

  • Upgrade Control-M/EM before you upgrade Control-M/Server.

Application Integrator

Export all job types created through Application Integrator prior to the upgrade.

If you want to upgrade from version 9.0.19.xxx to 9.0.22, you must re-import all the job types after the upgrade. To avoid this additional import step, you can plan an upgrade in stages, as follows:

  1. Upgrade from version 9.0.19.xxx to 9.0.20.200.

  2. Upgrade to version 9.0.22.000.

Control-M/EM Distributed

  • 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 Control-M Workload Archiving and Control-M Workflow Insights servers are upgraded during the Control-M/EM Distributed upgrade.

Client Distribution

To enable users to upgrade their clients without installing Java, you can save Java 1.8 (64-bit) or higher to a network location that is accessible by all Control-M client hosts and define the pathname in the following file:

<EM_HOME>/Client_Updates/conf/client_deploy_java.properties

java_home_path=/network/java_home_directory

High Availability

  • To upgrade in a High Availability environment, see High Availability Requirements.

  • If you set the Secondary to Primary after a failover, you cannot downgrade to an earlier version. You must fall back to the Primary before you can downgrade.

Demo Ha Cluster Scripts

If modified demo scripts from previous versions are stored in the $HOME/ctm_em/bin directory, the upgrade overwrites them and you must recreate them.

BMC recommends that you back the scripts up separately or modify the new demo scripts that are placed in the directory as part of the upgrade.

For more information, see Modifying the Demo Ha Cluster Script.

Site Standards

Site standards defined in the original version of Control-M are backed up to the def_items_table_backup.dat file during the upgrade.

To downgrade, see Restoring Site Standards after Downgrade.

Rule-Based Calendars

After you upgrade, if you have rule-based calendars with specific dates, you must Force Upload them to the Control-M/Server.

Backup Folders

After you upgrade, the backup folder of the previous version is compressed into a ZIP or TAR file and encrypted.

However, the exe folder of the previous version is kept on the host for three days before it is automatically deleted for the following components:

  • Control-M/EM 

  • Control-M/Server

  • Control-M/Agent

  • Application Integrator

  • Automation API

Verifying Upgrade Readiness

This procedure describes how to use the is_upgrade_ready utility to verify the minimum requirements for the Control-M/EM or Control-M/Server upgrade.

Before the utility checks whether requirements are met, it detects if the size of your environment is small, medium, or large, as described in Control-M/EM Production Size and Control-M/Server Production Size.

Before You Begin

  • Download the upgrade package, as described in Obtaining Control-M Installation Files.

  • Ensure that the is_upgrade_ready utility can be used during your planned upgrade. This utility is supported for upgrades from version 9.0.21.200 or later, on Linux or Windows platforms (but not on AIX).

Begin

  1. Log in to the host where your current Control-M Full Installation, Control-M/EM, or Control-M/Server is installed.

  2. Navigate to the temporary installation directory that contains the upgrade files.

  3. From the UpgradeReady/upgrade_ready directory, type one of the following commands:

    • Linux: is_upgrade_ready.sh -p <PRODUCT_NAME>

    • Windows: is_upgrade_ready.bat -p <PRODUCT_NAME>

    where <PRODUCT_NAME> is em (Control-M/EM) or ctms (Control-M/Server).

    A summary of the results and the path to a full report appears.

Measurements of the total RAM available to the operating system are often higher than the actual physical RAM, to avoid false alerts.

Control-M Downgrade

If you want to downgrade Control-M to version lower than 9.0.02, you must perform an uninstall to revert to the previous version.

A full uninstall lets you downgrade Control-M and all components, as described in Control-M Full Uninstall.

You can also downgrade individual Control-M components with the following uninstall procedures: