Scheduler Usage

Hi Everyone,

Can anyone explain about the Control-M/Agent. Why should we install Control-M Agent? Where it needs to be installed?

I'm new to Control-M

Thanks,
Gopi.

Could anyone please explain about this...

Your Control-M scheduler is on a SERVER. It schedules your jobs for that server. If you have a distributed system where you need to run jobs on other servers (clients) then you need an Agent on that server/client. It talks back and forth to the CTM-Server and keeps tracks of jobs run on that client. You can run "agentless", but you do not get some functions such as Advanced File Transfer. Also Agents offer more secure communications than agent-less.

Gopikkd wrote:Hi Everyone,

Can anyone explain about the Control-M/Agent. Why should we install Control-M Agent? Where it needs to be installed?

I'm new to Control-M

Thanks,
Gopi.

-------------------------------------------------------------------

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.

The server is the "mind" who decide the schedulation and send orders, agents act, are the "arms" of control-M scheduler.

Hi,
Control-M agent has below processes to complete job processing-
AG (Agent listener, Request handler) :Listens on TCP port for requests coming form server, Handles the requests also.
AT (Agent tracker): Tracks the job processing and post processing.
RT (Agent Router): IT is activated only if the persistent connection mode is used.
Listens request form server -> AT -> AG
UT (Utility Process): processes and submits utility requests from agent to Server.