The prconfig.xml file is a XML file that defines installation and operating parameters for a Process Commander node, including:

• Location of the PegaRULES database and other databases
• Timeout intervals
• Java compiler
• Reverse proxy server settings
• Whether features are enabled
• Directories used for indexes and temporary files

Consult Configuration Settings Reference, a document on the Pega Developer Network for more information on the contents and format of this file. (The 5.1 version of this document is named Prconfig.xml file Settings Reference.)

In a clustered system, a prconfig.xml file is present on each node.

Viewing the file

This file typically is placed in the WEB-INF/classes subdirectory of the application server directory. To view the prconfig.xml file for a node in your system:

1. Select Tools > System Management Application to start the System Management application. You may be prompted for authentication credentials.
2. Select a node.
3. Select the Configuration Management menu item.

Updates

Changes to this file may have dramatic effect on the operation and performance characteristics of your system. Make such changes only after careful planning and after review of documentation or consultation with Pegasystems support. Changes you make to this file take effect the next time you start the application server.

As a best practice, use an XML editor when changing the contents of this file. If no XML editor is available, use WordPad or a program editor rather than Windows Notepad.

As a best practice, use application server facilities to effect changes in this file:

1. Undeploy Process Commander.
2. Extract the current prconfig.xml file from the WAR file or EAR file.
3. Edit the file as required.
4. Repackage the WAR file or EAR file.
5. Redeploy with the application server facilities.
6. Restart the application server.

Notes

When Process Commander is deployed as an enterprise application, the prconfig.xml file is contained in a jar file /APP-INF/lib/prresources.jar.

In Process Commander releases before Version 5.1, an XML file named pegarules.xml served a similar function to the prconfig.xml file.

failover, keyring file, node, system ID, Tomcat, Virtual File interface

Definitions — P