GUI Server (GSR)

Handles communication between Control-M/EM clients and Control-M/Servers. You can configure multiple GUI Servers in one Control-M/EM environment for load balancing purposes.

The GUI Server connects to each Gateway to transmit requests and receive responses to/from Control-M/Server.

Global Conditions Server (GCS)

Identifies and distributes global conditions used to create job dependencies between Control-M/Servers.

The GCS connects to each Gateway to receive and transmit prerequisite conditions to the appropriate Control-M/Server.

Gateway

Handles communication between the Control-M/EM servers (GUI Server and GCS), to the Control-M/Server.

A different gateway is defined for each Control-M/Server (including Control-M for z/OS).

Configuration Manager Server (CMS)

Receives information from the configuration agents of Control-M/Server and Control-M for z/OS, and handles requests from Control-M Configuration Manager client.

SLA Manager

Monitors critical batch services when your site uses the Control-M SLA Manager Add-on.

Forecast Server

Helps you simulate job patterns to validate the schedules for running jobs on a future date. This is supported when your site uses the Control-M/Forecast Add-on.

Self Service Server

Monitors Self Service services when your site uses the Control-M Self Service Add-on.

Web Server

Provides access for the following applications using HTTP/S protocol:

• Control-M client
• Control-M Web
• Control-M Configuration Manager
• Control-M Reports
• Control-M/EM API
• Automation API

Services

Services are a set of the following services, which expose shared functionality to various Control-M/EM applications and enable you to control and monitor them in the CCM or in the services-cli utilily:

• Services Configuration Agent
• Apache Kafka
• Apache Zookeeper
• Services Health Monitor
• Protocol Translator
• Validation Service
• Reports Service
• Scheduling Service

For a detailed description of each service, see Services.