Control-M/Enterprise Manager Installation

The Control-M/EM installation includes the following components and features:

Control-M/EM server
Control-M/EM database
Control-M/Forecast
Control-M/Self-Service
Control-M SLA Management

If you have additional load balancing and geo-redundancy requirements, you can install multiple instances of Control-M/EM with its client and Control-M/Server components.

Before you install Control-M/EM, you must do the following:

Verify that your host meets the system requirements, as described in Control-M/EM System Requirements.
(UNIX only) Complete the pre-installation procedures, as described in Control-M/EM Pre-Installation Procedures on UNIX.

You can install Control-M/EM as follows:

Default: Installs Control-M/EM with a dedicated BMC-supplied PostgreSQL database server, default database name, default username, and default ports.
Custom: Installs Control-M/EM with your choice of an external database server, database name, username, and ports.
Distributed: Installs an additional Control-M/EM without a database server, but which is connected to a database server on another Control-M/EM. By default, there are no components defined in a Control-M/EM distributed machine, except for the Control-M/EM Configuration Agent.

The following procedures describe how to install Control-M/EM on UNIX and Windows:

Installing Control-M/EM on UNIX
Installing Control-M/EM on Windows
Installing a Control-M/EM Fix Pack on UNIX
Installing a Control-M/EM Fix Pack on Windows

Control-M/EM System Requirements

Before you install Control-M/EM, verify that your operating system, processor, and database server are supported and have the required amount of memory and disk space. For a full list of requirements, see the Control-M 9.0.02 Release Notes.

Verify that your system meets one of the following requirements:

Control-M/EM UNIX System Requirements
Control-M/EM Windows System Requirements

The number of processes limit must be equal to or greater than the number of expected parallel running jobs.

Control-M/EM UNIX System Requirements

The following table lists the prerequisite requirements for a UNIX platform. These values represent the minimum requirements for an entry level deployment. For higher capacity workloads, you must add resources.

Resource	Requirement
Compatible Processors	Linux: x86_64
CPU	4 vCPU: 100 SPEC rating (SPECint2006)
Memory	Depends on production environment size database type, as follows: Dedicated BMC-Supplied PostgreSQL Database: Small: 20 GB Medium: 36 GB Large: 64 GB For more information, see Control-M/EM Production Size.
Disk Space	Control-M/EM Host: Installation: 60 GB Upgrade: 12 GB (Optional) External Database Server Host: 10 GB BMC recommends 1.5 times more disk space than memory. A host with 24 GB of memory requires 36 GB of disk space.
Database	Database Server Requirements

Control-M/EM Windows System Requirements

The following table lists the prerequisite requirements for a Windows platform. These values represent the minimum requirements for an entry level deployment. For higher capacity workloads, you must add resources.

Resource	Requirement
Compatible Processors	x86_64
CPU	Intel Xeon 64-bit AMD Opteron 4 vCPU: 100 SPEC rating (SPECint2006)
Display	16-bit (65,536) colors or higher.
Memory	Depends on production environment size database type, as follows: Dedicated BMC-Supplied PostgreSQL Database: Small: 20 GB Medium: 32 GB Large: 64 GB For more information, see Control-M/EM Production Size.
Disk Space	Control-M/EM Host: Installation: 60 GB Upgrade: 12 GB (Optional) External Database Server Host: 10 GB BMC recommends 1.5 times more disk space than memory. A host with 24 GB of memory requires 36 GB of disk space.
Related Software	Google Chrome (version 78 or higher) or Microsoft Edge (version 80 or higher). Microsoft .NET Framework 4.7.2.
File System Permissions	The <Installation_Folder> must have Read, List Folder Contents, Write, and Read & Execute permissions assigned to the Users group.
Database	Database Server Requirements

Control-M/EM Production Size

The following table summarizes the criteria that determine production environment size categories.

Measurement	Small	Medium	Large
Active Jobs	0–40,000	35,000–300,000	280,000–600,000
Job Executions Each Day	0–40,000	35,000–300,000	280,000–600,000
Users	20–40	40–200	180–400

Control-M/EM Pre-Installation Procedures on UNIX

Before you install Control-M/EM, you must complete the following procedures:

