ControlMServer

ControlMServer is a central server component of the ControlM automation platform that coordinates the execution and monitoring of automated workflows across multiple systems. It serves as the authoritative source for job definitions, schedules, and runtime state, and it negotiates work with remote agents and clients.

Architecturally, ControlMServer runs as a persistent service backed by a database. It exposes a RESTful API and a web user interface to create and manage jobs, dependencies, and schedules. Remote agents installed on target hosts poll the server to receive ready jobs and report status, enabling centralized control of distributed tasks. The server maintains a directed acyclic graph of job dependencies, enforces concurrency limits, and applies retry and alert policies.

Its features include: job definitions with parameterization, time-based and event-driven triggers, complex dependency graphs, retries and backoffs, SLA adherence, real-time monitoring, audit trails, and reporting. It supports multi-tenant use through role-based access control, and provides APIs and web hooks for integration with external systems and CI/CD pipelines.

ControlMServer can be deployed on-premises or in cloud environments. High availability is supported through clustering and failover configurations, while data at rest and in transit can be secured with encryption and TLS. Access is controlled via authentication, RBAC, and granular permissions to define who can view, modify, or execute workflows.

Users typically define end-to-end workflows that span databases, ETL tools, file systems, and cloud services, schedule them with calendars or event triggers, and monitor executions from the UI or via APIs. The platform emphasizes observability, reproducibility, and controlled rollout of changes through versioning and approvals.