Control-M presentation

Control-M is a scheduler (the best on the market) .

CONTROL-M/EM architectural structure

client components

The primary client components include:
— CONTROL-M Configuration Manager GUI—the main CONTROL-M
administrator interface to CONTROL-M/EM, CONTROL-M/Server and
CONTROL-M/Agent. It provides a single point of control for administering the
CONTROL-M environment and enables you to manage many of your
CONTROL-M administrative tasks from a central location.


— CONTROL-M/Desktop—GUI interface used by end-users for modeling the
production environment (defining jobs).

— CONTROL-M/EM GUI—GUI interface used by end-users and administrators
for monitoring the production environment and intervening when necessary.

— CONTROL-M Reporting facility—facility and GUI used by end-users and
administrators for generating useful reports of many types.

— Command line utilities—Many functions that are available through the GUIs
are also available through the use of interactive and batch utilities.

■

CONTROL-M/EM server components

— GUI Server—provides information to, and handles user requests issued
through, the CONTROL-M/Enterprise Manager window.

— Gateway—interface that handles communication between CONTROL-M/EM
and CONTROL-M/Server. A different gateway is dedicated to each
CONTROL-M/Server. The gateway is defined when the CONTROL-M/Server
is defined. CONTROL-M/EM and CONTROL-M for z/OS also interface
through a gateway.

— Configuration Management Server (CMS)—interfaces with the configuration
agents of CONTROL-M/Server and CONTROL-M for z/OS to provide
information to, and handle administrator requests issued through, the
CONTROL-M Configuration Manager.

— Global Alerts server (GAS) —manages alerts to CONTROL-M/EM GUIs
— Global Conditions server (GCS)—distributes global conditions to different
CONTROL-Ms.

— Batch Impact Manager (BIM) server—monitors critical batch services when your
site uses the BMC Batch Impact Manager add-on.

— Forecast server—helps you predict job patterns in order to forecast schedules for
running jobs in the future, when your site uses the CONTROL-M/Forecast
add-on.

CONTROL-M/Server and Agent components

■
infrastructure components
These components include:
— CONTROL-M/EM Configuration Agent—interface between
CONTROL-M/EM Configuration Manager Server and other CONTROL-M/EM
servers that provides CONTROL-M/EM server information to, and handles
administrator requests issued through, the CONTROL-M Configuration
Manager.

— CONTROL-M/EM database (Oracle, Sybase, MSSQL, or PostgreSQL) where
CONTROL-M/EM data resides

— CORBA-based naming services, which enables the client to locate the server to
which it must connect. For more information, see Appendix A, “Configuring
CORBA components.”

— CONTROL-M Web Server, used for deploying CONTROL-M client components
on client computers.


CONTROL-M/Server and Agent architectural structure

CONTROL-M/Server

Heart of the CONTROL-M family of products, CONTROL-M/Server submits jobs

for execution on Agent or remote host computers, monitors the jobs and performs

post-processing analysis, after which it may perform post-processing actions. The

completion status of jobs and the results of post-processing analysis are

transmitted to CONTROL-M/Enterprise Manager.

Agent computers

An agent computer is one on which CONTROL-M/Agent has been installed.

CONTROL-M/Agent submits jobs for execution, monitors the jobs, and performs

post-processing analysis of output files. The completion status of jobs and the

results of post-processing analysis are transmitted back to CONTROL-M/Server.

CONTROL-M/Agent can submit jobs to a remote host for execution.

Remote host computers

Agentless computer on which jobs can run. Each remote host is identified by its

node ID.

Control Modules

Control Modules (CMs) enable CONTROL-M/Agents to interface with the

external applications (for example SAP and Oracle E-Business Suite).

Infrastructure components

These components include:

— CONTROL-M/Server Configuration Agent —interfaces with

CONTROL-M/EM Configuration Manager Server to provide

CONTROL-M/Server information to, and handle administrator requests issued

through, the CONTROL-M Configuration Manager.

— CONTROL-M/Server database (Oracle, Sybase, MSSQL, or PostgreSQL)—

repository of CONTROL-M/Server data. One database exists for each

CONTROL-M/Server, which maintains the database by using a dedicated or

shared SQL server.