Skip to main content

Changing node settings by modifying the prconfig.xml file

Suggest edit Updated on May 11, 2022

Although it is a best practice to change system configuration settings by modifying the dynamic system settings, you can also change individual node settings in on-premises environments by modifying system settings in the prconfig.xml file.

Before you begin: Caution: Changes to the prconfig.xml file can affect the operation and performance characteristics of your Pega Platform system. Make changes only after careful planning and after reviewing documentation or consulting with Pegasystems Pega Support.

Dynamic system settings can override prconfig.xml settings when your Pega Platform database is configured to retrieve its data using JNDI, and the prconfig.xml file for a given node has the following setting: <env name="initialization/settingsource" value="merged" />. See the appropriate deployment guide for your system for information on configuring JNDI in the context.xml file.

Edit the prconfig file on the application server.

  1. Stop Pega Platform.
  2. Undeploy Pega Platform.
  3. Extract the current prconfig.xml file from the WAR file or EAR file.
  4. Edit the file as required.
    Entries are in the format <env name="ParameterName" value="ParameterValue" />, where ParameterName and ParameterValue are set to the appropriate values.
    For example: <env name="agent/enable" value="true" />
  5. Repackage the WAR file or EAR file.
  6. Redeploy Pega Platform with the application server facilities.
  7. Restart the application server to implement the changes to the prconfig.xml file.
Result: Changes that are made to this file take effect the next time that the application server starts.
  • Previous topic Setting the outbound port for cluster communication
  • Next topic Downloading and viewing the prconfig.xml file for a specific node
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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