Is there a limit to the number of managers that can be configured for a single agent?
Article ID: 112049
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Workload Automation Agent
Issue/Introduction
Is there a limit to the number of managers that can be configured for a single agent?
Environment
Release:
Component: ATSYS
Component: ATSYS
Resolution
The agent does not have a limit for the number of configured managers. However, there are some things to consider when configuring an agent with multiple managers...
1. While there is no limit to the number of managers that can be configured, the agent does have its limits on how many jobs it can run concurrently. By default, it can run 1000 jobs at a time. However, it can also be constrained by java memory limits and system resource limits. This should be considered when scheduling from multiple managers so as to not overload a single agent.
2. The communication parameter tags for each manager must be unique. This is accomplished by using sequential numbers in the parameter tags. For example, if two managers on machine1 and machine2 are configured in the agentparm.txt file, the communication parameters should look something like this...
communication.manageraddress_1=machine1
communication.managerhealthmon_2=true
communication.managerid_3=DEV_SCH
communication.managerport_4=7507
communication.socket_5=plain
communication.manageraddress_2=machine2
communication.managerhealthmon_2=true
communication.managerid_2=DEV_SCH
communication.managerport_2=7507
communication.socket_2=plain
Notice machine 1's parameters all contain '1' at the end of the parameter name and machine2 's parameters all contain a '2'. If machine2's parameters also had a '1', only machine1's manager would successfully communicate with the agent since it is listed first.
1. While there is no limit to the number of managers that can be configured, the agent does have its limits on how many jobs it can run concurrently. By default, it can run 1000 jobs at a time. However, it can also be constrained by java memory limits and system resource limits. This should be considered when scheduling from multiple managers so as to not overload a single agent.
2. The communication parameter tags for each manager must be unique. This is accomplished by using sequential numbers in the parameter tags. For example, if two managers on machine1 and machine2 are configured in the agentparm.txt file, the communication parameters should look something like this...
communication.manageraddress_1=machine1
communication.managerhealthmon_2=true
communication.managerid_3=DEV_SCH
communication.managerport_4=7507
communication.socket_5=plain
communication.manageraddress_2=machine2
communication.managerhealthmon_2=true
communication.managerid_2=DEV_SCH
communication.managerport_2=7507
communication.socket_2=plain
Notice machine 1's parameters all contain '1' at the end of the parameter name and machine2 's parameters all contain a '2'. If machine2's parameters also had a '1', only machine1's manager would successfully communicate with the agent since it is listed first.
Feedback
Yes
No
Powered by
