Control-M/Enterprise Manager installation
If you have additional load balancing and geo-redundancy requirements, you can install multiple instances of Control-M/EM with client and server components.
Before you install Control-M/EM, verify the requirements, as described in Control-M/EM system requirements.
If you are installing Control-M/EM on UNIX, complete the pre-install procedures, as described in Control-M/EM pre-installation procedures on UNIX.
You can install Control-M/EM with one of the following options:
- Default: Installs Control-M/EM with a dedicated PostgreSQL database server, default database name, default username and default ports.
- Custom: Enables you to select a database server, database name, username and ports.
- Distributed: Installs an additional Control-M/EM without a database server. This Control-M/EM is connected to a database server on another Control-M/EM. By default, there are no components defined in a Control-M/EM distributed, except for the Control-M/EM Configuration Agent.
NOTE:
- After you have installed, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
- If you are installing Control-M/EM and Control-M/Server on the same computer or installing multiple instances of Control-M/EM on the same computer (UNIX only), you must configure the Zookeeper and Kafka services to use different ports on Control-M/Server and on the additional Control-M/EM instances, as described in KA 000225564.
The following procedures describe how to install Control-M/EM on UNIX and Windows: