Installing Control-M/Agent on UNIX

This procedure describes how to install Control-M/Agent on a UNIX host. This installation includes Application Integrator and 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.

To install multiple instances of Control-M/Agent on several hosts with the same configuration, use the automatic installation, as described in this procedure.

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

  • Verify that your operating system is compatible with the current version of Control-M/Agent, as described in Agent System Requirements for UNIX.

  • Verify that you have completed the Agent Pre-installation Procedures for UNIX.

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

  • If you plan to use Automation API CLI, verify that Python version 3.8.4 or higher is installed.

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

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

  • (Red Hat 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

  • (Solaris only) As a root user, add the following line to the /etc/project file:

    project-name:project-id-number::username::rcap.max-rss=734003200

Begin

  1. Log in to the host.

  2. Download the installation files, as described in and move them to the home directory.

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

  4. From the home directory, type 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.SaaS/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.

By default, Control-M/Agent is configured to work with TCP. To secure your environment, BMC recommends to change your configuration to SSL, as described in Zone 2 and 3 SSL Configuration.