System category — Tools menu

Starts the System Management application. Authentication may be required. About the System Management Application.

Lets you view the most recent Alert log or Pega log for the current node. With appropriate server configuration, you can download either the log to your workstation. About the Log Files tool.

Lets you temporarily override prlogging.xml settings for a category (Java class) as a debugging aid. About the Logging Level tool.

Use on system upgraded from releases before V5.3 only; not necessary otherwise. Lets you perform limited revalidation to improve the completeness and accuracy of Referencing Rules feature. See About the Referencing Rules display.

Starts the bulk revalidation tool, to check the validity of multiple rules (of one rule type) at once. This operation is similar to opening and saving each rule or data instance. About the bulk Revalidate and Save tool.

Starts the Hotfix Installation wizard to compare the inventory of rules and code currently installed on your system to the contents of selected hotfixes. About the Update Manager Hotfix Installer.

Starts the Update Manager System Scanner, which evaluates your system’s current inventory of rules, code, and hotfixes, comparing them with the latest hotfix catalog from Pegasystems. About the Update Manager System Scanner.

Lists the hotfixes applied to your PRC system but not yet committed. These hotfixes are active in the system but can still be rolled back. See System category — Update Manager landing page.

Lists the status of all hotfixes that have been applied to your PRPC system, committed and uncommitted. See System category — Update Manager landing page.

Adjusts all the rules that apply to a class so that they apply to a different, new class. About the Rename a Class wizard.

Deletes all the rules that apply to a class and the class itself. About the Delete a Class wizard.

Searches through all rules, or a subset of rules, and replaces one text string by another. See About the Search/Replace a String wizard.

Lets you rename the classes in a ZIP archive during import, to place the new rules in the appropriate position within the class hierarchy of this system. See About the Refactoring on Import wizard.

Starts the RuleSet Maintenance wizard, which allows you to rename, duplicate, or consolidate RuleSets and versions. About the RuleSet Maintenance wizard.

Starts the RuleSet Delete tool, which allows you to delete all rules in a RuleSet or RuleSet Version. About the RuleSet Delete tool.

Starts the Skim rules wizard, to copy the highest (major or minor) version of existing rules to a higher version. See Skim — definition and Help: Skim to a new Version.

Compares the individual rules in the current system with those in a target PRPC system, listing differences. See About the Rulebase Compare wizard.

Starts the Duplicate Properties wizard, which helps you find properties the same name in one inheritance change; these can impact performance.. See About the Duplicate Properties wizard.

Starts the Product Migration wizard, to move RuleSets or a product ZIP archive between two PRPC systems. See About the Product Migration wizard.

Starts the Package Work wizard, which allows you to create a product rule that contains work items, attachments, and work item history as well as rules. See About the Package Work wizard.

Two menu items support the Purge/Archive wizard, which can delete work items, attachments and history.

Starts the Purge/Archive configuration wizard to define work item purge or archive criteria. See About the Purge/Archive Configuration wizard.

Starts the Purge/Archive configuration wizard to schedule work item purging or archiving. See About the Purge/Archive Configuration wizard.

Create a ZIP archive of the text file rules and images in an application, for deployment on an edge server. See How to deploy static content to an edge server.

Opens the Static Assembler landing page, which lets you pre-assemble rules in an application. See System category — Static Assembler page.

Four menu options provide reports and charts about recent system usage, as captured by the License Compliance facility.

See License Compliance Facility — Standard reports and charts.

See License Compliance Facility — Standard reports and charts.

See License Compliance Facility — Standard reports and charts.

See License Compliance Facility — Standard reports and charts.

Lists active requestor sessions. Requestor IDs starting with H correspond to HTTP browser sessions; click a row to review the corresponding Operator ID.

Requestor IDs starting with the letter B identify BATCH requestor sessions, such as agents. Requestor IDs starting with A are for APP requestor sessions, such as listeners.

These six reports support performance analysis of your system. The My Performance Details report is easiest to interpret. The others require familiarity with rules assembly processing internals.

RuleSet lists are identified by the internal hexadecimal hash code.

The Log-Usage.pzAssemblyCompilationSummary report shows the number and time of rule assemblies and compilations, by node.  You can see whether there are a lot of assemblies that do not result in compilations. See also How to analyze system-wide usage with the Log-Usage class.

The System-Cache-Entry.pxMyAssemblies report shows the assemblies done for your RuleSet list hash in the past 24 hours.  It shows the rule and implementation key.  This can help determine whether recent slow performance is due to rules assemblies.