Skip to main content

 –

Understanding system settings for high availability environments

Suggest edit Updated on August 18, 2021

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
  • Individual prconfig.xml files for each Pega Platform server
Note: Your organization might have specific preferences that differ from the order listed above.

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.

Note: Some settings might require a system restart, even if they are configured using dynamic system 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 prconfig.xml setting:

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

    Did you find this content helpful? YesNo

    Have a question? Get answers now.

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

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us