How the upgrade works

The upgrade utility uses the extracted contents of the ping-central-1.11.0.zip 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 you are using the H2 database, when upgrading from a previous version of PingCentral to 1.11, the upgrade script will generate a directory that contains the old H2 v1 database (h2v1-data). This file may be deleted after checking that the upgrade was successful in PingCentral.

Use the H2 database only for trial or training environments. It is not recommended to use the default H2 database in production. For testing and production environments, always use a secured external storage solution for proper functioning in a clustered environment. For more information on setting up an external database, see Setting up MySQL.

Testing involving H2 is not a valid test. In both testing and production, it might cause various problems due to its limitations, and PingCentral does not support H2-involved cases.

If the application.properties file was modified, the current version of the file is merged with the latest version, preserving customizations.

If you upgrade from any version prior to 1.10, use an H2 database, and still use the default password from your last installation, a new password will override it during this upgrade. However, if you updated the password from the original default, it is preserved in the application.properties file.

If the conf/log4j2.xml, bin/run.sh, and bin.run.bat 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 list indicates which directories and files are replaced with new files during the upgrade process of PingCentral 1.11, provided that they were not modified since the initial installation.

ReadMeFirst.txt
bin/obfuscate.bat
bin/obfuscate.sh
bin/run.bat
bin/run.sh
conf/application.properties
conf/log4j2.xml
bin/obfuscate.bat
legal
ping-central.jar
sbin
tools