Atlas
— Initial Dynamic System Setting data instances
|
|
XXXXXXXXXXXXXXXXX REVISE FOR MANY NEW INITIAL V6.2 SETTINGS xxxxxxxxxxxx As your Process Commander system operates, these and other dynamic
system settings instances may be created as needed. Consult the
Configuration Settings Reference, a document on the
Pega Developer Network, for additional details on specific Dynamic System
Settings instances. COLLAPSE CANDIDATE
Dynamic system settings that have Pega-Engine as the Owning RuleSet and key names that start with prconfig are known as prconfig settings.
Change these settings with care. These settings can have broad impact on the operation of your system. See How to create or update a prconfig setting.
Name |
Purpose |
| Pega-Engine. prconfig/agent/enable/default |
Enables application agents. |
| Pega-Engine. prconfig/identification/ systemName/default |
Sets the name of the Data-Admin-System instance for the server. |
| Pega-Engine. prconfig/initialization/ displayExceptionTraceback/default |
Controls the display of stack trace information in exception screens. |
| Pega-Engine. prconfig/initialization/ explicitTempDir/default |
Specifies the full path name which to be used as the work directory. |
| Pega-Engine. prconfig/initialization/ persistRequestor/default |
Sets the conditions for the system saving a user's requestor context. |
| Pega-Engine. prconfig/initServices/initEmail/default |
Enables Email listeners on start up, as defined in Data-Admin-Connect-EmailListener |
| Pega-Engine. prconfig/initServices/initFile/default |
Enables file listeners on start up, as defined in Data-Admin-Connect-FileListener |
| Pega-Engine. prconfig/initServices/initJMS/default |
Enables JMS listeners on start up, as defined in Data-Admin-Connect-JMSListener |
| Pega-Engine. prconfig/initServices/initMQ/default |
Enables MQ listeners on start up, as defined in Data-Admin-Connect-MQListener |
| Pega-Engine. prconfig/pradapter/ loggingLevel/default |
Specifies the level of tracing for output to the system log. This setting overwrites the setting located in the JVM properties file. |
Name | Purpose |
| Pega-ProcessEngine. pyEmailMaxResends | xxxxxxxxx See More about Email Accounts. |
| Pega-ProCom. ProComHelpURI | Identifies the property containing
the root URI of this Application Developer Help system. Determined
during installation. MELLJ 4/12/06 As a best practice, select |
| Pega-ProCom. PublicLinkURL | Edit to identify a URL for directed Web access, such as http://mysystem:8081/prweb/PRServlet As a best practice, select |
| Pega-ProCom. pyUseGoalTimeFor AvailabilityCalculation | If true, the assignment's goal time is compared to the assignment's start time and effort estimate to determine operator availability. See Operator form — Completing the Work Settings tab. |
| Pega-ProCom. SystemManagementURI | Identifies the root URI of the System
Management application. Established during installation. MELLJ 4/12/06 As a best practice, select  > System > Settings > Resource URLs to create or update this data instance. See System category — Settings page. |
| 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. As a best practice, select . ISLAS 5/2006B-19195 In Version 4, this
setting was stored in the |
| Pega-RULES. compiler/defaultPaths | Supports Service Java rules and other
handcrafted Java code. B-19195 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. As a best practice, select ISLAS 5/2006 See the
Pega Developer Network article |
| Pega-RULES. indexing/dataEnabled | Controls whether data instance
indexing for full-text search is enabled. As a best practice, select |
| Pega-RULES. indexing/hostname | In a multinode cluster, identifies
the internal node name (a hash value) of the node that supports
Lucene-based full-text indexing. As a best practice, select > System > Settings > Search to create or update this data instance. See System category — Settings page |
| Pega-RULES. indexing/ruleEnabled | Controls whether rule instance
indexing is enabled. See As a best practice, select > System > Settings > Search to create or update this data instance. See System category — Settings page. |
| Pega-RULES. indexing/updatetime | Records the date and time of the last comprehensive index build. |
| Pega-RULES. indexing/workEnabled | Controls whether work object indexing
is enabled. See As a best practice, select > System > Settings > Search to create or update this data instance. See System category — Settings page.. B-21255 |
| Pega-RULES. SearchSoapURI | In a multinode cluster, records the
URI to be used in SOAP-based communications among nodes to support
full-text searches. Suprakash 11/29/06 B-25359 As a best practice, select > System > Settings > Search to create or update this data instance. See System category — Settings page. |
| 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. |
| Pega-RULESEngine pyMaxRecords | Maximum records retrieved for report definition rules. . XXXXXXXXXXX. See Reporting Category — Settings Page 6.2 |
| Pega-RULESEngine pyQueryTimeoutInterval | XXXXXXXXXXX. See Reporting Category — Settings Page 6.2 |
| Pega-RULESEngine pyExportMaxRecords | XXXXXXXXXXX. See Reporting Category — Settings Page 6.2 |
| Pega-RULESEngine pyExportQueryTimeout | XXXXXXXXXXX. See Reporting Category — Settings Page 6.2 |
About System Setting data instances Atlas — Initial
Data Instances