Installing Control-M/Agent on UNIX/Linux

This procedure describes how to install Control-M/Agent on UNIX/Linux, which includes Application Integrator and Control-M Automation API CLI. If a previous version of Control-M/Agent is detected, the Agent is automatically upgraded and the previous version parameter values are saved. 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.

By default, Control-M components and connected user interfaces are configured to communicate via SSL in new Control-M 9.0.27 installations. BMC recommends that you upload your own signed, organization-managed, SSL/TLS certificate that supports Control-M security level 4 when prompted during installation.

If you install Control-M with a less secure, automatically generated self-signed SSL certificate that only supports Control-M security level 2 (and is valid for 20 years), BMC recommends that you later replace this self-signed certificate with a signed, organization-managed SSL/TLS certificate that supports security level 4, as described in the following procedures:

• Generating a Signed Certificate and Private Key

• Generating a PKCS #12 Keystore

• Replacing Default Self-Signed Certificates with User-Provided Certificates at Security Level 4.

Before You Begin

• Complete all Agent Pre-installation Procedures for UNIX/Linux.

• Verify that you meet the system requirements, as described in Agent System Requirements for UNIX.

• Verify that an external Java package is installed outside of the <Control-M/Agent_Home> directory, as described in External Java Installation.

• Verify that the Internal Process Communication (IPC) subsystem is enabled.

• Verify that your operating system locale is set to English.

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

• (Control-M Automation API CLI only) Verify the following:

  • Python 3.8.4 or higher and pip 20.1.1 or higher is installed.

  • Your system path includes the required Python executable pathname. Or, to use a different Python installation, point the CLI_INSTALL_PYTHON_EXE environment variable to the relevant Python installation.

  If you want to use Automation API CLI at a later time, you must install Python and pip, run the ctm command, and then follow the prompts.

• (RedHat Linux only) BMC recommends that you define the maxproc parameter to at least 4,096.

• (AIX only) run the following command to define the tcp_nodelayack parameter to 1:

  /usr/sbin/no -p -o tcp_nodelayack=1

Begin

1. Log in to the host.

2. Copy the installation files to the home directory.

3. Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX/Linux.

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

   <source_path>/setup.sh

5. Do one of the following:

   • Interactive Installation: Follow the on-screen instructions until the installation is complete.

   • Automatic Installation: Create a parameter file and then do the following:

     1. Follow the on-screen instructions until the Summary window appears.

     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. Run the following command:

        <Source_Path>/setup.sh -silent <xml_path>/<Filename.xml>

     To encrypt a password in the installation, run the following command:

     <Source_Path>/setup.sh -encrypt <Password>

     The installation log and backup file are available in the following directories:

     • Installation Log: <$HOME>/BMCINSTALL/log/BMC_Control-M_AGENT_Install<date-time>.log

     • Backup File: $HOME/BMCINSTALL/uninstall/DRKAI.9.0.27/backup_area

6. After Agent installation, jobs can run under the Agent user account only. To allow jobs to run under other Run As users, you must change the Agent mode, as described in set_agent_mode.

Installing Control-M/Agent on Linux with RPM

This procedure describes how to install Control-M/Agent on Linux with Red Hat Package Manager (RPM). You can only install one instance of Control-M/Agent on a Linux host with RPM because Control-M/Agent must be installed on the root user account.

Before You Begin

• Verify that one of the following operating systems are installed with x 86_64 architecture:

  • Amazon Linux

  • Oracle Linux

  • Red Hat

  • SuSE

  • AlmaLinux

• Verify that Java 17 or 21 for x 86_64 architecture is installed from a supported vendor, as described in Control-M Compatibility with External Java Vendors.

• Define a non-root user as an Agent owner, as described in Configuring a User Account on UNIX/Linux.

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

Begin

1. Log in to the host as the root user.

2. (Optional) To change the default Control-M/Server host and port settings, in the /tmp directory, create a controlm-agent.ini input file with parameters defined in the following format:

   <parameter name>=<parameter value>

   Copy

   CTMSHOST=localhost 
   CTMPERMHOSTS="localhost|host2" 
   ATCMNDATA=7005 
   AGCMNDATA=7006

   If you do not change a parameter value, it retains the default value, as described in this example.

   For parameter descriptions, see Configuring Agent System Parameters.

3. Run the following command:

   rpm -U <RPM_Package_Pathname>

   The following message appears:

   Execute the set_agent_mode script as root, enable non-root mode, and start the agent with the start-ag utility.

4. To enable jobs to run as other Run as Users, change the Agent mode, as described in set_agent_mode.

5. Start up the Agent, as described in Starting Up the Agent.

Installing Control-M/Agent on Debian or Ubuntu with the dpkg Package Manager

This procedure describes how to install Control-M/Agent for Debian or Ubuntu Linux with the dpkg package manager. You can only install one instance of Control-M/Agent on a Debian or Ubuntu Linux host because these operating systems require you to install Control-M/Agent on the root user account.

Before You Begin

• Verify that you have either Debian or Ubuntu operating systems for x 86_64 architecture installed.

• Verify that Java 17 or 21 for x 86_64 architecture is installed from either Ubuntu (Private Build) or Debian.

• Define a non-root user as an Agent owner, as described in Configuring a User Account on UNIX/Linux.

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

Begin

1. Log in to the host as the root user.

2. Save the downloaded installation package to a temporary directory.

3. (Optional) To change the default Control-M/Server host and port settings, in the /tmp directory, create a controlm-agent.ini input file with parameters defined in the following format:

   <parameter name>=<parameter value>

   Copy

   CTMSHOST=localhost 
   CTMPERMHOSTS="localhost|host2" 
   ATCMNDATA=7005 
   AGCMNDATA=7006

   If you do not change a parameter value, it retains the default value, as described in this example.

   For parameter descriptions, see Configuring Agent System Parameters.

3. Run the following command:

   dpkg -i <Debian_Package_Pathname>

   The following message appears:

   Execute the set_agent_mode script as root, enable non-root mode, and start the agent with the start-ag utility.

4. To enable jobs to run as other Run as Users, change the Agent mode, as described in set_agent_mode.

5. Start up the Agent, as described in Starting Up the Agent.