This procedure describes how to install Control-M/Agent on UNIX. If you want to install multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic installation, as described in this procedure.
NOTE: If a previous version of Control-M/Agent is detected, an upgrade is automatically performed and the parameters values from the previous version are used.
NOTE: 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:
From your home directory, type the following command:
<source_path>/setup.sh
Do one of the following:
Interactive install: Select the Control-M/Agent 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:
Select the Control-M/Agent option and continue with the on-screen instructions until the Summary window.
Click Generate and select the location to create the XML parameter file.
Click Yes to quit the installation.
A confirmation message appears.
Click Yes.
Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation.
To run the installation script, type the following command:
After you have installed Control-M/Agent, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
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. For information on how to do this, see set_agent_mode.
NOTE: 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.