High availability settings management
There are multiple ways to set and manage Pega Platform settings. Following are recommended methods listed in terms of precedence:
- Dynamic system settings for each cluster
- Java Naming and Directory Interface (JNDI) settings for a cluster
prconfig.xmlfiles for each Pega Platform server
Using dynamic system settings
Based on the environment setup, administrators should use dynamic system settings 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.
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.xml files
To make the high availability settings page available and allow the dynamic system setting
instances to be updated from high availability landing pages, all nodes in the cluster must
have the following
<env name="initialization/settingsource" value="merged" />