Agent Installation
The Agent installation installs Control-M/Agent
If you are installing an Agent on UNIX, complete the pre-installation procedures, as described in Agent Pre-installation Procedures for UNIX and the post-installation 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 Control-M/Agent, verify that your operating system and processor are supported and that your minimum requirements for memory and diskspace are met. Verify that your system meets the following requirements:
You can install multiple Agents (including Control-M/Agent and Helix Control-M/Agent together) on the same host, but the following requirements must be met:
-
(UNIX only) Each Agent must be installed on a separate account.
-
Each Agent must have a unique name.
-
Each Agent or Helix Agent must be version 9.0.21.100 or higher.
To install a self-hosted Agent on a self-hosted Control-M/Server, see one of the following procedures:
-
If you use a proxy server to connect to the Internet, verify that the proxy server settings are defined, as described in Proxy Server Configuration.
-
If Application Pack 9.0.21.000 or lower is installed and you want to upgrade to Control-M/Agent 9.0.22, you must upgrade Application Pack to 9.0.21.100 or uninstall Application Pack, and then upgrade the Agent to 9.0.22.
-
If you upgrade the Agent, the Application Integrator version that is contained in the Application Pack installation is also upgraded. 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 finished executing before you upgrade the Agent.
-
If you have defined 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 version of Java that is higher than 11 and with an Application Pack version lower than 9.0.21, you might encounter issues with Application Pack plug-ins. To ensure that Application Pack functions properly, BMC recommends that you do one of the following:
-
Configure the Agent to use Java version 11 or lower.
-
Upgrade Application Pack to version 9.0.21 or higher.
-
-
Security troubleshooting and best practices are described in Control-M/Agent Security Updates for UNIX and Windows.
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 |
CPU and Memory |
100 concurrent jobs or less:
|
100–200 concurrent jobs:
|
|
Disk Space |
1,150 MB BMC Software recommends that you reserve three times the amount of RAM in the system for swap space. |
Agent System Requirements for UNIX
The following table lists the prerequisite requirements for Agent on a UNIX 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:
|
500–1,000 concurrent jobs:
|
|
Disk Space |
1,150 MB BMC Software recommends that you reserve three times the amount of RAM in the system for swap space. |
Control-M/Agent and Plug-ins Java Support
From version 9.0.21.000, Java library deliveries are decoupled from Control-M and not part of the installation. You must ensure that Java is available on the Control-M component host machines.
-
Control-M Application pack, Control-M for Airflow, Control-M for SAP version 9.0.21.000 cannot be installed on Control-M/Agent 9.0.21.100 or higher with Java 17 or higher.
-
You can use Java 21.0.0 with Control-M Application pack, Control-M for Airflow, Control-M for SAP version 9.0.21.200 only if Control-M/Agent is 9.0.21.300 or higher.
-
You can use Java 17.0.1 or 21.0.0 with Control-M for OEBS and Control-M for PeopleSoft version 9.0.21.000 only if Control-M/Agent is 9.0.21.300 or higher.
The following table lists the supported versions of Java for Control-M/Agent and Control-M plug-ins.
Component |
Previous Version |
9.0.20.200 |
9.0.21.000 |
9.0.21.100 |
9.0.21.200 |
9.0.21.300 |
---|---|---|---|---|---|---|
Control-M/Agent |
11.0.5 |
11.0.5 |
11.0.12 or higher |
|
|
|
Airflow |
|
|
11.0.12 or higher |
|
|
|
SAP |
(9.0.01) 1.8 |
|
11.0.12 or higher |
|
|
|
Application Pack |
11 |
|
11.0.12 or higher |
|
|
|
Application Integrator |
See Application Pack |
See Application Pack |
See Control-M/Agent |
See Control-M/Agent |
See Control-M/Agent |
See Control-M/Agent |
Databases |
See Application Pack |
See Application Pack |
See Application Pack |
See Application Pack |
|
|
Informatica |
See Application Pack |
See Application Pack |
See Application Pack |
See Application Pack |
|
|
Backup |
See Application Pack |
See Application Pack |
See Application Pack |
See Application Pack |
|
|
Hadoop |
See Application Pack |
See Application Pack |
See Application Pack |
See Application Pack |
|
|
PeopleSoft |
(9.0.01) 1.8 |
|
11 |
|
|
|
OEBS |
(9.0.01) 1.8 |
|
11 |
|
|
|
WJM |
(9.0.00) 1.8 |
|
|
|
|
|
DataStage |
(8.0.00) 1.6 |
|
|
|
|
|
Cognos |
(7.0.00) 1.6 |
|
|
|
|
|