PingFederate Server

Other configuration files

As of PingFederate 10.0, the upgrade process copies many files automatically. However, there are still some files that you must copy manually, which you can find in <pf_install>/pingfederate/server/default/conf.

The following files are copied automatically:

  • Properties files with the .conf extension

  • The log4j2.db.properties file

  • The jmx-remote-config.xml file

  • The csd_configuration.yaml file

  • Non-default files located in the template directory

If you modified the default templates located in <pf_install>/pingfederate/server/default/conf/template, you must customize these templates in the new PingFederate installation.

If you modified versions of tcp.xml, udp.xml, and log4j2.xml, they are copied over intact. The default files are saved in the target directory with a different extension. To take advantage of the improvements in the default versions of these files, merge your changes into the current default files and then rename them appropriately.

If you are upgrading from 8.0 or earlier, PingFederate might not start until you have merged your changes into the current default files because of JGroups errors.

Other files, such as jmx.remote.access, are not copied to the new installation automatically. To preserve any custom settings, create a backup of the current configuration files and merge your changes to the current files.

If you previously customized Java virtual machine (JVM) options in the run.bat or run.sh files, instead of updating these files, manually merge your JVM options to the <pf_install>/pingfederate/bin/jvm-memory.options file. For more information, see Fine-tuning JVM options and memoryoptions and upgrade.