Configuring a User Account on UNIX: Describes how to configure specific parameters for Control-M/EM.
Setting Environment Variables in UNIX: Describes how to set environment variables in UNIX, which enables you to see messages from the console.
Setting the Java Environment Variable: Describes how to set the Java environment variable, which points to an external Java installation.
Verifying Operating System Levels and Patches: Describes how to verify operating system level and patches with Control-M/EM requirements.
PostgreSQL UNIX Kernel Parameters: Describes how to modify AIX and Linux system parameters, which enables you to allocate resources for Control-M components.

Installing Control-M/EM on UNIX

This procedure describes how to install a Control-M/EM on UNIX. You can automatically or interactively install Control-M with its default settings or custom define its database server and name, along with the component usernames, hostnames, and port settings.

Before You Begin

Complete all Pre-installation Procedures.
Verify that you meet the system requirements, as described in Control-M/EM UNIX System Requirements.
Verify that an external Java package is installed, as described in External Java Installation.
Download the installation package, as described in Obtaining Control-M Installation Files.
(Cluster configurations only) Prepare the database server and data for a cluster installation, as described in Cluster Configuration.

Begin

Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory.
Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.
From your home directory, run the following command:

<source_path>/setup.sh
Do one of the following:
- Interactive Installation: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the installation is complete, as described in Installing Control-M/EM on UNIX (video).
- Automatic Installation: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
  1. Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.
  2. Click Generate and select the location to create the XML parameter file.
  3. Click Yes to quit the installation.
    
    A confirmation message appears.
  4. Click Yes.
  5. Copy the automatic installation parameters file to a network location that is accessible to all hosts where you want to perform an automatic installation.
  6. To run the installation script, run the following command:
    
    <source_path>/setup.sh -silent /app/CONTROLM-TMX/em-install.xml
    
    To encrypt a password in the installation, run the following command:
    
    <source_path>/Setup_files/components/em/setup.sh -encrypt <password>
    
    The installation log can be found at the following location:
    
    <$HOME>/BMCINSTALL/log/BMC_Control-M_Enterprise_Manager_<date-time>.log
    
    The backup file is available in the following location:
    
    $HOME/BMCINSTALL/uninstall/DRNFT.9.0.02/backup_area
Continue with Post-installation Procedures on UNIX.

Installing a Control-M/EM Fix Pack on UNIX

This procedure describes how to install a Control-M/EM fix pack on UNIX.

You must install the fix pack on every host where Control-M/EM server is installed.
In a High Availability environment, you must install this fix pack on active and non-active hosts.

Before You Begin

Ensure that you have already installed Fix Pack PAOST.9.0.22.100, as indicated in the <EM_Home>/installed_versions.txt file or (in a Control-M Full Installation) the <HOME>/installed_versions.txt file.
Verify that Control-M/EM 9.0.02 is installed before you install this fix pack.
Obtain Control-M installation files

Begin

Log in to the account where Control-M/EM is installed and copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to a temporary directory on your local hard drive (not a network drive), and then extract the package.
In a High Availability environment, stop the Control-M/EM Configuration Agent on the non-active environment to avoid automatic failover.
From the temporary directory, run the following command:

./install_patch.sh
Follow the on-screen instructions until the installation is complete.

The installation file shuts down the Control-M/EM components, installs the fix pack, and restarts the components.
In a High Availability environment, do the following:
1. Verify that the Control-M/EM Configuration Agent on the non-active environment is up after the installation completes.
2. Repeat the entire procedure on the non-active environment.

Installing Control-M/EM on Windows

This procedure describes how to install Control-M/EM on Windows. You can automatically or interactively install Control-M with its default settings or custom define its database server and name, along with the component usernames, hostnames, and port settings.

If Control-M/EM and Control-M/Server are installed on the same Windows host (including cluster), you must install each component on the same drive.
BMC recommends that you extract the installation files with a third-party extraction tool, such as WinZip, 7-Zip, or NanoZip, to avoid the 260-character extraction limit of the Windows built-in extraction utility.

Before You Begin

Verify that you meet the system requirements, as described in Control-M/EM Windows System Requirements.
Verify that an external Java package is installed, as described in External Java Installation.
Download the installation package, as described in Obtaining Control-M Installation Files.
(Cluster configurations only) Prepare the database server and data for a cluster installation, as described in Cluster Configuration.

Begin

