Control-M Installation

Control-M installation includes all Control-M components and enables you to install a new installation on a clean computer or upgrade an existing installation. You can install or upgrade the latest version of Control-M components whether it's an annual or fix pack version from the same installation files. You do not need to install a base version and then apply fix packs. You can use the same installation files to install a new installation or upgrade an existing installation.

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

You can use the version 9.0.21 installation files to install Control-M on a clean account or upgrade an existing Control-M version to 9.0.21.

To upgrade an existing version of Control-M/EM server and clients, Control-M/Server, and Control-M/Agents, see Control-M Upgrade.

To install one or many Control-M components on a clean account, see one of the following options:

  • Control-M Full Installation: Enables you to install the Control-M package with all Control-M components including Application Plug-ins, and add-ons, (see Control-M Installation Terminology) on UNIX and Windows via an interactive or automatic installation. You can install with the default settings, or choose the custom installation to select the database server, database names, usernames, hostnames, and port settings.

  • Control-M/Enterprise Manager Installation: Enables you to install multiple instances of Control-M/Enterprise Manager (Control-M/EM).

  • Control-M/Server Installation: Enables you to install multiple instances of Control-M/Server.

  • Agent Installation: Enables you to install additional Control-M/Agents on different computers throughout your organization, which enables you to run jobs on multiple computers. This enhances performance and creates greater load balancing control.

  • Control-M Client Installation: Enables you to install additional Control-M clients on different computers throughout your organization, which enable multiple users in your organization to access Control-M.

  • Control-M Installation on a Cloud Environment: Enables you to install all Control-M components in a cloud environment. You can also install a secondary instance of Control-M full installation, Control-M/EM, and Control-M/Server for High Availability (see High Availability Installation).

If you are installing Control-M in a cluster environment, see Control-M Cluster Configuration.

Planning Your Installation

In Control-M, you have the option to install both Control-M/EM and Control-M/Server in one account for UNIX and Windows using the Full Install option or you can install Control-M/EM in one account and Control-M /Server in a different account. In addition, you can install each component on a separate computer in separate accounts. There are several advantages to install each component in a distributed configuration. These considerations are more relevant in a production environment then they are in a non-production environment. A distributed environment has benefits if you need to perform maintenance on a computer, OS kernel, or for backup/restore a PostgreSQL database. PostgreSQL in a Full install builds two databases on a single database server instance and when a backup or restore is performed, both Control-M/EM and Control-M/Server are impacted and must be down.

The Full install option is recommended in a testing environment or if you have limited resources and you need to install all Control-M components on one computer. Note all aspects of redundancy, availability, and the cost of ownership to meet those objectives.

The user that is used to install the base version must be the same user to install a fix pack. Consider this limitation before installing the base version.

Language Options

Support for East Asian languages (Simplified Chinese, Traditional Chinese, Japanese, and Korean) is provided for all installations at the database level.

When you create a Control-M database on an existing PostgreSQL or MSSQL database server, CJK settings are not inherited automatically from the database server. They must be defined during the installation.

When you create a Control-M database on an existing Oracle database server, CJK settings are inherited automatically from the database server.

For more information regarding language support, including CJK and databases, see Language and Customization.

Control-M Installation Terminology

The following table lists terms that are specific to the Control-M environment.

Term

Description

Control-M client

Provides the main interface to your real-time batch environment and consists of the following GUI applications:

  • Control-M Configuration Manager

  • Control-M

  • Control-M Reports

Control-M/Agent

Handles job execution and runs jobs on behalf of its requesting Control-M/Server, tracks the job processing, and sends status information back to the Control-M/Server.

Control-M Add-ons

The following Control-M Add-ons are automatically installed in a trial version, which enables you to use the Add-on functionality:

  • Batch Impact Manager

  • Control-M/Forecast

  • Control-M Self Service

  • Control-M Workload Change Manager

  • Control-M Workload Archiving

Control-M/EM

Controls and manages your production jobs. Control-M/EM provides a single, centralized point of access and control that enables you to view, monitor, manage, and intervene in batch flow processing across the entire enterprise. Control-M/EM on Windows includes the Control-M client.

Control-M/Server

Handles job scheduling and processing needs that can be used in the Control-M environment. You can install multiple instances of Control-M/Server and each is responsible for scheduling individual jobs, managing job processing flows, and notifying Control-M/EM of job statuses.

Trial Version

Installs a trial version of Control-M with all base and optional components including the following:

This version is intended for testing and evaluation, not for usage in a production environment. For production usage in the future, uninstall the trial version and then re-install a non-trial version.

  • Batch Impact Manager

  • Control-M/Forecast

  • Control-M Self Service

  • Control-M Workload Change Manager

  • Control-M Workload Archiving

Non-Trial Version

Install the following Control-M base components:

  • Control-M/Enterprise Manager

  • Control-M/Server

  • Control-M/Agent

  • Control-M for SAP

  • Control-M for Web Services, Java, and Messaging

  • Control-M for OEBS

  • Control-M for Informatica

  • Application Pack (Application Pack deployment)