About Agent
Schedule data instances
|
|
| Key | Schedule | Security | History | More |
An agent schedule instance (Data-Agent-Queue class) determines whether an agent runs and, for a multinode system, on which server nodes it runs. Agent schedules cannot be created manually. The Agent Manager master agent generates agent schedule instances from agents rules (Rule-Agent-Queue rule type).
The Agent Manager on your Process Commander system generate at least one agent schedule instance for each agents rule. In a multinode system, for each agents rule, the Agent Manager generates one agent schedule instance for each node. For example, if a clustered Process Commander system has five nodes, then there are five Pega-ProCom agent schedule instances generated from the Pega-ProCom agents rule.
When you need to modify the behavior of an agent listed in an agents rule in a locked RuleSet (any of the standard Process Commander agents rules, for example) you do so by editing one or more of the generated agent schedule instances.
By default, the Agent Manager checks for new or updated agents rule once every ten minutes. After you create an agents rule, the Agent Manager generates one Agent Schedule instance for each node running on your Process Commander system the next time it checks for new agents rules.
Note the following about
agent schedules and multi-node clustered systems:
The Nodes tab on an agents rule lists all the agent schedules generated for that rule. Therefore, the easiest way to access an agent schedule is to open the agents rule and locate the agent schedule on the Nodes tab. You can also use the Rules by Type explorer to list agent schedules: select SysAdmin > Agent Schedule.
The Data-Agent-Queue class holds agent schedule data instances. They are part of the SysAdmin category.
|
Agents
— Concepts and Terms
About Agents rules |
|
Atlas — Initial Agent Schedule data instances |
Home