Q1: Could you provide us some information about a solid concurrency setup so that we do not Max out on the Concurrent Tasks of an Agent
A1: Multiple taskagent configurations won’t necessarily reduce hitting the max number of concurrent tasks on any one taskagent configuration. If that is a common experience in your environment, double (super precise I know) the number of max concurrent tasks for all of the taskagent configurations.
Q2: Also is there a way to dedicate a special Task Agent for just Multi-Company processes, IC Processes, Global Scheduling etc…?
A2: Taskagents don’t do much beyond polling the appserver every X number of seconds for tasks that need to be processed–they don’t do processing itself. However, there is a way to dedicate one appserver process that handles background processing to only handle MC or Global Scheduling through the System Agent > Task Agent rules.
Q3: Also if you have 3 Task Agents configured and one reaches its concurrent limit; will the other one pick up the other pending tasks?
A3: The taskagents aren’t aware of each other beyond knowing if another taskagent has staked claim to a particular request. If taskagent1 hit the max number of concurrent tasks it wouldn’t stop staking claim to more tasks if the other taskagent configurations didn’t stake claim to them first. NOTE: When a taskagent has hit the max concurrent tasks, the task in the system agent will have a PENDING status in the Active tasks. One a task is completed, it will change the status of the PENDING status task to ACTIVE.
My next post will be about task agent rules and how they fit in with multiple taskagent configurations.