|
|
Working with the PegaRULES database
This topic describes miscellaneous PegaRULES database tables, including those with names that start with one of these values:
pr_log
|
pr_perf_stats | |
pr_license
|
pr_*usage*
|
|
pr4_rule_sysgen
|
Tables for Log- instancesEleven tables can store instances of Log- classes. The key to these instances contains a date and time in UTC format.
Table |
Description |
pr_changelog
|
Holds instances of the concrete classes derived from Log-System-. These record schema changes through the Property Optimization tool and the Modify Schema tab. See System category — Database page. |
pr_perf_stats
|
Holds instances of the Log-Usage class. See Analyzing System-wide usage with the Log-Usage table. |
pr_daily_usage pr_hourly_usage pr_license_parameterspr_usage_summary |
Support the License Compliance facility. See Working with the License Compliance facility. Select > System >Tools > Usage Metrics to report on the pr_usage_summary table. |
pr_log_reportstats
|
Holds instances of the Log-ReportStatistics class, containing statistics about each execution of a report definition. See Understanding the Pega-RulesEngine agents. |
pr4_log_rule_usage
|
Holds statistics collected during system shutdown about cumulative rule execution statistics. Associated with the Log-RuleUsage class. See Working with the shutdown rule usage facility. |
pr4_log_rule_usage_details
|
Corresponds to the Log-RuleUsage-Details class. Holds details of a daily snapshot of the Rules Assembly cache, which the system can scan later at the next system startup to pre-populate the Rules Assembly cache. See Working with the Rules Assembly cache. |
pr_log_dataaccessaudit
|
Corresponds to the Log-DataAccessAudit class. When configured in harnesses and flow actions, holds the details for each operator's use of those rules. See Flow Action form — Completing the Security tab. |
pr_log
|
Holds instances of concrete classes derived from the Log- base class, other than those in the above tables. |
The Pega-RULES agent normally runs the standard Code-.SystemCleaner activity once each day for housekeeping tasks, including purging older records (instances) from certain log tables. (Separately, the License Compliance facility includes built-in daily and end-of-period purging of Log- classes.)
These tables support miscellaneous capabilities.
Table |
Description |
pr_assembledclasses
|
Supports fast startup by saving assembled Java classes for applications in your system. See static assembler. |
pr_engineclasses
|
Contains foundation Java classes that are part of PRPC internals. Storing classes in the database facilitates startup and maintenance, and helps assure that each node in a cluster is using identical code. See CodeSet. |
pr_extract_time
|
Supports logging and dynamic selection of rows by Business Intelligence Exchange product. Not used unless BIX is installed. |
pr_file_store
|
Contains rows that index the /Common/StaticContent/ directories and file structure within the temporary file directory. These directories contain JavaScript and CSS files extract from rules (such as Rule-File-Text or Rule-HTML-Fragment rules) plus images (JPG, GIF, PNG) extracted from Rule-File-Binary rules. See static content. |
pr_portal_state
|
Contains saved instances of the Pega-Portal-Developer and Pega-Portal-User classes. |
pegaam_alert
|
Supports Autonomic Event Services. Not used unless AES is installed. |
pc_events
|
Contains instances of Pega-Event and Pega-Event-* classes. |
pr_cep_users_subscriptions
|
Contains business event subscriptions, instances of the Pega-CEP-Subscription class. |
pr_cep_eventslookup
|
Supports business event processing, with instances of the Pega-CEPEventsLookup class. |
pc_cep_events_repository
|
Contains instances of the Pega-Event-System-Action class. |
pr_cep_events_queue
|
System-Queue-Events |
|
Custom Fields, Log- base class, passivation, referencing rules, timeouts |
|
Atlas — Initial Database Table data instances
Atlas — Standard classes derived from the Log- base class |