One system, multiple agents
One system, multiple agents
What do you think: is it possible to run multiple CTM agents on the same target system connected to the same CTM server?
The target system is AIX with RBAC. The idea behind this question is the possibility to run the agents under different userid with different roles. Thus the individual agents can be dedicated to the appropriate applications. The agent userid will have limited access rights, only those, which are necessary to run the application jobs.
Best regards,
Vince
The target system is AIX with RBAC. The idea behind this question is the possibility to run the agents under different userid with different roles. Thus the individual agents can be dedicated to the appropriate applications. The agent userid will have limited access rights, only those, which are necessary to run the application jobs.
Best regards,
Vince
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
Yes you can,
like the following on unix:
create a user for each agents you want to install on the same host
install them
create a link from the secondary agents to the first one
create a node group with all thoses agents
then
when you submit to the node_group using the node_group name, and not selecting the submit on all node in group definition parameter for the job, it will be submit using the first free agent for the process.
regards
philmalmaison
like the following on unix:
create a user for each agents you want to install on the same host
install them
create a link from the secondary agents to the first one
create a node group with all thoses agents
then
when you submit to the node_group using the node_group name, and not selecting the submit on all node in group definition parameter for the job, it will be submit using the first free agent for the process.
regards
philmalmaison
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
so what is your solution to be sure to have one concerned agent process free to dialog with it's controlm server ?
on some environment, as mine (Total group), you can have some datacenters on wich it's so much jobs to submit per day, that it's necessary to serialize by agent process for submission, to not have to recover blue jobs in AJF.
this kind of load balancing is used to.
i know that the new versions seems to be OK with that default number of jobs per day, but BMC could not ensure it as well.
regards
philmalmaison
on some environment, as mine (Total group), you can have some datacenters on wich it's so much jobs to submit per day, that it's necessary to serialize by agent process for submission, to not have to recover blue jobs in AJF.
this kind of load balancing is used to.
i know that the new versions seems to be OK with that default number of jobs per day, but BMC could not ensure it as well.
regards
philmalmaison
Thanks for the answer.
Some more points:
- the security policy wishes to minimize root users or tasks/jobs launched from root
- the approach is to restrict all access levels to the minimum
- RBAC is a good base for the above
mauriziog has the point: multiple agents with different access rights can serve different applications controlled by one single CTM server.
Some more points:
- the security policy wishes to minimize root users or tasks/jobs launched from root
- the approach is to restrict all access levels to the minimum
- RBAC is a good base for the above
mauriziog has the point: multiple agents with different access rights can serve different applications controlled by one single CTM server.
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
multiple agents - multiple servers?
Hi! I'm interested on running jobs from different servers to different agent on the seme host. Has anybody experienced this? thnks in advance!
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
Another approach was a request being made to me, to run the same jobflow on the same host. Conventions within prerequisite conditions, quantitative and control resources are using the first qualifier of the hostname.
We defined an alias (on UNIX) to the hostname, and installed a second Control-M agent with the alias name, and were able to duplicate the flow with small adaptions to the mentioned prerequisite conditions, quantitative and control resources.
This works fine.
We defined an alias (on UNIX) to the hostname, and installed a second Control-M agent with the alias name, and were able to duplicate the flow with small adaptions to the mentioned prerequisite conditions, quantitative and control resources.
This works fine.