Control-M/Server Services

Control-M/Server services are a set of micro services that are independent and can perform individual tasks without making requests from larger components. This enables your environment to use fewer resources and run more efficiently.

The following Control-M/Server services can be managed in the CCM:

• Services Configuration Agent: Functions as a watchdog process for all services, which is monitored by the Control-M/Server Configuration Agent. This service enables you to monitor and send commands for all services such as shutting down, starting up, ignoring services, viewing the status, and setting the log level.
• Apache Kafka: Open source for publish/subscribe data stream between different applications.
• Apache Zookeeper: Centralized service for distributed systems, which Apache Kafka uses to coordinator between Apache Kafka instances.
• Services Health Monitor: Produces health reports for all service statuses from life checks sent through Apache Kafka.
• Scheduling Service: Calculates the dates that match the scheduling criteria of a job or Smart folder. The View Schedule option sends a request to the Scheduling Service to receive the dates that match the scheduling criteria for the selected jobs or folders.

The Services Configuration Agent is a watchdog process for all services, which is monitored by the Control-M/Server Configuration Agent and responsible for starting all the services. When the Services Configuration Agent detects that if a service process is down but set to Up, the SCA starts it up and vice versa.

All services send life checks through Kafka. The Service Health Monitor monitors the life checks and produces a report with information of all services statuses. If the Service Health Monitor is not running, a message appears in the Control-M client, and services cannot be displayed.

The following diagram shows the Control-M/Server services architecture.