If you have modified any Jetty or JBoss settings that need to be carried forward, you must make the corresponding changes manually in the new PingFederate deployment.

If you are upgrading from PingFederate 6.9 or later, merge any changes in <pf_install>/etc/jetty-runtime.xml and <pf_install>/etc/jetty-admin.xml files into the corresponding files of the new deployment.


If only the values of the minThreads, maxThreads, and acceptQueueSize parameters were modified in those Jetty files, you should set those values in the new deployment's <pf_install>/bin/run.properties file instead of merging them into the Jetty files.

The advantage of setting those values in run.properties is that PingFederate can automatically merge run.propertiescustomizations into new deployments, saving you time and preventing errors in future upgrades. For more information, see Configuring PingFederate properties.

If you are upgrading from PingFederate 6.0 through 6.8, first identify any changes made to the JBoss configuration, then make corresponding changes for the newer Jetty configuration.

For example, if you modified the <pf_install>/pingfederate/server/default/deploy/jetty.sar/META-INF/jboss-service.xml file before 6.9, identify the changes and make the same modifications at corresponding points in either the jetty-admin.xml or jetty-runtime.xml files located in the new Jetty configuration directory, <pf_install>/pingfederate/etc.