The prlogging.xml file is a control file for the Process Commander logging facility, a modified version of the Apache log4j facility.

Entries in the prlogging.xml file follow the syntax of Apache log4j xml configuration entries. For example, the following settings cause INFO-level logging for every agent, activity, model, and when rule:

<category name="com.pega.pegarules.engine.context.Agent">
   <priority value="info"/>
</category>
<category name="Rule_Obj_Activity">
   <priority value="info"/>
</category>
<category name="Rule_Obj_Model">
   <priority value="info"/>
</category>
<category name="Rule_Obj_When">
   <priority value="info"/>
</category>

 

Changes

To change a logging level only temporarily, you do not need to update the file. Use the Logging Level Settings tool.

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

1. Undeploy Process Commander.
2. Extract the current prlogging.xml file from the prweb.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.

See also the Pega Developer Network article PRKB-10403 How to Customize the log4j.xml logging file.

Rolling the log files daily

By default, the date portion of the Pega log file name and Alert log file name indicates the date the application server was recently started on the node. You can update the prlogging.xml file to cause a new log file to be created at the start of each day, known as "rolling" the log file. For details, see the Administration and Security 5.3 publication.

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.

	alert log, appender, log4j
	About the Logging Level Settings tool

Definitions — P