Atlas
— Initial Agent Schedule data instances
|
|
v6.1Your system includes eight standard agents rules (Rule-Agent-Queue rule type). When Process Commander is first started on a node, agent schedule data instances (Data-Agent-Queue class) are generated automatically from the agents rules. You cannot update the standard agents rules, but you can override or adjust their configuration settings through the generated agent schedules.
With the exception of the agents listed in the
Pega-ProCom agents rule, do not enable standard legacy
agents (those created before version 5.4) on more than one node. If your
have multi-node Process Commander cluster, configure the generated agent
schedules so that the agents listed in the Pega-RULES agents
rule and the three legacy agents listed in the Pega-IntSvcs
agents rule run on one node only.
Agent Schedule |
Purpose |
| Pega-AutoTest.<node ID > | The agents in the Pega-AutoTest agents rule support Automated Unit Testing. See Understanding the Pega-AutoTest agents. |
| Pega-ImportExport.<node ID > | The agents in the Pega-ImportExport agents rule support the Purge/Archive wizard and support certain one-time post-upgrade processing. See Understanding the Pega-ImportExport agents. |
| Pega-IntSvcs.<node ID > | The agents in the Pega-IntSvcs agents rule process queued service requests and perform maintenance for PegaDISTRIBUTION MANAGER (formerly called Correspondence Output Server, or COS). See Understanding the Pega-IntSvcs agents. |
| Pega-ProcessEngine.<node ID > | The agent in the Pega-ProcessEngine agents rule supports calculations defined in case type rules. See Understanding the Pega-ProcessEngine agent. |
| Pega-ProCom.<node ID > |
The agents in the Pega-ProCom agents rule process email, service level rules, and assignments, and so on. See Understanding the Pega-ProCom agents. |
| Pega-RuleRefactoring.<node ID > | The agent in the Pega-RuleRefactoring agents rule supports the RuleSet Maintenance wizard for queued tasks such as copying, moving, merging, and renaming RuleSets. See Understanding the Pega-RuleRefactoring agent. |
| Pega-RULES.<node ID > | These agents perform general system housecleaning and periodic system pulse processing. See Understanding the Pega-RULES agents. |
| Pega-RulesEngine.<node ID > | The agent in the Pega-RulesEngine agents rule supports periodic maintenance of the rules assembly cache. See Understanding the Pega-RulesEngine agent. |
The second key part of an Agent Schedule data instance is the node ID, a hash value encoding the JVM, server hostname, and other facts.
|
agent, node id |
|
About Agent Schedule data instances
Agents — Concepts and terms |