This section explains how the upgrade works and shows you which files are added and replaced during the process. For instructions on running the upgrade itself, see Upgrading to PingCentral 1.8.
Note: Starting with PingCentral 1.8, signing certificates are stored in the PingCentral database instead of a PingCentral-specific trust store. Certificates that exist in this trust store are imported to the PingCentral database during the upgrade process.

How the upgrade works

The upgrade utility uses the extracted contents of the file to copy and replace the appropriate information in the existing version installation location.

Files that were not modified since they were initially installed are overwritten with new versions during the upgrade process.

Note the following:
  • The database files (h2-data directory), the log files (log directory), the external library files (ext-lib directory), and the host key file (conf/pingcentral.jwk) remain intact during the upgrade process to preserve user data.
  • If the file was modified, the current version of the file will be merged with the latest version, preserving customizations.
  • If the conf/log4j2.xml, bin/, and files were modified, the new versions are installed and the old versions are renamed. Manually update the new files with customizations, as necessary.

The following image shows PingCentral 1.8 after it has been run and the database files that have been generated. It also shows which files are replaced with new files during the upgrade process.