Log in to the host 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 home directory.
From a command prompt window, run the following command:

<source_path>\setup.exe
Do one of the following:
- Interactive Installation: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the installation is complete.
- Automatic Installation: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
  1. Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.
  2. Click Generate and select the location to create the XML parameter file.
  3. Click Yes to quit the installation.
    
    A confirmation message appears.
  4. Click Yes.
  5. Copy the automatic installation parameters file to a network location that is accessible to all hosts where you want to perform an automatic installation.
  6. Log in using a user ID that has Administrator permissions on the current host.
  7. Run the following installation script:
    
    <source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>
    
    To encrypt a password in the installation, run the following command:
    
    <source_path>\Setup_files\components\em\setup.exe-encrypt <password>
    
    The installation log can be found at the following location:
    
    <installFolder>\BMCINSTALL\log\BMC_Control-M_Enterprise_Manager_<date-time>.log
    
    The backup file is available in the following location:
    
    <Install Directory>\BMCINSTALL\uninstall\DRNFT.9.0.02\backup_area

Installing a Control-M/EM Fix Pack on Windows

This procedure describes how to install a Control-M/EM fix pack on Windows.

You must install the fix pack on every host where Control-M/EM server is installed.
In a High Availability environment, you must install the fix pack on active and non-active hosts.

Before You Begin

Ensure that you have already installed Fix Pack PAOST.9.0.22.100, as indicated in the <EM_Home>\installed_versions.txt file or (in a Control-M Full Installation) the <HOME>\installed_versions.txt file.
Verify that Control-M/EM 9.0.02 is installed before you install this fix pack.
(Control-M cluster configurations only) From the Roles section in the Cluster Manager, shut down the following processes:
- Control-M-EM-CMS
- Control-M/EM Configuration Agent
- Control-M-EM-GCS
- Control-M-EM-GSR
- Kafka for Control-M/EM
- ZK for Control-M/EM
Obtain Control-M installation files

Begin

Log in to the account where Control-M/EM is installed and copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to a temporary directory on your local hard drive (not a network drive), and then extract the package.
In a High Availability environment, stop the Control-M/EM Configuration Agent on the non-active environment to avoid automatic failover.
From the temporary directory, run the following command:

./install_patch.bat
Follow the on-screen instructions until the installation is complete.

The installation file shuts down the Control-M/EM components, installs the fix pack, and restarts the components.
In a High Availability environment, do the following:
1. Verify that the Control-M/EM Configuration Agent on the non-active environment is up after the installation completes.
2. Repeat the entire procedure on the non-active environment.
(Control-M cluster configurations only) Do the following:
1. Restart Windows.
2. From the Roles section in the Cluster Manager, start up the following processes:
- Control-M-EM-CMS
- Control-M/EM Configuration Agent
- Control-M-EM-GCS
- Control-M-EM-GSR
- Kafka for Control-M/EM
- ZK for Control-M/EM

Changing the DBO Password

This procedure describes how to change the Oracle, MSSQL, or PostgreSQL database owner (DBO) password on UNIX and Windows. You must perform this procedure on all Control-M/EM installations (primary, secondary, and Control-M/EM Distributed) as they use the same database.

If High Availability is enabled, you must first perform this procedure on the primary Control-M/EM, and then on all other Control-M/EM servers. The first time that you perform this procedure on the primary, you must define the database administrator username and password.

Begin

Shut down all Control-M/EM components on all Control-M/EM installations including the Control-M/EM Configuration Agent (primary, secondary, and Control-M/EM Distributed).
On the primary host, run the following command:
- UNIX: <BMC_Install_Folder>/ctm_em/bin/change_em_database_owner_password.sh
- Windows: <BMC_Install_Folder>\Control-M EM\Default\bin\change_em_database_owner_password.bat
On the remaining hosts, run the following command:
- UNIX: <BMC_Install_Folder>/ctm_em/bin/change_em_database_owner_password.sh
- Windows: <BMC_Install_Folder>\Control-M EM\Default\bin\change_em_database_owner_password.bat

Uninstalling Control-M/EM from UNIX

This procedure describes how to uninstall Control-M/EM from UNIX.

