About Agents rules
|
|
| New | Schedule | Security | Nodes | History | More |
An agents rule provides configuration information for the agents listed in the rule, including the trigger or wake-up interval or schedule, the activities the agents execute, and the way the agent queue is handled. Each agent in the list performs one task (sends generated correspondence or processes assignments, for example) by running its associated agent activity.
The name of an agents rule is the name of a RuleSet and there can be
only one agents rule defined for each RuleSet and version in a Process
Commander system. When the Agent Manager master agent notices a newly
added Agents rule (Rule-Agent-Queue), it generates agent
schedules (Data-Agent-Queue instances) for each node in your
Process Commander system. If you need to modify the configuration
settings for an agent from a locked RuleSet (any of the standard Process
Commander agents rules, for example), you do so by updating the generated
agent schedules. (See 
Pega Developer Network article
PRKB-25049 How to modify an agent.)
Although agent entries are listed and have numbers, the order in which you list agents in an agents rule does not create a sequence. Each agent activity runs individually on its own interval schedule, as a separate requestor thread. Do not design application logic that depends on agent activities running in a specific order.
Use the Rules Explorer to list all the agents rules that are available to you: select SysAdmin > Agents. The list includes the standard agents rules: Pega-AutoTest, Pega-ImportExport, Pega-IntSvcs, Pega-ProCom, Pega-ProcessEngine, Pega-RULES, Pega-RuleRefactoring, and Pega-RulesEngine. You create your own agents rules when you need application-specific background processing.
Agents rules are instances of the Rule-Agent-Queue class. They are part of the SysAdmin category.
In releases before V5.4, Agents rules were known as
Agent Queue rules.
|
Agents — Concepts and terms |
|
Atlas — Standard Agents |
SysAdmin category
Help Home