Atlas — Initial Agent Schedule data instances

Your system includes three 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 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-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-ProCom.<node ID >	The agents in the Pega-ProCom agents rule process e-mail, service level rules, and assignments, archive work objects, and so on. See Understanding the Pega-ProCom agents.
Pega-RULES.<node ID >	These agents perform general system housecleaning and periodic system pulse processing. See Understanding the Pega-RULES agents.

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.

Agents - Concepts and terms

About Agent Schedule data instances
Atlas — Initial Data Instances