Server to Agent Communication

[nicke]

Hi all!

Does anyone know what the underlying technique is for the communication between Control-M/Server and Agent? As we all know it is the Agent Listener process (p_ctmag) that listens for connections from the Control-M/Server and it is a tcp/ip based communication on tcp port, in our case 9006. And then there is the Protocol Communication version that you need to set for the Agent for example 07 or 08. But what is the technique behind it? For example the EM GUI uses Corba through tcp to communicate with Enterprise Manager Server but what is Server and Agents using?? Does anybody know or is it a BMC secret because I can't find any information about it anywhere. I would need to know this for explaining to our IT-architects when we are setting up Control-M Agents in the DMZ.

Thanks!

[nicke]

My Spanish is not that good Could you not explain in English?? Otherwise take it in Spanish and I try to run it through babelfish Any answers that gives some lights in this would be highly appreciated.

Thanks!!

[philmalmaison]

ConfigurationAgent of the control-m server tcp 2369 by default for the control-m server and it's agents
Configuration Server of the control-m server tcp 2370 by default for the control-m server and control-m em

regards
philmalmaison

[nicke]

Thank you But I wonder if anybody knows more about what the underlying technology is between the Control-M/Server and the Control-M/Agents??? We know that it is tcp/ip based communication on tcp ports but what is the underlying technology? Does anybody know

[philmalmaison]

what do you mean by underlying technology ?
the communications ports are used by host (statically or dynamically)
having timeout parameters, the satics ones are "listen" by the necessary host ...

what do you really want to know ?

regards
philmalmaison

[nicke]

If possible I would like to know what really happens when p_ctmag gets initiated to run a job from the Control-M/Server? It listens on tcp port but with what technology does the Control-M Server use to communicate with p_ctmag?

As you all know you can see that if you check with netstat command that the Agent gets the communication initiated from the Server on the tcp port during the run of the jobs and then it is released but how is the communication handled more than tcp?

For example EM Server uses Corba technology to communicate with EM Clients.

But I have not found what underlying technology Server uses to Agents. Does anyone know

Thanks

[philmalmaison]

the technology is the following :
SU Supervisor
TR Tracker
SL Selector and submitter
NS Communication with Agent computers
CO Communication gateway
CD New Day procedure, downloads, updates to CONTROL-M/Server database
CS CONTROL-M/EM user requests
LG Utilities invoked from Agent computers
WD Watchdog process
RT Inter-process Communication Router

NS is in charge of agents communication

regards
philmalmaison

[nicke]

Thanks ! I know about the NS daemon (p_ctmns) and it's check and communication with the Agents but do you know more about how it is communcating with the Agents? More than it is tcp? What is the technology? It is at least not Corba I guess. Maybe it is a BMC secret...

[mauriziog]

What is the technology

technology?
Is a client-server comunication, build with a program.
The laguage of the program can be java, .net, C++ using the TCP/IP protocol and so develop objects that use that protocol features.

[maheshvenu]

Kindly let me know how the following process communicate with each other

SU Supervisor
TR Tracker
SL Selector and submitter
NS Communication with Agent computers
CO Communication gateway
CD New Day procedure, downloads, updates to CONTROL-M/Server database
CS CONTROL-M/EM user requests
LG Utilities invoked from Agent computers
WD Watchdog process
RT Inter-process Communication Router
NS is in charge of agents communication

Also explain abt how this process are related to create a newday process