Control-M Upgrade
The Control-M upgrade process upgrades your current version of Control-M/Enterprise Manager, Control-M/Server, and Control-M/Agent to the latest annual or fix pack version on the same computer. This eliminates the need to migrate data and reduces downtime. To minimize downtime, Control-M processes stay 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.
-
You can only upgrade from Control-M/EM and Control-M/Server version 9.0.19 or higher. For lower versions, you must first migrate your data, as described in Control-M Migration.
-
Control-M requires an external Java library. To ensure that Java libraries remain updated, Java library deliveries are decoupled from Control-M and not part of the upgrade. For more information, see Control-M External Java Installation.
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.19 and higher).
-
An upgraded Control-M/Server is compatible with lower versions of Control-M/EM (from 9.0.19 and higher).
-
An upgraded Control-M/EM is compatible with lower versions of Control-M client (from 9.0.19 and higher). However, the new features of the higher version are disabled.
For more information, see Compatibility Mode and Control-M Client and Control-M/EM Server Compatibility Scenarios.
-
An upgraded Control-M/Server is compatible with lower versions of Control-M/Agent (9.0.00.300 and higher).
-
An upgraded Control-M/Agent is compatible with lower versions of Control-M/Server (9.0.19 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 were not upgraded can still work with the upgraded Control-M/EM server.
-
Control-M clients: The new features are disabled in Compatibility Mode. You can upgrade manually or with Client Distribution.
-
Control-M/Server
-
Turn off Compatibility Mode, as described in Turning off Compatibility Mode.
-
Control-M/Agents: You can upgrade manually or with Control-M/Agent Deployment.
-
Control-M MFT: See Control-M MFT Deployment
-
Application Pack: See Application Pack Deployment
Before you upgrade, review Upgrade Requirements and Considerations
The following procedures describe how to upgrade Control-M/EM, Control-M/Server, and Control-M/Agent:
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 upgraded, as described in Control-M Upgrade.
If you are using an Oracle or MSSQL external database, see Upgrading an External Oracle or MSSQL Database Server.
Upgrade Requirements and Considerations
The following table lists requirements and considerations to review prior to the upgrade:
Component/Topic |
Requirement |
---|---|
New Features |
You must upgrade both Control-M/EM and Control-M/Server to use the new features of Control-M 9.0.21.100. |
Authorizations |
Control-M authorizations are assigned to roles only. If you are upgrading from any version prior to 9.0.21, you must assign all users to a role. Previous user authorizations are carried over during an upgrade but cannot be modified. 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. |
PostgreSQL Database Server |
You must upgrade PostgreSQL database server to version 11.5 to use version 9.0.21.100. If you do not upgrade, Control-M might not work as expected. If you are using AIX, you cannot upgrade to PostgreSQL 11.5. |
Compatibility Mode |
|
Promotion |
|
HTTPS Protocol |
|
Control-M/Agent |
You can upgrade Control-M/Agent 9.0.00.300 and higher to version 9.0.21.100. |
Control-M Full Installation |
To avoid any Kafa configuration issues, you must do the following:
|
Application Integrator |
Make sure to export all job types that were created through Application Integrator prior to the upgrade. When you upgrade from 9.0.19.xxx to 9.0.21 or 9.0.21.100, you are required to re-import all the job types after you complete the upgrade process. If you want to avoid this additional import step, you can plan an upgrade in stages: first upgrade from 9.0.19.xxx to 9.0.20.200, and then upgrade to 9.0.21.100. |
Control-M/EM Distributed |
|
|
|
SSL |
For more information about security policy attributes, see Security Policies. |
High Availability |
|
Demo Ha Cluster Scripts |
If modified demo scripts from previous versions are stored in the $HOME/ctm_em/bin directory, they are overwritten during the upgrade and you must recreate them. BMC recommends to back up the scripts 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 you created in the original version of Control-M are backed up in the def_items_table_backup.dat file when you upgrade. If you want 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. |
Upgrade Scenarios
The following table lists the supported upgrade options to upgrade to 9.0.21.100 based on your database and version.
Database |
Version |
Upgrade Action |
---|---|---|
PostgreSQL (Dedicated) |
|
|
10.4 |
|
|
11.5 |
Upgrade to Control-M 9.0.21.100. |
|
Oracle |
|
|
19c |
Upgrade to Control-M 9.0.21.100 |
|
MSSQL |
|
|
2014 SP3 |
Upgrade to Control-M 9.0.21.100 (Windows 2012R2 or 2016 only). |
|
|
Upgrade to Control-M 9.0.21.100. |
|
PostgreSQL (Existing) |
9 or lower |
|
10.x |
|
|
|
Upgrade to Control-M 9.0.21.100. |
Compatibility Mode
Compatibility Mode allows users with previous versions of the Control-M client to connect to the latest version of Control-M/EM server in addition to the upgraded Control-M clients. However, when Compatibility Mode is on, new features are disabled in upgraded Control-M clients. This ensures system integrity during the transition to a higher version. After Compatibility Mode is turned off, the new features are enabled in the upgraded Control-M clients and older clients are disconnected. Users that have not upgraded their Control-M clients cannot log in.
After you upgrade to Control-M/EM 9.0.21.100 and turn Compatibility Mode Off, you can no longer downgrade Control-M/EM to a version lower than 9.0.21 since the password encryption method changes.
The following table lists the features that are disabled in Control-M clients after you have upgraded and compatibility mode is on.
Source Version |
Disabled Features |
---|---|
9.0.20.xxx |
|
9.0.19.xxx |
|
Turning off Compatibility Mode
This procedure describes how to turn off Compatibility Mode, which enables new features in upgraded clients.
-
After Compatibility Mode is turned off, users that have not upgraded their Control-M clients cannot log in.
-
After Compatibility Mode is turned off, you cannot turn it back on.
Begin
-
From the CCM in the Manage tab, click Compatibility Mode.
-
Click I have read and understand.
-
Click Turn Off Compatibility Mode.
Control-M/EM server components are restarted automatically.
Control-M Client and Control-M/EM Server Compatibility Scenarios
The following table lists the different Control-M client and Control-M/EM server compatibility scenarios after you upgrade Control-M/EM server from the source (compatibility version) to the new target version.
Control-M/EM Server Source Version |
Control-M/EM Server Target Version |
Client Version |
Result |
---|---|---|---|
9.0.19.xxx | 9.0.21 |
9.0.19.xxx Compatibility Mode: On |
Success |
9.0.19.xxx |
9.0.21 |
9.0.19.xxx Compatibility Mode: Off |
Fail Reason: If compatibility mode is off, the client must be in the same major release as the server target version. |
9.0.19.xxx | 9.0.21 |
9.0.21 Compatibility Mode: On |
Success |
Upgrading Control-M/EM on UNIX
This procedure describes how to upgrade from Control-M/EM 9.0.19 (Default and Distributed) and higher to the latest version of Control-M/EM on UNIX. If you want to upgrade multiple instances of Control-M/EM on several computers using the same configuration, use the automatic installation, as described in this procedure.
-
The default upgrade is interactive and uses a GUI display. XServer must be running and configured using 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.
-
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 are upgrading 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.
-
Before You Begin
Ensure that you have met the following requirements:
-
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 have met Java requirements, as described in Control-M External Java Installation.
-
If you are upgrading Control-M in a cluster environment, see Control-M/EM Cluster Configuration.
Begin
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/EM is installed.
-
Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.
-
From your home directory, type the following command:
<source_path>/setup.sh
-
Do one of the following:
-
Interactive upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.
There is no confirmation to shut down Control-M/EM processes. It is done automatically. -
Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the upgrade.
A confirmation message appears.
-
Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
To run the upgrade script, type the following command:
<source_path>/setup.sh -silent <xml_path>/<filename.xml>
The upgrade logs can be found at the following location:
<$HOME>/BMCINSTALL/log/BMC_Control-M_Enterprise_Manager_<date-time>.log
To ensure compatibility between older versions of Control-M client, Control-M/EM is now running in Compatibility Mode.
By default, Control-M/EM and Control-M clients are configured to work with HTTP. To secure your environment, BMC recommends to 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.19 (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 computers using the same configuration, use the automatic installation, as described in this procedure.
-
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 are upgrading 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.
-
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 have met Java requirements, as described in Control-M External Java Installation.
-
If you are installing 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 upgrading.
Begin
-
Log in to the computer using a user ID that has Administrator permissions.
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/EM is installed.
-
From a command prompt window, enter <source_path>\setup.exe.
-
Do one of the following:
-
Interactive Upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic Upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.
There is no confirmation to shut down Control-M/EM processes. It is done automatically -
Click Generate and select the location to create the XML parameter file.Click Yes to quit the upgrade.
-
Click Yes to quit the upgrade.
-
A confirmation message appears.Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
Log in using a user ID that has Administrator permissions on the current computer.
-
Run the upgrade script, as follows:
<source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
%temp%\BMC_Control-M_Enterprise_Manager_<date-time>.log
To ensure compatibility between older versions of Control-M client, Control-M/EM is now running in Compatibility Mode.
By default, Control-M/EM and Control-M clients are configured to work with HTTP. To secure your environment, BMC recommends to change your configuration to HTTPS, as described in Zone 1 SSL Configuration.
-
-
Upgrading Control-M Client on Windows from the Full Installation Package
This procedure describes how to upgrade the Control-M client to the latest version on Windows from the Full installation package. If you want to install multiple instances of Control-M client on several computers using the same configuration, use the automatic installation, as described in this procedure.
Before You Begin
-
Ensure that your operating system is compatible with the new version of the Control-M client, as described in Control-M/EM Windows System Requirements.
-
Verify that you have met Java requirements, as described in Control-M External Java Installation.
Begin
-
Log in to the computer using a user ID that has Administrator permissions.
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/EM is installed.
-
Do one of the following:
-
Interactive upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.
-
Click Generate and select the location to create the XML parameter file.Click Yes to quit the upgrade.
-
Click Yes to quit the upgrade.
-
A confirmation message appears. Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
Run the upgrade script, as follows:
<source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
%temp%\BMC_Control-M_Enterprise_Manager_<date-time>.log
-
-
Upgrading Control-M Client on Windows from the Client Installation Package
This procedure describes how to upgrade the Control-M client to the latest version on Windows from the client installation package. If you want to install multiple instances of Control-M client on several computers using the same configuration, use the automatic installation, as described in this procedure.
Before You Begin
-
Ensure that your operating system is compatible with the new version of the Control-M client, as described in Control-M/EM Windows System Requirements.
-
Verify one of the following:
-
Java 1.8 (64-bit) or higher is available in your Path Environment Variable.
-
The Java path is on a network, which is accessible from all Control-M clients.
To enable users to upgrade their clients without installing Java, you can place Java 1.8 (64-bit) or higher on a network location that is accessible by all Control-M client machines and define the path in the following file:
<EM_HOME>/Client_Updates/conf/client_deploy_java.properties
java_home_path=/network/java_home_directory
-
Begin
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/EM is installed.
-
From the same command line, run the following command:
<source_path>\setup.exe
If Java is not available, run the following command:
setup.bat -BMC_INST_JAVA_HOME <Java 11 installation directory>
The Java installation directory must contain the bin directory and the Release file.
-
Do one of the following:
-
Interactive upgrade: Follow the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Follow the on-screen instructions until the Summary window.
-
Click Generate and select the location to create the XML parameter file. Click Yes to quit the upgrade.
-
Click Yes to quit the upgrade.
-
A confirmation message appears. Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
Run the upgrade script, as follows:
<source_path>\Setup_files\components\clientem\setup.bat -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
<installFolder>\BMCINSTALL\log\BMC_Control-M_client_<date-time>.log
-
-
Upgrading Control-M Client from the Control-M Welcome Page
This procedure describes how to upgrade the Control-M client on Windows from the Control-M Welcome Page. The Control-M/EM server and port are automatically configured during the installation.
Before You Begin
-
Ensure that your operating system are compatible with the current version of the Control-M client, as described in Control-M Client and Control-M/EM Server Compatibility Scenarios.
-
Verify one of the following:
-
Java 1.8 (64-bit) or higher is available in your Path Environment Variable.
-
The Java path is on a network, which is accessible from all Control-M clients.
To enable users to upgrade their clients without installing Java, you can place Java 1.8 (64-bit) or higher on a network location that is accessible by all Control-M client machines and define the path in the following file:
<EM_HOME>/Client_Updates/conf/client_deploy_java.properties
java_home_path=/network/java_home_directory
-
Begin
-
Open a new browser window before you download and install.
-
Go to <Control-M/EM_Host>:<port>/Welcome/ and from the Control-M Client section, click Download.
-
Run the upgrade and continue with the on-screen instructions until the upgrade is complete.
The upgrade log can be found at the following location:
<installFolder>\BMCINSTALL\log\BMC_Control-M_client_<date-time>.log
Upgrading Control-M/Server on UNIX
This procedure describes how to upgrade from Control-M/Server 9.0.19 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 computers using 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 using 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.
-
If you are upgrading 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.
-
Before You Begin
Ensure that you have met the following requirements:
-
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 have met Java requirements, as described in Control-M External Java Installation.
-
Set the BMC_INST_CTM_APIGTW_PORT environment variable to the number of an unused port of your choice. The default is 8393.
-
If you are upgrading in a cluster environment, see Control-M/Server UNIX Cluster Configuration.
-
If your current Control-M components were installed using the Full Installation method and you are upgrading from a version earlier than 9.0.20, upgrade Control-M/EM before upgrading Control-M/Server.
Begin
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/Server is installed.
-
Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.
-
From your home directory, type the following command:
<source_path>/setup.sh
-
Do one of the following:
-
Interactive upgrade: Select the Control-M/Server option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Server option and continue with the on-screen instructions until the Summary window.
NOTE: There is no confirmation to shut down Control-M/Server processes. It is done automatically.
- Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the upgrade.
A confirmation message appears.
- Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
To run the upgrade script, type the following command:
<source_path>/Setup_files/components/ctm/setup.sh -silent <xml_path>/<filename.xml>
The upgrade log can be found at the following location:
<$HOME>/BMCINSTALL/log/BMC_Control-M_Server_<date-time>.log
-
-
-
If a firewall is active, perform the steps described in System Configuration.
Upgrading Control-M/Server on Windows
This procedure describes how to upgrade from Control-M/Server 9.0.19 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 computers using 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 have met Java requirements, as described in Control-M External Java Installation.
-
Set the BMC_INST_CTM_APIGTW_PORT environment variable to the number of an unused port of your choice. The default is 8393.
-
If you are upgrading in a cluster environment, see Control-M/Server Windows Cluster Configuration.
-
If your current Control-M components were installed using the Full Installation method and you are upgrading from a version earlier than 9.0.20, upgrade Control-M/EM before upgrading Control-M/Server.
-
If you are upgrading 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
-
Log in to the computer using a user ID that has Administrator permissions.
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/Server is installed.
-
From a command prompt window, enter <source_path>\setup.exe.
-
Do one of the following:
-
Interactive upgrade: Select the Control-M/Server option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Server option and continue with the on-screen instructions until the Summary window.
There is no confirmation to shut down Control-M/Server processes. It is done automatically. -
Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the upgrade.
A confirmation message appears.
- Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
Log in using a user ID that has Administrator permissions on the current computer.
-
Run the upgrade script, as follows:
<source_path>\Setup_files\components\ctm\setup.exe -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
%temp%\BMC_Control-M_Server_<date-time>.log
-
-
-
If a firewall is active, perform the steps described in System Configuration.
Upgrading Control-M/Agent on UNIX
This procedure describes how to upgrade from Control-M/Agent 9.0.00.300 and higher to the latest version of Control-M/Agent on UNIX, which includes Application Integrator and Automation API CLI. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.
-
This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.
-
If you upgrade the Agent, Application Integrator that was part of Application Pack is upgraded as well. If you roll back the Agent, then Application Integrator cannot work. To re-enable Application Integrator, you must uninstall and then reinstall Application Pack.
-
If Application Pack is installed, verify that all Application Integrator jobs have completed before upgrading the Agent.
The default upgrade is interactive and uses a GUI display. XServer must be running and configured using 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
Ensure that you have met the following requirements:
-
Ensure that your operating system is compatible with the new version of Control-M/Agent, as described in Agent System Requirements for Linux.
-
Verify that you have met Java requirements, as described in Control-M External Java Installation.
-
Ensure that the Internal Process Communication (IPC) subsystem is enabled.
-
Verify that your locale is set to English before beginning the upgrade.
-
(AIX only) You must set the tcp_nodelayack to 1 as a root user, as follows:
/usr/sbin/no -o tcp_nodelayack=1
Begin
-
Log in as a Control-M/Agent user and then switch to user root.
If you are upgrading Control-M/Agent in non-root mode, log out user root and log in as the Control-M/Agent user.
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/Agent is installed.
-
Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.
-
From the Agent home directory, type the following command:
<source_path>/setup.sh
-
Do one of the following:
-
Interactive upgrade : Select the Control-M/Agent option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Agent option and continue with the on-screen instructions until the Summary window.
There is no confirmation to shut down Control-M/Agent processes. It is done automatically.
-
Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the upgrade.
A confirmation message appears.
-
Click Yes.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
To run the upgrade script, type the following command:
<source_path>/Setup_files/components/agent/setup.sh -silent <xml_path>/<filename.xml>
The upgrade log can be found at the following location:
<$HOME>/BMCINSTALL/log/BMC_Control-M_Agent_<date-time>.log
-
-
Upgrading Control-M/Agent on Windows
This procedure describes how to upgrade from Control-M/Agent 9.0.00.300 and higher to the latest version of Control-M/Agent on Windows. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.
-
This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.
-
If there are multiple Agents installed on the same machine, you must upgrade each Agent to the same version before you can start up any Agent.
-
If you upgrade the Agent, Application Integrator that was part of Application Pack is upgraded as well. If you roll back the Agent, then Application Integrator cannot work. To re-enable Application Integrator, you must uninstall and then reinstall Application Pack.
-
If Application Pack is installed, verify that all Application Integrator jobs have completed before upgrading the Agent.
Before You Begin
-
Ensure that your operating system is compatible with the new version of Control-M/Agent, as described in Agent System Requirements for Windows.
-
Verify that you have met Java requirements, as described in Control-M External Java Installation.
Begin
-
Log in to the computer using a user ID that has Administrator permissions.
-
Copy the installation files from the temporary directory that you created in Obtaining Control-M Installation Files, to the host where the existing Control-M/Agent is installed.
-
From a command prompt window, enter <source_path>\setup.exe.
-
Do one of the following:
-
Interactive upgrade : Select the Control-M/Agent option and continue with the on-screen instructions until the upgrade is complete.
-
Automatic upgrade :Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
-
Select the Control-M/Agent option and continue with the on-screen instructions until the Summary window.
There is no confirmation to shut down Control-M/Agent processes. It is done automatically. -
Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the upgrade.
A confirmation message appears.
-
Click Yes.
The automatic upgrade XML parameters file that is created (<filename>.xml) is relevant only for computers with the same agent instance name. Otherwise, a separate <filename>.xml file must be created for each computer, or modified manually for each computer.
-
Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
-
Log in using a user ID that has Administrator permissions on the current computer.
-
Run the upgrade script, as follows:
<source_path>\Setup_files\components\oneagent\setup.exe -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
%temp%\BMC_Control-M_Agent_<date-time>.log
-
-
Upgrading the PostgreSQL Database Server
This procedure describes how to upgrade the PostgreSQL database server to the latest supported version. After you have upgraded Control-M/EM or Control-M/Server, the PostgreSQL database server version remains the same. If you want to use version 9.0.21.100 you must upgrade the PostgreSQL database server.
-
After you have upgraded the dedicated PostgreSQL database server to PostgreSQL 11, you can no longer downgrade Control-M/EM or Control-M/Server to a version below 9.0.21.100.
-
In a Full installation environment, perform this procedure one time. The Control-M/EM and Control-M/Server PostgreSQL databases are upgraded together.
Before You Begin:
-
Verify that there is enough disk space to contain an additional PostgreSQL database server. The free space must be greater than the size of the <Control-M_Home>\pgsql directory including an additional 25%. The upgrade checks if there is enough space and it fails if it is not enough. For example, if the size of the pgsql directory is 1 GB, the upgrade requires at least 1.25 GB of free space.
-
Upgrade Control-M/EM or Control-M/Server to version 9.0.21.100.
-
Note that the upgrade requires down time of Control-M. The time for upgrade depends on the size of database. In most scenarios, the upgrade completes in 10 minutes. In a large scale environment it might take up to an hour.
Begin
-
Navigate to one of the following PostgreSQL server upgrade package locations:
UNIX: <cdPath>/Setup_files/TOOLS/pg_server_upgrade.tar.gz
Windows: <cdPath>\Setup_files\TOOLS\pg_server_upgrade.zip
-
Copy the package to one of the following locations:
-
Full Installation and Control-M/Server on UNIX: $HOME
-
Control-M/Server on UNIX: $HOME
-
Control-M/EM on UNIX: $HOME/ctm_em/
-
Full Installation on Windows: <Control-M Home>\Control-M Server
-
Control-M/Server on Windows: <Control-M Home>\Control-M Server
-
Control-M/EM on Windows: <Control-M Home>\Control-M EM 9.0.00\Default
-
-
Do one of the following:
-
UNIX: Type the following commands to open and uncompress:
-
gunzip pg_server_upgrade.tar.gz
-
tar -xvf pg_server_upgrade.tar.gz
-
-
Windows: Extract the pg_server_upgrade.zip.
-
-
Shut down Control-M/EM or Control-M/Server components (both for Full Install), and verify that the processes are down.
-
Verify that the PostgreSQL database server is up and online.
-
Navigate to the pg_server_upgrade directory and run one of the following commands:
-
UNIX: PG_Upgrade.sh
-
Windows: PG_Upgrade.bat
-
-
Follow the on-screen instructions until the upgrade is complete.
If you want to downgrade to the old PostgreSQL database server version, rename the the pgsql.old.<timestamp> directory to pgsql. The database server is reverted to the existing version before the upgrade. Any changes made to the new PostgreSQL server are not applied to the downgraded PostgreSQL server version.
Upgrading an External Oracle or MSSQL Database Server
This procedure describes how to upgrade an external Oracle or MSSQL database server after you have upgraded Control-M/EM or Control-M/Server.
Begin
-
Verify that the database server version is supported, as described in Product Availability & Compatibility.
-
Verify the database server requirements, as described in Database Server Requirements.
-
Contact your DBA to upgrade your database server.
-
If the connection properties have changed in the new database server, update Control-M/EM or Control-M/Server configuration to point to the new location, as described in Reconfiguring the Database Server Connection Data.
-
(Oracle only) You can upgrade Control-M to version 9.0.21.100 using Oracle 12c as an external database server, but you must upgrade your external database server to a supported version before you start up Control-M components.
-
Upgrading Control-M in a Disaster Recovery Configuration
This procedure describes how to upgrade Control-M/EM and Control-M/Server in a Disaster Recovery configuration on UNIX and Windows. In a disaster recovery environment, the database in the recovery site is set to read-only, which enables replication from the primary site. This procedure allows you to upgrade without changing the read-only status of the database and without interrupting the database replication.
The database in the disaster recovery environment must have read access.
Begin
-
Set the inst_skip_db_changes environment variable to Y where the upgrade is executed.
-
Do one of the following:
To upgrade Control-M/EM, see Upgrading Control-M/EM on UNIX or Upgrading Control-M/EM on Windows.
To upgrade Control-M/Server, see Upgrading Control-M/Server on UNIX or Upgrading Control-M/Server on Windows.
-
Set the inst_skip_db_changes environment variable to N.