If you are working in a Distributed environment, you must uninstall all Control-M/EM Distributed instances before you uninstall the Control-M/EM primary.
Automation API CLI is not included in 9.0.21.200 on Red Hat 8 and 9, CentOS 7, Amazon Linux 2, Suse 12.1, and Oracle Enterprise Linux 7. If you uninstall, Automation API CLI is not restored. It is not saved in the backup directory.

Before You Begin

Ensure that all jobs have completed execution.

Begin

Log in to the host where Control-M/EM is installed.
Navigate to the following directory:

<EM_Installation_Folder>/BMCINSTALL/uninstall/
Do one of the following:
- Interactively Uninstall: Run the following command:
  
  DRNFT.9.0.02/uninstall.sh
- Automatically Uninstall: Run the following command:
  
  DRNFT.9.0.02/uninstall.sh -silent
Control-M/EM is successfully removed from your host. If you performed a downgrade, Control-M components are up and running.

Uninstalling a Control-M/EM Fix Pack from UNIX

This procedure describes how to uninstall a Control-M/EM fix pack from UNIX.

In a High Availability environment, you must uninstall the fix pack from active and non-active hosts.

Begin

Log in to the account where Control-M/EM is installed.
In a High Availability environment, stop the Control-M/EM Configuration Agent on the non-active environment to avoid automatic failover.
Navigate to the following directory:

<EM_HOME>/patches/PANFT.9.0.21.000
Run the following command:

./uninstall_patch.sh

The uninstall file shuts down your Control-M/EM components, uninstalls the fix pack, and restarts the components.
In a High Availability environment, run the following command on the non-active environment:

./uninstall_patch.sh

The uninstall file shuts down your Control-M/EM components, uninstalls the fix pack, and restarts the components.
Verify that the Control-M/EM Configuration Agent on the non-active environment is up after the installation completes.

Uninstalling Control-M/EM from Windows

This procedure describes how to uninstall Control-M/EM from Windows.

If you are working in a Distributed environment, you must uninstall all Control-M/EM Distributed instances before you uninstall the Control-M/EM primary.

Before You Begin

Ensure that all jobs have completed execution.

Begin

From the Start menu, select Control Panel.
Double-click or Programs and Features.
Select Control-M/Enterprise Manager 9.0.02 and click Uninstall.
Click OK to continue.

Control-M/EM is successfully removed from your host. If you performed a downgrade, Control-M components are up and running.

Uninstalling a Control-M/EM Fix Pack from Windows

This procedure describes how to uninstall a Control-M/EM fix pack from Windows.

In a High Availability environment, you must uninstall the fix pack from active and non-active hosts.

Before You Begin

(Control-M cluster configurations only) From the Roles section in the Cluster Manager, shut down the following processes:
- Control-M-EM-CMS
- Control-M/EM Configuration Agent
- Control-M-EM-GCS
- Control-M-EM-GSR
- Kafka for Control-M/EM
- ZK for Control-M/EM

Begin

Log in to the account where Control-M/EM is installed.
In a High Availability environment, stop the Control-M/EM Configuration Agent on the non-active environment to avoid automatic failover.
Navigate to the following directory:

<EM_Home>\patches\PANFT.9.0.21.000
Run the following command:

uninstall_patch.bat

The uninstall file shuts down your Control-M/EM components, uninstalls the fix pack, and restarts the components.
In a High Availability environment, run the following command on the non-active environment:

uninstall_patch.bat

The uninstall file shuts down your Control-M/EM components, uninstalls the fix pack, and restarts the components.
(Control-M cluster configurations only) From the Roles section in the Cluster Manager, start up the following processes:
- Control-M-EM-CMS
- Control-M/EM Configuration Agent
- Control-M-EM-GCS
- Control-M-EM-GSR
- Kafka for Control-M/EM
- ZK for Control-M/EM
Verify that the Control-M/EM Configuration Agent on the non-active environment is up after the uninstallation completes.

Performing an Automatic Control-M/EM Uninstall on Windows

This procedure describes how to uninstall Control-M/EM from Windows via an automatic uninstall.

Before You Begin

Ensure that all jobs have completed execution.

Begin

Log in to the host where Control-M/EM is installed with a username that has Administrator permissions.
Navigate to the following directory:

<em_InstallFolder>\BMCINSTALL\uninstall\DRNFT.9.0.02
Run the following command:

Uninstall.exe -silent

Control-M/EM is successfully removed from your host.