Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a dynamic system setting

Updated on August 25, 2021

Add a dynamic system settings rule to change default system behavior.

For example, by default, encryption and authentication are not enabled for communication among search nodes. To enable encryption, create the indexing/distributed/enable_inter_node_encryption dynamic system setting and set it to true.
  1. In the header of Dev Studio, click CreateSysAdminDynamic System Settings.
  2. Enter a short description.
  3. Enter the Owning Ruleset.
    For example: Pega-RULES
    If no ruleset is associated with the data instance, when the data instance is saved, the system assigns a ruleset from the current application, which assists with application packaging.
  4. In the Setting Purpose field, enter the name of the setting.
    For example: indexing/distributed/enable_inter_node_encryption, where the key structure has the following components:
    • File type – Specifies the kind of setting for the instance.
      • prconfig – Used for prconfig.xml settings.
      • properties – Used for settings.
      • blank (no value entered) – Used for unspecified Data-Admin-System-Settings.
    • Setting name – Specifies the name of the setting and can include long strings that are divided by slashes or periods.
    • Node classification – Specifies the node classification for the instance. For prconfig.xml settings, use default. For example, the prconfig.xml setting asyncservices/enable as a dynamic system setting is prconfig/asyncservices/enable/default.
  5. Click Create and open.
  6. In the Value field, enter the value for the setting.
    For example:
    • true for a Boolean value
    • 100 timeout value
  7. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us