Enabling console logging
You can edit the <pf_install>/pingfederate/server/default/conf/log4j2.xml file to enable console logging.
About this task
For troubleshooting purposes, you can enable console logging or verbose messages.
|
When you no longer require console logging or verbose messages, turn them off. On Windows, never highlight the console output because it might slow or stop PingFederate from processing requests. |
To enable console logging:
Steps
-
Edit the
<pf_install>/pingfederate/server/default/conf/log4j2.xmlfile. -
Look for the
Set up the Root loggersection as shown in the following example.... <!-- ======================= --> <!-- Set up the Root logger --> <!-- ======================= --> ... <AsyncRoot level="INFO" includeLocation="false"> <!-- <AppenderRef ref="CONSOLE" /> --> <AppenderRef ref="FILE" /> </AsyncRoot>Then, update as shown in bold in the following snippet.
... <!-- ======================= --> <!-- Set up the Root logger --> <!-- ======================= --> ... <AsyncRoot level="INFO" includeLocation="false"> <AppenderRef ref="CONSOLE" /> <AppenderRef ref="FILE" /> </AsyncRoot>When you no longer require console logging, comment out the
<AppenderRef ref="CONSOLE" />entry for theAsyncRootlogger. -
Save any changes made.
-
In a clustered PingFederate environment, repeat these steps on each applicable node.
Result
PingFederate activates the changes within half a minute. You don’t need to restart PingFederate.