Control-M/EM Upgrade

You can upgrade to Control-M/EM 9.0.02 for UNIX and Windows from version 9.0.20 and higher.

The following procedures describe Control-M/EM upgrade process:

• Upgrading Control-M/EM on UNIX

• Upgrading Control-M/EM on Windows

You can also downgrade Control-M/EM to the previous  version, as described in Control-M/EM Downgrade.

Control-M/EM SSL Requirements

If Control-M/EM is configured for TCP mode, the Control-M/EM upgrade installs the default PKCS #12 archive file. If the CmsCommMode system parameter value is SSL or AUTO, with at least one Control-M/Server connected via SSL, then you must ensure the following:

• You cannot upgrade Control-M/EM if you utilize SSL with a KDB keystore. You must deploy a PKCS #12 keystore before you upgrade to 9.0.02.

• The security policy must be configured to the TLS 1.2 protocol before the upgrade.

• If you installed Control-M/EM 9.0.20.205, you must disable SSL before you upgrade to 9.0.02.

• Manage_SSL_BYO: If the value of the message digest algorithm is sha1, it is upgraded to sha256. If the value of the certificates key length is 1,024, it is upgraded to 2,048.

For more information about security policy attributes, see Security Policies.

Upgrading Control-M/EM on UNIX

This procedure describes how to upgrade from Control-M/EM 9.0.20 and higher (Default and Distributed) to the latest version of Control-M/EM on UNIX. To upgrade multiple instances of Control-M/EM on several hosts with the same configuration, use the automatic installation, as described in this procedure.

Before You Begin

• Verify that your operating system and database software is compatible with the new version of Control-M/EM, as described in Control-M/EM UNIX System Requirements.

• Verify that you meet the Java requirements, as described in Control-M External Java Installation.

• If you upgrade Control-M in a cluster environment, see Control-M/EM UNIX Cluster Configuration.

• Verify that the Control-M/EM database server is up.

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

• Use the is_upgrade_ready utility to verify minimum upgrade requirements, as described in Verifying Upgrade Readiness. This enables you to resolve detected issues even days or weeks before the upgrade.

• If your site uses SSL, verify that you meet the requirements, as described in Control-M/EM SSL Requirements.

• If you have a Control-M/EM Distributed installation, you must upgrade the default Control-M/EM first and then upgrade the Distributed Control-M/EM. The Workload Archiving server is upgraded automatically during the Control-M/EM Distributed upgrade.

• If you upgrade in a Full installation environment, 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.

Begin

1. Copy the upgrade files from the temporary installation directory to the host where Control-M/EM is installed.

2. Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.

3. Navigate to the home directory and run the following command:

   <source_path>/setup.sh

4. Do one of the following:

   • Interactively Upgrade: Select Control-M/Enterprise Manager and continue with the on-screen instructions until the upgrade is complete.

   • Automatically Upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

     1. Select Control-M/Enterprise Manager and continue with the on-screen instructions until the Summary window appears.

        There is no confirmation to shut down Control-M/EM processes. It is done automatically.

     2. Click Generate and select the location to create the XML parameter file.

     3. Click Yes to quit the upgrade.

        A confirmation message appears.

     4. Click Yes.

     5. Copy the automatic upgrade parameters file to a network location that is accessible to all hosts where you want to perform an automatic upgrade.

     6. Run the following command:

        <source_path>/setup.sh -silent <xml_path>/<filename.xml>

        The upgrade logs are in the following location:

        <$HOME>/BMCINSTALL/log/BMC_Control-M_Enterprise_Manager_<date-time>.log

        Control-M/EM configured by default for HTTP. To secure your environment, BMC recommends that you change your configuration to HTTPS, as described in Zone 1 SSL Configuration.

Upgrading Control-M/EM on Windows

This procedure describes how to upgrade from Control-M/EM 9.0.20 (Default and Distributed) and higher to the latest version of Control-M/EM on Windows. If you want to install multiple instances of Control-M/EM on several hosts with the same configuration, use the automatic installation, as described in this procedure.

Before You Begin

• Ensure that your operating system and database software is compatible with the new version of Control-M/EM, as described in Control-M/EM Windows System Requirements.

• Verify that you meet the Java requirements, as described in Control-M External Java Installation.

• If you install Control-M on a cluster environment, see Control-M/EM Windows Cluster Configuration.

• If MSSQL 2016 and higher is installed on the same host as Control-M/EM, you must shut down the PolyBase service before you upgrade.

• Verify that the Control-M/EM database server is up.

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

• Use the is_upgrade_ready utility to verify minimum upgrade requirements, as described in Verifying Upgrade Readiness. This enables you to resolve detected issues even days or weeks before the upgrade.

• If your site uses SSL, verify that you meet the requirements, as described in Control-M/EM SSL Requirements.

• If you have a Control-M/EM Distributed installation, you must upgrade the default Control-M/EM first and then upgrade the Distributed Control-M/EM. The Workload Archiving server is upgraded automatically during the Control-M/EM Distributed upgrade.

• If you upgrade in a Full installation environment, 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.

Begin

1. Log in to the host with a user ID that has Administrator permissions.

2. Copy the upgrade files from the temporary installation directory to the host where Control-M/EM is installed.

3. From a command prompt window, type the following:

   <source_path>\setup.exe.

4. Do one of the following:

   • Interactively Upgrade: Select Control-M/Enterprise Manager and continue with the on-screen instructions until the upgrade is complete.

   • Automatically Upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

     1. Select Control-M/Enterprise Manager and continue with the on-screen instructions until the Summary window appears.

        There is no confirmation to shut down Control-M/EM processes. It is done automatically.

     2. Click Generate and select the location to create the XML parameter file.

     3. Click Yes to quit the upgrade.

        A confirmation message appears.

     4. Click Yes.

     5. Copy the automatic upgrade parameters file to a network location that is accessible to all hosts where you want to perform an automatic upgrade.

     6. Log in with a user ID that has Administrator permissions on the current host.

     7. Run the upgrade script, as follows:

        <source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>

        The upgrade log is in the following location:

        %temp%\BMC_Control-M_Enterprise_Manager_<date-time>.log

        Control-M/EM configured by default for HTTP. To secure your environment, BMC recommends that you change your configuration to HTTPS, as described in Zone 1 SSL Configuration.

Control-M/EM Downgrade

If you want to downgrade to a Control-M/EM version lower than 9.0.02, you uninstall Control-M/EM and the version will automatically revert to the previous version.

The following procedures describe how to downgrade Control-M/EM:

• Uninstalling Control-M/EM from UNIX

• Uninstalling Control-M/EM from Windows