Merging custom logging configurations - PingFederate - 11.2

PingFederate Server

bundle
pingfederate-112
ft:publication_title
PingFederate Server
Product_Version_ce
PingFederate 11.2
category
Administrator
Administratorguide
Audience
Capability
ContentType
DeploymentMethod
Guide
Product
Productdocumentation
SingleSignonSSO
Software
SystemAdministrator
pf-112
pingfederate
ContentType_ce
Guide
Guide > Administrator Guide
Product documentation

The upgrade tools do not support automatic merging of customizations made to the existing logging configuration. Instead, these upgrade tools copy the modified log4j2.xml file to the new installation intact and rename the configuration file from the product .zip archive using the new PingFederate version number. Both configuration files are located in the same conf directory.

Note:

If the Upgrade Utility or the PingFederate installer for Windows determines that the log4j2 configuration file ( <pf_install>/pingfederate/server/default/conf/log4j2.xml) has changed since it was originally installed, new features are not activated.

To activate new features:

  1. Review the new features by comparing the renamed log4j2 configuration file against the log4j2.xml file.
  2. Modify the log4j2.xml file to suit your needs.
  3. If you have a clustered PingFederate environment, repeat step 2 for all applicable PingFederate nodes in the cluster.