Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Cannot redirect log files (WebSphere Application Server)



The system administrator cannot redirect the log files to a different location even after entering the values in the WebSphere Application Server JVM properties. Also, the Pega configuration files (prconfig.xml, prlogging.xml, and log4j.xml) are not created after the deployment and restart of the JVM.

Error Messages

Not Applicable

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment using WebSphere Application Server


There are three ways to tell Pega to look for configuration files (prconfig.xml, prlogging.xml, outside of the EAR and inside of the prresources.jar file.

Approach #1: URL resource references
  1. In the WebSpere Application Server Administrator Console, click Applications > Enterprise Applications > PRPC.
  2. Click Resource References.
    Notice a couple of optional URLs to control Pega resources. By default, they are all mapped to url/pega/none and PRPC ignores them.
  3. Use the following URLs:
    url/pegarules.config – points to configuration file (prconfig.xml)
    url/ – points to mbean properties file (
    url/pegarules.logging.configuration – points to logging setup (prlogging.xml)
  4. Each of these is repeated three times because EAR/e-tier deployment of Pega breaks the runtime into three parts:
    prweb.war (servlet container)
    EngineBMT (EJB container when using bean-managed transactions including browser-based interactins)
    EngineCMT (EJB and MDB services)
  5. Define URLs using full URL syntax, file:///path/path/file . . .

URL configuration General Properties
Approach #2, IBM WebSphere custom properties or JVM Generic Arguments

Pega uses the following Java command line arguments if they are specified:
  1. In WebSphere Application Server, specify the “-D” command line arguments in one of two ways:
    In the JVM definition, explicitly add –D arguments as Generic JVM properties
    Use JVM custom properties as shown below.
  2. In the following example, define the properties pega.logdir and pega.tmpdir, which are themselves referenced from the files prlogging.xml and prconfig.xml.
IBM WebSphere Application Server Application Server JVM properties

Approach #3, Specify Generic JVM argument or WebSphere Application Server JVM custom property

Override the Java default ‘home’ directory by specifying
Pega will look in the user.home directory for prlogging.xml, prconfig.xml, and

Published June 1, 2017 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us