You are here: System management > System management tools

  System Tools landing page menu

The following tools are available when you select Designer Studio> System :

Operations > System Management Application

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

Operations> Logs> Log Files

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.

Operations> Logs > Logging Level Settings

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

Release> Upgrade> Validate > Revalidate for References

Use on system upgraded from releases before PRPC Version 5.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.

Release> Upgrade> Validate > Validate > Revalidate and Save

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.

Release> Hotfix Manager

Starts Hotfix Manager to compare the inventory of rules and code currently installed on your system to the contents of available hotfixes. About Hotfix Manager.

Refactor> Rules > Rename a Class

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

Refactor> Rules > Delete a Class

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

Refactor> Rules > Search/Replace a String

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

Refactor> Rules > Refactor on Import

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.

Refactor> RuleSets > Copy/Move/Merge

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

Refactor> RuleSets > Delete a RuleSet

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

Refactor> RuleSets > Skim a RuleSet

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

Refactor> RuleSets > Rulebase Compare

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

Application> Distribution> Migrate Product

Starts the Product Migration wizard, to move RuleSets or a product .zip archive between two Pega 7 Platform systems.

Application> Distribution> Package

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.

Operations> Purge/Archive > Configuration...

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

Operations> Purge/Archive > Schedule Process...

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

Assembly> Extract Edge Server Files

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.

Assembly> Static Assembler

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

License > Usage Summary Report

See License Compliance Facility — Standard reports and charts.

License > Named Users Chart

See License Compliance Facility — Standard reports and charts.

License > Services Invocations Chart

See License Compliance Facility — Standard reports and charts.

License > Web Invocations Chart

See License Compliance Facility — Standard reports and charts.

License > Active Connections

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.

Assembly> Assembly Compilation Summary

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.

Assembly> Assemblies for RuleSet lists

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.

Performance > Active RuleSet lists The standard summary view Log-Usage.pyActiveRulesetListCount, shows total performance statistics (CPU, output bytes, database bytes read and written) for each of the 7 past days for each active RuleSet lists. Drill down for details. See How to analyze system-wide usage with the Log-Usage class.
System> Refractor>Classes > Class Dependencies The System-Cache-Dependency.pzClassDependencies report shows the number of dependencies of a class. Drill down to a list of dependencies.
System> Refractor> Rules > Rule Dependents The System-Cache-Dependency.pzImplsPerDep report shows the number of classes that depend on a rule. Drill down to see a list of dependencies.
Performance >My Performance Details The summary view rule Log-Usage.pzPerformanceDetailsSingleUser, which shows interaction data for your user for the past week. Rows are sorted by requestorID.. You can adjust both the Operator ID and time range selection criteria. Two levels of drill-down are available. See How to analyze system-wide usage with the Log-Usage class.

Tools — System

Designer Studio landing pages