Dynamic System Settings

You can set or change system configuration settings by using Dynamic System Settings data instances. For example, you can use Dynamic System Settings to configure which fields are available in full-text search. Dynamic System Settings are stored in the PegaRULES database and are used by all nodes that share that database.

Dynamic System Settings and prconfig.xml file settings

Most system configuration settings in the prconfig.xml file can be stored in a Dynamic System Setting instance, which is the preferred method for maintaining system configuration settings. You might want to change settings in the prconfig.xml file when you only want the settings to apply to a subset of nodes. Settings in the prconfig.xml file apply to the node on which the prconfig.xml file resides.

Dynamic System Settings have the following advantages over using the prconfig.xml file:

  • You can change the value of Dynamic System Settings without redeploying the application. Editing the prconfig.xml file requires redeploying the application.
  • In a multi-node system, the same Dynamic System Settings can be used by all the nodes that are sharing the database, making system administration easier.

The rule and data instances listed below have similar names, but they are not related. Use System settings rules to hold important constant values in your application that are the same in every deployed copy of your application. 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.

  • System settings rules ( Rule-Admin-System-Settings rule type)
  • Dynamic Systems Settings data instances ( Data-Admin-System-Settings )
  • Setting rules ( Rule-Access-Setting rule type)