Control-M/Server Upgrade

You can upgrade to Control-M/Server 9.0.02 on UNIX and Windows from version 9.0.20 and higher. Control-M/Server must be upgraded after Control-M/EM.

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

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

Control-M/Server SSL Requirements

If Control-M/Server is configured for TCP mode, the Control-M/Server upgrade installs the default PKCS #12 archive file.

The following actions are required for sites with SSL:

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

  • If Control-M/Server is configured to communicate via an SSL protocol lower than TLS1_2 (either SSLv3 or TLS1), you must update SSL to TLS1_2.

  • If you use Control-M/Server 9.0.20.204, you must disable SSL before you upgrade to 9.0.02.

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

Upgrading Control-M/Server on UNIX

This procedure describes how to upgrade from Control-M/Server 9.0.20 and higher to the latest version of Control-M/Server on UNIX. If you want to upgrade multiple instances of Control-M/Server on several hosts with the same configuration, use the automatic upgrade, as described in this procedure.

The default upgrade is interactive and uses a GUI display. XServer must be running and configured with the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console upgrade or perform an automatic upgrade.

Before You Begin

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

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

  • Set the BMC_INST_CTM_APIGTW_PORT environment variable to an unused port. The default is 8393.

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

  • If your current Control-M components are installed with the Full Installation method and you upgrade from a version lower than 9.0.20, upgrade Control-M/EM before you upgrade Control-M/Server.

  • Verify that the Control-M/Server 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/Server SSL Requirements.

  • Shut down Control-M/Server.

  • 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/Server is installed.

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

  3. From your home directory, type the following:

    <source_path>/setup.sh

  4. Do one of the following:

    • Interactively Upgrade: Select Control-M/Server 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/Server and continue with the on-screen instructions until the Summary window appears.

        There is no confirmation to shut down Control-M/Server 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. To run the upgrade script, type the following:

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

        The upgrade log is in the following location:

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

  5. If a firewall is active, see System Configuration.

Upgrading Control-M/Server on Windows

This procedure describes how to upgrade from Control-M/Server 9.0.20 and higher to the latest version of Control-M/Server on Windows. If you want to upgrade multiple instances of Control-M/Server on several hosts with the same configuration, use the automatic upgrade, 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/Server, as described in Control-M/Server Windows System Requirements.

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

  • Set the BMC_INST_CTM_APIGTW_PORT environment variable to an unused port. The default is 8393.

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

  • If your current Control-M components are installed with the Full Installation method and you upgrade from a version lower than 9.0.20, upgrade Control-M/EM before you upgrade Control-M/Server.

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

  • If Control-M/EM and Control-M/Server are installed on the same Windows host (including cluster), they must be installed on the same drive.

  • Shut down Control-M/Server.

  • 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.

  • 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/Server SSL Requirements.

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/Server 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/Server 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/Server and continue with the on-screen instructions until the Summary window appears.

        There is no confirmation to shut down Control-M/Server 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 following upgrade script:

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

        The upgrade log is in the following location:

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

  5. If a firewall is active, see System Configuration.

Control-M/Server Downgrade

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

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