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

Externalization of config and prlogging XML fails

SA-14381

Summary



The url or pegarules.logging.configuration has been set to an external location. The startup indicates that the mapping is made to that location as expected.
However no PegaRULES log files are produced and there is no information in the SystemOUT log file.


Error Messages



Not Applicable.


Steps to Reproduce



Not Applicable.


Root Cause



A defect or configuration issue in the operating environment
The File parameter was not specified properly. It used an absolute path that was not correct.

Resolution



Make the following change to the operating environment:

Out of the box Pega 7 uses this symbolic which is substituted to the application temp directory @{web.temp}

<param name="FileNamePattern" value="'@{web.tmpdir}/PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>

Specifying other symbolics for the directory such as ${your_symbolic} are substituted as defined in the apache log4j documentation.
<param name="FileNamePattern" value="'${your_symbolic}/PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>

Specifying without a leading . (period) will cause the directory to be absolute.
<param name="FileNamePattern" value="'/your_directory/PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>

Specifying with a leading . (period) will cause the directory to be relative to the current directory for the application server

<param name="FileNamePattern" value="'./your_directory/PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>
Suggest Edit

Published October 1, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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