Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Pega-RulesEngine agents

Updated on May 11, 2022

The agents support periodic maintenance of the system cache, event processing, the Property Optimization tool, and report statistics. In a multinode cluster, you can enable these agents on multiple nodes.

Purge Assembly Database Cache

The System-Cache-.Purge agent runs once a week on any node in the cluster and purges records from the database.

Scheduled Task Processor

The System-Queue-ScheduledTask.pzScheduledTaskProcessor agent processes instances of the System-Queue-ScheduledTask class to run scheduled reports.

Property Optimization

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. Click ConfigureSystemDatabaseColumn Population Jobs to see the status of jobs in this queue.

Report Statistics

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.

Update Active Non Quiesce Admin Requestors

The System-Status-Nodes.pyUpdateActiveUserCount activity runs every 5 seconds to count the number of non-quiesce administrators (general users) on a node.

This agent is particularly important for highly available systems that use Slow Drain mode as a quiesce strategy. Quiesce is complete in Slow Drain mode when all users (non-administrators) are removed from the system, while high availability administrator accounts are still operable in a quiesced system. For more information, see Quiesce using slow drain.

Delete Unused Static Content Files

To maximize performance, rules assembly in certain cases automatically creates aggregated static content containing CSS (Cascading Style Sheet) to support portal display and harness display. These aggregated static content records can be orphaned (never needed or used) by later processing. The System-Static-Content-.pzDeleteOrphanStaticContent activity deletes unused aggregated static content records to reduce clutter in the database table.

Disable Dormant Operators

The agent is disabled by default. If you enable the agent, it is configured to run once a day.

The Data-Admin-Operator-ID-.pzDisableDormantOperators activity is used to disable the operators in the system that are inactive for more than the number of days that are specified in the Number of days of inactivity text box in the Operator disablement policy section on the Security Policies landing page. To trigger the agent, at least one enabled operator must be specified in the Exclusion list of operator IDs section.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us