PingFederate 6.x and 7.x use Log4j to write log messages.
If the Upgrade Utility or the PingFederate installer for Windows determines that the Log4j configuration file (log4j.xml in the <pf_install>/pingfederate/server/default/conf directory) has changed since it was originally installed, these upgrade tools copy the modified log4j.xml to the new installation with a new name and installs the new log4j2.xml from the product ZIP file.
The new name for the previously customized log4j.xml is log4j-old-<SourceVersion>.xml, where <SourceVersion> is the version number of the source PingFederate installation.
Both configuration files are located in the conf directory.
To migrate custom changes from Log4j to Log4j2:
Review custom changes by comparing
log4j.xml that is located in the
directory from the upgrade tool.
The <SourceVersion> values must match each other.
Modify log4j2.xml to suit your needs.
The configuration syntax between Log4j and Log4j2 varies. For more information, consult Log4j 2 documentation (logging.apache.org/log4j/2.x/manual/index.html).
- If you are writing log messages to a database server, enter the database information into log4j2.db.properties in the same conf directory.
- If you have a clustered PingFederate environment, repeat steps 2 and 3 for all applicable PingFederate nodes in the cluster.