features of control-m

Ability to schedule cross-platform batch flow.

Allows real-time batch monitoring and management from a single point
of control.
Supports calendar-based scheduling and event-trigger scheduling. Meets
complex scheduling requirements.
Dynamically manages the execution of workload according to real-time CPU
resource utilization.
According to the predefined rules, to automatically perform actions when
a job execution event has occurred (for example, a job failed with a certain
return code, or the job didn't run at the expected time).
Allows batch execution history lookup.
Automatically generates an alert when a job fails or a predefined condition
is met.
Job version control and built-in change management facility.
Integration with ITSM and IT management software.
Ability to relate batch jobs to business services.
Forecasting capabilities for planning changes in the batch environment
Agentless technology was introduced in the release of Control-M 6.3.01. With thi
s
feature, users can run jobs on a remote host without preinstalling Control-M's a
gent
application. This feature allows rapid job deployment
you no longer need to wait
to
create a user account, allocate disk space, open firewall ports, install, and co
nfigure
agent application, and so on. This feature also allows Control-M job scheduling
on
operating systems that are not natively supported by Control-M agent application
,
such as CISCO OS, FreeBSD, SCO Unix, and so on.
Control-M job
In Control-M, each job represents one execution step of a batch flow. The job
definition records what to execute, to be executed under which user, on which
machine, on which day, under what conditions, required resources, how does it
run (run once or cyclic), the time frame (from/to time), job's time zone, under
what
conditions it runs, and the post-actions upon job's completion.
Control-M/Enterprise manager GUI front end has four components:
Control-M Enterprise Manager Client
Control-M Desktop
Control-M Configuration Manager
Reporting Facility
Control-M Enterprise Manager Client
Control-M Enterprise Manager GUI Client is the central point for graphical batch
monitoring and control. Within the GUI, active jobs that are running across the
IT environment can be presented in flow diagram according to the logical order
between them or in list format
Control-M Desktop

The Control-M Desktop is the user working space for defining and modifying
job definitions, working with job calendars, and viewing job forecasts (optional
component). It provides a uniformed job editing interface to define and modify j
ob
definitions regardless of what operating system it is going to be running on.
The jobs defined in Control-M Desktop can be saved in Control-M job draft format
(.drf) on the user's local computer. As version 6.4.01, Control-M Desktop allowe
d
job definitions to be saved in .xml format.
Since Control-M/Enterprise Manager 6.4.01 fix pack 1, Control-M Desktop added th
e
capability to handle Unix crontab job conversion user can directly import a cron
tab
file through Control-M Desktop.
Control-M Configuration Manager
Control-M Configuration Manager is the central place for managing Control-M
components within the batch environment.
Configuration Manager (CCM) added the ability to manage the scheduling engines
(Control-M/Server) and job execution hosts (Control-M/Agent), as well as many
other functions around the administration aspect.
Reporting Facility
The Reporting Facility is the key tool for extracting batch related informaiton
from Control-M and analyzing the batch environment therefore supporting
future decision making such as forcasing batch processing volume or planning on
optimising batch processing duration. It provides a user interface for generatin
g
reports against the data collected by Control-M/Enterprise Manager while the
system is running.
The report can be saved in the Crystal Reports format or exported into other
common formats. The available formats are: comma separated values (.csv), tab
separated values (.ttx), Acrobat (.pdf), Excel (.xls), Word (.doc), HTML 4.0
(.html), and XML (.xml).
(Control-M Control Modules), Control-M can automate special
job types such as file transfer, web services, messaging, java applications, as
well as
able to expand its schedule capability into major applications such as SAP, Orac
le
E-Business Suit, Informatica, and PeopleSoft.
additional modules
Control-M/Forecast
Control-M/Forecast does the hard job in the background by calculating the job's
statistical information that is collected by Control-M/Enterprise Manager during
batch job running.

BMC Batch Impact Manager

BMC Batch Impact Manager enables batch processing monitoring at the service
level.
Control-M Architecture and Components
Control-M is well known for its three-tier architecture. Control-M/Enterprise Ma
nager sits at the top layer
The middle tier Control-M/
Server is the schedule engine that performs the actual job submission and tracki
ng.
the bottom tier is Control-M/Agent that runs on different machines to handle
job submission requests from Control-M/Server.

Control Modules and Agentless

hosts are also part of the bottom layer, but just under Control-M/Agent
Agentless hosts are managed by Control-M/Server through
selected Control-M/Agent(s).
Control-M/Enterprise Manager:two sub layers:Control-M/Enterprise Manager GUI Client
Control-M/Enterprise Manager Server
Control-M/Enterprise Manager Server Components
Control-M/Enterprise Manager Server relies on database for storing information
such as, static job definitions, active job's execution information, historical
job
execution information, as well as information required for Batch Impact Manger
and Forecast
Control-M/Enterprise Manager Server components are a set of processes that play
different roles at the back end. These processes are:
Naming Services
Control-M Configuration Server
Control-M/Enterprise Manager Configuration Agent
GUI Server
Gateway process (GTW)
Global Condition Server (GCS)
Global Alert Server (GAS)
Control-M Web Server
Naming Service
The Naming Service provides the foundation for the majority of communications
between Control-M/Enterprise Manager components. It is in fact an embedded TAO
(The Ace Orb) naming service an open-source C++ implementation of CORBA

(Common Object Request Broker Architecture) protocol. It is a middleware in

between Control-M/Enterprise Manager components allowing the components to
communicate with each other over the network by using the same interface.
Control-M Configuration Server
Control-M Configuration Server component was introduced in Control-M/
Enterprise Manager 6.3.01 as a background service to support CCM GUI front-end
and perform backend administration tasks like cleaning hysterical data from the
database on regular intervals.