Hi Saroj,
For Control M to access the BODI jobs, we need to install Control M agent in the BODI application server (for e.g if the application server name is ABC), and also ensure that the Control M services are running (Tracker and Listener), on the Control M desktop define the node ID as ABC and on the general tab, specify the path where the batch files are installed.
Hope this works.
Thanks
Himanshu
Accessing BODI from Control-M
I suppose you have succefully installed Control-M Server and Control-M Agent and you have tested the comunication between these components ("ctmping -nodeid ABC" from server or "ag_ping" from agent). Once you have defined the job, specifying the owner the command line the machine name (nodeid) using the Control-M Desktop utility, you must export the job defintion on the Control-M Server using the write and upload functions.
If you have succefully performed the previous steps you can now open the Control-M EM gui and order/force the job on the scheduling plan.
Note that by default the Control-M Agent on windows machine use the "local system account" to run the job. So what ever account (owner) you define on the job the batch script will be run by the "local system account". In order to specify the "log on as user" mode i suggest you to read the documentation.
Bye
If you have succefully performed the previous steps you can now open the Control-M EM gui and order/force the job on the scheduling plan.
Note that by default the Control-M Agent on windows machine use the "local system account" to run the job. So what ever account (owner) you define on the job the batch script will be run by the "local system account". In order to specify the "log on as user" mode i suggest you to read the documentation.
Bye