Show
all
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-
instances
Nine tables can store instances of Log- classes. The
key to these instances contains a date and time in UTC format.
Table
|
Description
|
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_parameters
pr_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. PROJ-532 |
pr4_log_rule_usage
|
Holds statistics collected during system shutdown about
cumulative rule execution statistics. Associated with the
Log-RuleUsage class. C-2707 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. PROJ-454 |
pr_log_dataaccessaudit
|
Corresponds to the Log-DataAccessAudit class.
When configured in harness rules and flow action rules, holds
the details for each operator's use of those rules. See
Flow
Action form — Completing the Security tab. 5.5
GRP-245 |
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.)
Other tables
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. VAGUEV6.1 GRP-11968 |
pr_engineclasses
|
Contains foundation Java classes that are part of Process Commander internals. Storing classes in the database facilitates startup and maintenance, and helps assure that each node in a cluster is using identical code. See CodesSet. |
pr_extract_time
|
Supports logging and dynamic selection of rows by Business Intelligence Exchange product. |
pr_portal_state
|
Contains saved instances of the Pega-Portal-Developer and Pega-Portal-User classes. MORE |
pegaam_alert
|
Supports Autonomic Event Services. |
Working with the PegaRULES database