Understanding the
Pega-RulesEngine agents
Understanding the
|
|
The agent rule in the Pega-RulesEngine ruleset has five agents. In a multinode cluster, you can enable this agent on multiple nodes.
The Pega-RulesEngine agent is different from the Pega-Rules agent.
The System-Cache-.Purge agent runs twice a day (every twelve hours) and purges records from the Rules Assembly cache (on the current node).
The System-Queue-ScheduledTask.pzScheduledTaskProcessor agent processes instances of the System-Queue-ScheduledTask class to run scheduled reports.
The System-Job-PropertyOptimizationpyOptimization agent supports background processing to expose properties from the pzPVStream (BLOB) column. Queue entries are instances of the System-Queue-ColumnPopulation class.
Use the Property Optimization tool to expose a property as a separate column and specify that values for that column are populated automatically, The Property Optimization landing page tab on the System-Database landing page tracks the progress of this agent. Select Designer Studio> System > Database > Column Population Jobs to see the status of jobs in this queue.
To maximize performance, rules assembly in certain cases automatically creates text rules of type CSS (Cascading Style Sheet) to support portal display and harness display. These text file rules can be orphaned (never needed or used) by later processing. This activity deletes unused text file rules, to reduce rule count and clutter.
Once an hour, the Log-ReportStatistics.pzSaveReportStatUsage activity adds an instance to the Log-ReportStatistics class for each execution of a report definition. Each instance identifies the report definition and the date and time when the report ran. Standard reports are available to support reviewing these log instances. Enabled by default, the dynamic system setting reporting/enablestatistics controls this logging behavior.
