Back Forward Atlas — Initial Dynamic System Setting data instances

About Dynamic System Setting data instances

As your Process Commander system operates, these and other dynamic system settings instances may be created as needed. Consult the PDNConfiguration Settings Reference, a document on the Pega Developer Network, for additional details on specific Dynamic System Settings instances (Data-Admin-System-Settings class).

Name

Purpose

Pega-ProCom.
ProComHelpURI
Identifies the property containing the root URI of this Application Developer Help system. Determined during installation.
Pega-ProCom.
PublicLinkURL

Edit to identify a URL for directed Web access, such as

http://mysystem:8081/prweb/PRServlet

See How to provide external assignments through directed Web access.

Pega-ProCom.
SystemManagementURI
Identifies the root URI of the System Management application. Established during installation.
Pega-ProCom.
WorkHistoryVersion
When set to 5.1, indicates that a one-time upgrade activity for Version 4.2 work object history instances has completed successfully. The upgrade is not necessary on systems that contain no Version 4.2 work object history instances.
Pega-RULES.
compiler/defaultClasses
Supports Service Java rules and other handcrafted Java code. A list of Java classes that are added to the compile-time classpath for the compiler used to compile the generated Java. This allows service activities to call such classes. In Version 4, this setting was stored in the pegarules.xml file.
Pega-RULES.
compiler/defaultPaths
Supports Service Java rules and other handcrafted Java code. A list of jar files that are added to the compile-time classpath for the compiler used to compile the generated Java. This allows service activities to call the classes in external JAR files. See the Pega Developer Network article PDNPRKB-20931 About the Process Commander class paths.In Version 4, similar settings were stored in the pegarules.xml file.
Pega-RULES.
indexing/dataEnabled
Controls whether data instance indexing is enabled. See Understanding the Find Content Search facility.
Pega-RULES.
indexing/hostname
In a multinode cluster, identifies the internal node name (a hash value) of the node that supports Lucene-based indexing. See Understanding the Find Content Search facility.
Pega-RULES.
indexing/ruleEnabled
Controls whether rule instance indexing is enabled. See Understanding the Find Content Search facility.
Pega-RULES.
indexing/updatetime
Records the date and time of the last comprehensive index build. See Understanding the Find Content Search facility.
Pega-RULES.
indexing/workEnabled
Controls whether work object indexing is enabled. See Understanding the Find Content Search facility.
Pega-RULES.
SearchSoapURI
In a multinode cluster, records the URI to be used in SOAP-based communications among nodes to support Advanced Search.
Pega-RULES.
usage/usagetrackingenabled
Enables or disables usage tracking. Initial value is true. See How to analyze system-wide usage with the Log-Usage class.

zzz About System Setting data instances
Up Atlas — Initial Data Instances