Control-M/Enterprise Manager Installation

Control-M/EM installation includes Control-M/EM Server and database and Control-M/EM client components (Windows only). In addition, Control-M SLA Management, Control-M/Forecast, and Control-M/Self Service are included with this installation.

Control-M SLA Management requires additional resources to run. BMC recommends that you run Control-M SLA Management on a Control-M/EM Distributed instance.

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

Before you install Control-M/EM, verify the requirements, as described in Control-M/EM System Requirements.

If you are installing Control-M/EM on UNIX, complete the pre-install procedures, as described in Control-M/EM Pre-Installation Procedures on UNIX.

You can install Control-M/EM with one of the following options:

Default: Installs Control-M/EM with a dedicated PostgreSQL database server, default database name, default username, and default ports.
Custom: Enables you to select a database server, database name, username, and ports.
Distributed: Installs an additional Control-M/EM without a database server. This Control-M/EM 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.

If you install Control-M/EM and Control-M/Server on the same computer, or multiple instances of Control-M/EM on the same computer (UNIX only), you must configure the Zookeeper and Kafka services to use different ports on Control-M/Server and on the additional Control-M/EM instances, as described in KA 000374213.

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

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 correct amount of memory and disk space. For a full list of requirements, see the Control-M 9.0.21.100 Release Notes.

Depending on your operating system, 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, add resources.

Resource	Specification	Requirement
Compatible Processors	AIX	IBM RISC System/6000 Bash shell
Compatible Processors	Linux	x86_64
Memory	N/A	16 GB
Disk Space	N/A	60 GB Upgrade: 7 GB If you are installing Control-M with a remote database server, 10 GB are required on the database server. BMC Software recommends that you reserve 1.5 times the amount of host memory in disk swap space. For example, a host with 24 GB of memory would require 36 GB of disk space.
CPU	4 VCPU	100 SPEC rating (2006_int_rate)

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, add resources.

Resource	Requirement
CPU	Intel Xeon 64-bit AMD Opteron
Compatible Processors	x86_64
Display	16-bit (65,536) colors or higher.
Memory	16 GB
Disk Space	60 GB Upgrade: 7 GB If you are installing Control-M with a remote database server, 10 GB are required on the database server. BMC Software recommends that you reserve 1.5 times the amount of host memory in disk swap space. For example, a host with 24 GB of memory would require 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.
CPU	4 VCPU 100 SPEC rating (2006_int_rate) The <install folder> must have Read, List Folder Contents, Write, and Read & Execute permissions assigned to the Users group.

Control-M/EM Pre-Installation Procedures on UNIX

Before you install Control-M/EM, you need to 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 Control-M/EM on UNIX. You can install with the default settings, or choose the custom installation to select the database server, database names, usernames, hostnames, and port settings. 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.

You need to install the Control-M client on a Windows computer.
The default installation 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 installation or perform an automatic installation.

Before You Begin

Ensure that you have met the following requirements:

Verify that your operating system and database software is compatible with the current version of Control-M/EM, as described in Control-M/EM UNIX System Requirements
Successful completion of Control-M Pre-installation Procedures.
Verify that you have met Java requirements, as described in Control-M External Java Installation.
If you are installing on cluster environment, see Control-M/EM UNIX Cluster Configuration.
If you are running the Kafka service, a Bash shell must be installed before you install Control-M/EM.

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, type the following command:

<source_path>/setup.sh
Do one of the following:
- Interactive Install: 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 Install: 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 computers where you want to perform an automatic installation.
  6. To run the installation script, type the following command:
    
    <source_path>/setup.sh -silent /app/CONTROLM-TMX/em-install.xml
    
    If you want 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.21.200/backup_area
    
    If you are working in a clustered environment, you must run the following:
    
    -file “<EM_HOME>bin\ CTMUpadteCluster_V21.ps1” install EM
Continue with Control-M Post-installation Procedures on UNIX.

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.

Installing Control-M/EM on Windows

This procedure describes how to install Control-M/EM on Windows. You can install with the default settings, or choose the custom installation to select the database server, database names, usernames, hostnames, and port settings. 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.

Before You Begin

Ensure that your operating system and database software is compatible with the current 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 cluster environment, see Control-M/EM Windows Cluster Configuration.

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

<source_path>\setup.exe
Do one of the following:
- Interactive Install: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the installation is complete.
- Automatic Install: 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 computers where you want to perform an automatic installation.
  6. Log in using a user ID that has Administrator permissions on the current computer.
  7. Run the following installation script:
    
    <source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>
    
    If you want 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.21.200\backup_area
    - If you are working in a clustered environment, you must run the following:
      
      -file “<EM_HOME>bin\ CTMUpadteCluster_V21.ps1” install EM
      
      After you install, you must restart all cluster hosts.
    - By default, Control-M/EM and Control-M clients are configured to work with HTTP. To secure your environment, BMC recommends that you change your configuration to HTTPS, as described in Zone 1 SSL Configuration.

Changing the DBO Password

This procedure describes how to change the Oracle, MSSQL, or PostgreSQL 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 you are working in a High Availability environment, you must perform this procedure on the active Control-M/EM first and then on all other Control-M/EM servers. The first time you perform this procedure on the primary, you require 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).
Run one of the following on the primary host and then on all the other hosts:
- 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 7, 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 ended.

Begin

Log in as a Control-M/EM user.
Navigate to the following directory:

<EM_Install_Folder>/BMCINSTALL/uninstall/
Type one of the following commands:

Interactive Uninstall: DRNFT.9.0.21.000/uninstall.sh

Automatic Uninstall: DRNFT.9.0.21.000/uninstall.sh -silent

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

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

Begin

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

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

If you are working in a clustered environment, you must run the following:

-file “<EM_HOME>bin\ CTMUpadteCluster_V21.ps1” uninstall EM

After you uninstall, you must restart all cluster hosts.

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

Begin

Log into the computer using a user ID that has Administrator permissions.
Navigate to the following directory:

<em_InstallFolder>\BMCINSTALL\uninstall\DRNFT.9.0.21.000
Type the following command:

Uninstall.exe -silent

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