Creating a Dynamic System Setting
You can 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.
- In the Dev Studio header, click .
-
On the Create form, enter values in the fields to define the Dynamic System Setting.
Options include:
-
In the Owning Ruleset field, 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.
-
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 prbootstrap.properties 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 settingasyncservices/enable
as a Dynamic System Setting isprconfig/asyncservices/enable/default
.
- File type – Specifies the kind of setting for the instance.
-
In the Owning Ruleset field, enter the owning ruleset, for
example, Pega-RULES.
- Click Create and open.
- In the Value field, enter the value for the setting. For example, true for a Boolean value, or 100 for timeout value.
- Click Save.