CONTROL-M/Agents:

CONTROL-M/Agents are commonly used to place computers under the control of a CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the CONTROL-M/Server, track the jobs’ processing, and provide status information back to the CONTROL-M/Server.

As an alternative to having a dedicated CONTROL-M/Agent installed on each computer under the control of a CONTROL-M/Server, CONTROL-M/Server can also submit jobs to agentless computers known as Remote Hosts.

CONTROL-M/Agents and remote hosts are identified by their node IDs. Jobs are assigned to specific node IDs. You can balance processing loads by grouping a number of CONTROL-M/Agents together into a node group, and then assigning jobs to the node group, instead of to a specific CONTROL-M/Agent. The job will be processed on any agent in the group, according to the processing load at that particular moment.

Read more »

Control-M GUI's

GUI’s:

          The main 3 GUI’s are listed below.

ü  Control-M / EM

ü  Control-M Desktop

ü  Control-M Configuration Manager

Control-M / EM:

This is a GUI where we can view all the jobs which are running for today. The jobs which are active for today is called ‘Active Job File (AJF)’.

Control-M Desktop

Using this GUI you can make all permanent changes to scheduling tables and calendars. You can create new jobs, tables and calendars using Control-M desktop. The changes which you are performing through this will be permanently stored in control-M server database.

Control-M Configuration Manager

Through this GUI you can monitor all control-m components (Control-M server, agents, remote hosts… etc) health status. You can also implement additional security using this GUI. We can define agents, Remote Hosts through this GUI.  

Read more »

The Control-M Data Center

The Control-M/Data Center is the true core of the Control-M system. The Data Center is comprised of a Control-M/Server, Database and Control M/Agents.

The Control-M/Server

The Control-M/Server is the central component of the Data Center. It controls interaction with the Enterprise Manager, Control-M/Agents and the database backend. The Control-M/Server (CTM/SERVER) is the component that maintains the schedule, job definitions, calendars, resources and conditions. CTM SERVER is the only component that can load or order jobs.

The Database

The database serves as a backend data repository for Control-M (Sybase, PGSQL, Oracle or MS SQL server can be used). The CTM/SERVER has its own data-space within an Oracle instance. This data-space contains the Master versions of all of the job-related data: job-definitions, scheduling tables, resources, calendars active jobs tables and shout tables, to name a few. It also houses runtime specific data for the CTM/SERVER such as process flags, user access profiles and agent status.

The Database is critical to the operation of CTM/SERVER & Control-M. If the database is not available, Control-M will not operate.

The Control-M/Agent

The Control-M/Agent (CTM AGENT) is a small-footprint application that is installed on each target server for jobs, as well as the CTM SERVER. It runs as a service on Windows-based systems and has a “hook” into “inetd” on UNIX systems. It is dormant until a request comes from the CTM SERVER or until a job-related message needs to be sent to CTM SERVER.

Read more »

The Control-M Accessories

The Control-M “Accessories” are:

• Control-M/Enterprise Manager GUI (EM/GUI or ECS GUI)

• Gateways

• Global Alert Server (GAS)

• Global Condition Server (GCS)

It is important to understand what each of these components does and its place in the Control-M architecture.

GUI’s:

The main 3 GUI’s are listed below.

1. Control-M / EM GUI
2. Control-M Desktop
3. Control-M Configuration Manager

Gateways: These are used for communication between Control-M/EM and Control-M Server. If these gateways are down then Control-M/EM GUI won’t get any status updates from the Control-M Server.

Global Alert Server (GAS): GAS will contain all the alerts sent from jobs which are active in Control-M. You can connect to GAS using ‘Alert window’ and can view all the alerts. Usually operations will monitor these alerts and take appropriate actions.

Global Condition Server (GCS): GCS will keep track of all Prerequisite and Global conditions added by jobs which are in AJF. Once a condition added to GCS, control-M will satisfies the condition for all the waiting jobs.

Read more »

Control-M Components

CONTROL-M/Enterprise Manager (CONTROL-M/EM): This application provides a single, centralized point of access and control of your batch processing environment. Through EM we can connect to multiple control-m servers.

CONTROL-M/Servers: At the heart of CONTROL-M processing are CONTROL-M/Servers. These are the scheduling engines that schedule jobs, manage job processing flows, and provide notification of job flow status. Each CONTROL-M/Server is resident on a particular computer and is specific to its operating system.

CONTROL-M/Agents and Remote hosts: Though CONTROL-M/Servers are responsible for job scheduling and processing, they do not have to limit their activity to the computer on which they reside; they can schedule jobs on other computers that come under their control. CONTROL-M/Agents are commonly used to place computers under the control of a CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the CONTROL-M/Server, track the jobs’ processing, and provide status information back to the CONTROL-M/Server.

As an alternative to having a dedicated CONTROL-M/Agent installed on each computer under the control of a CONTROL-M/Server, CONTROL-M/Server can also submit jobs to agentless computers known as remote hosts.

CONTROL-M/Agents and remote hosts are identified by their node IDs. Jobs are assigned to specific node IDs.

You can balance processing loads by grouping a number of CONTROL-M/Agents together into a node group, and then assigning jobs to the node group, instead of to a specific CONTROL-M/Agent. The job will be processed on any agent in the group, according to the processing load at that particular moment. You can also submit a single job to all the nodes in a Node Group. This is all depends on the scenario.

Control Modules: To bring CONTROL-M functionality to your external, packaged application environment (for example SAP and Oracle E-Business Suite), CONTROL-M provides Control Modules (CMs) that enable CONTROL-M/Agents to interface with the external applications.

Read more »

Introduction to Control-M

Control-M is a software application product developed by a team of software engineers in Israel to provide enterprise-level job scheduling and management. According to BMC’s literature “CONTROL-M for Distributed Systems is a business integrated scheduling product that focuses on the production environment's business applications and platforms”. Simply put, Control-M is an application able to execute programs on many different types of servers, manage the timing of them and report the results to a central point.

Read more »

Welcome

Hi All,

Thanks for visiting my blog. Let me introduce my self. This is Mahendra Vakati, Working as a Control-M Scheduler. I'm having experience in Control-M Operations, Scheduling and Basic Administration knowledge.

I know its a demanding technology in the current IT trend. many of my friend used to ask me some questions in control-m. So, I just thought to share my knowledge on Control-M to others, the result is this blog.

Please let me know your Suggestions, Queries, and anything. Just drop a mail at Mahi@learnctm.com or Mahendra.ControlM@gmail.com

I'll post Important topics in Control-M, Interview tips and many more....

Hope this blog will helps you...

Thanks,
Mahendra

Read more »