Use the Dev Studio, dynamic system settings rules, and properties files and scripts, to set system-wide parameters. The specific tool depends on your situation.
- System-wide parameters
- To specify system-wide parameters, use system data instances. System data instances are occurrences of your Pega Platform. See Specifying system-wide security parameters by using system data instances.
- Cluster-wide parameters that differ from site to site
- To set cluster-wide parameters when the values differ from site to site, such as with URLs, user names, or port numbers, and when they might be set programmatically use dynamic system settings. See Configuring dynamic system settings.
- For example, you can use a dynamic system settings to configure which fields are available in full-text search. Dynamic system settings are stored in the Pega Platform database and are used by all nodes that share that database.
- Individual node settings
- To apply changes to only some nodes in a system, change settings in the
prconfig.xmlfile. Settings in the
prconfig.xmlfile apply to the node on which the
prconfig.xmlfile resides. See Changing node settings by modifying the prconfig.xml file.
Note: This is only for on-premises environments.
- Production-level-specific run-time parameters
- To set production-level-specific parameters, use data transforms and other rule types. Run-time application settings can differ based on a system's production level, and are further resolved at run time through rule resolution. See Configuring production-level run-time settings.
The rule and data instances listed below have similar names, but they are not related.
- Application settings rules (Rule-Admin-System-Settings rule type) – Use application settings rules to hold important constant values in your application that are the same in every deployed copy of your application, that can differ by production level, and are rule-resolved.
- Dynamic system settings data instances (Data-Admin-System-Settings) – Use dynamic system settings when the values differ from site to site, such as with URLs, user names, or port numbers, and when they might be set programmatically.
- Setting rules (Rule-Access-Setting rule type) – Use setting rules in role-based access control when defining access roles and permissions.
- Configuring high availability deployments
Highly available systems are accessible with minimal or no downtime, despite hardware failure, process crashes due to insufficient resources, memory leaks, maintenance, application upgrade activities, or natural disasters. Pega Platform provides tools to meet high level production service level agreements for mission critical applications with high availability features.
- Configuring system settings
To configure your system, use the Dev Studio Configure System Settings menu.
- Configuring production-level run-time settings
Application settings rules define run-time settings that can differ based on a system's production level, and which are resolved at run time through rule resolution. Application settings are identified by name and owning ruleset. The owning ruleset functions as a namespace and does not have to equal the ruleset that contains the rule.
- Configuring dynamic system settings
As a best practice, set system configuration settings by using dynamic system settings data instances. For example, you can use a dynamic system settings to configure which fields are available in full-text search. Dynamic system settings are stored in the Pega Platform database and are used by all nodes that share that database.
- Managing rules
Pega Platform includes various utilities to streamline system management activities.
- Classifying nodes
Node classification is the process of separating nodes by purpose, predefining their behavior by assigning node types. When you associate a work resource with a specific node type,you optimize work performance in your Pega application.
- Setting application-specific configuration settings with configuration definitions and configuration bundles
Use configuration definitions and configuration bundles to set application-specific configuration parameter values to store historical configuration information or to port the configuration definitions and values to other instances of the application.