Agent Installation

The Agent installation installs Control-M/Agent, Application Integrator, and Automation API CLI. Additional Agents enable you to run jobs on multiple computers. This enhances performance and creates greater load balancing control.

If you are installing an Agent on Linux, complete the pre-install procedures, as described in Agent Pre-installation Procedures for Linux and the post install procedures, as described in Agent Post-installation Procedures.

Control-M/Agent requires an external Java library. To ensure that Java libraries remain updated, Java library deliveries are decoupled from Control-M/Agent and not part of the installation. For more information, see Control-M External Java Installation.

Before you install an Agent, verify that your operating system and processor are supported and that your minimum requirements for memory and diskspace are met. Depending on your operating system, verify that your system meets one of the following requirements:

You can install multiple Agents (including Agent and Helix Agent together) on the same host machine, but the following requirements must be met:

  • Each Agent must be installed on a separate account (Linux only).

  • Each Agent must have a unique name.

  • Each Agent or Helix Agent must be version 9.0.21.100 or higher.

  • Any plug-in that is installed on multiple Agents on the same Windows machine must be the same version.

The following procedures describe how install Control-M/Agent on UNIX and Windows.

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

  • If you have Control-M for Databases connection profiles, you cannot upgrade Application Pack to version 9.0.21.100 or higher until you have upgraded Control-M for Databases to version 9.0.21.100 or higher.

  • If you are using Agent 9.0.21.100 or higher with a Java version that is higher than 11 with Application Pack lower than version 9.0.21, you might encounter issues in Application Pack plug-ins. To ensure that Application Pack functions properly, BMC recommends to set the Agent to use Java version 11 or lower, or upgrade Application Pack to version 9.0.21 or higher.

Agent System Requirements for Windows

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

Resource

Specification

Compatible Processors

x86_64

For up-to-date information, see Control-M Compatibility for Version 9.0.21.

CPU and Memory

100 concurrent jobs or less: 

  • CPU: 2

  • Memory: 4 GB

  • CPU SPEC: 90

100–250 concurrent jobs:

  • CPU: 4

  • Memory: 6 GB

  • CPU SPEC: 180

Disk Space

BMC Software recommends that you reserve three times the amount of RAM in the system for swap space.

1,150 MB

Agent System Requirements for Linux

The following table lists the prerequisite requirements for Agent on a Linux platform. These values represent the minimum requirement for an entry level deployment. For higher capacity workloads, add resources.

Resource

Requirement

Hardware

For an up-to-date list of supported operating systems and requirements, see Control-M Compatibility for Version 9.0.21.

Memory

500 concurrent jobs or less:

  • CPU: 2

  • Memory: 4 GB

  • CPU SPEC: 90

500–1,000 concurrent jobs:

  • CPU: 4

  • Memory: 8 GB

  • CPU SPEC: 180

Disk Space

BMC Software recommends that you reserve three times the amount of RAM in the system for swap space.

1,150 MB