Managing high availability environment variable settings

There are multiple ways to set and manage Pega Platform settings. Following are recommended methods listed in terms of precedence:

Data-Admin-System-Settings (DASS) instances for each cluster
Java Naming and Directory Interface (JNDI) settings for a cluster
Individual prconfig.xml files for each Pega Platform server

Note: Organizations might have specific preferences that differ from the order listed above.

Using DASS instances

Based on the environment setup, administrators should use Data-Admin-System-Settings (DASS) instances for updating cluster-wide settings or for dynamic control of high availability settings. In cases that require finer Pega Platform server control and where restarts are acceptable, administrators should use JNDI or prconfig settings for high availability-specific settings.

Note: Some settings might require a system restart, even if they are configured using DASS instances.

Using JNDI settings

Administrators can use a shared prconfig.xml location by specifying the file URL using JNDI. This can be used for clusters and for Pega Platform server groups.

Individual Pega Platform servers can set specific settings directly using JNDI. See the specific Installation and Upgrade guides for your database and application server for details on how to set Pega Platform settings using JNDI.

Using prconfig files

To make the high availability settings page available and allow the DASS instances to be updated from high availability landing pages, all DASS instances in the cluster must have the following prconfig.xml setting:

<env name="initialization/settingsource" value="merged" />