To upgrade PingCentral to 1.7, on either Windows or Linux, download the 1.7 installation file, run the PingCentral upgrade utility, and plan for a short period of downtime.
- You are signed on to your system and have privileges that allow you to install applications.
- All system requirements are met, and the Oracle Java 11 LTS runtime environment is installed.
- The JAVA_HOME path points to the Java Development Kit software on your system. For example, /usr/lib/jvm/java-11-openjdk-18.104.22.168-0.e17_7.x86_64. To verify this information, run the echo $JAVA_HOME command.
- The Java /bin directory path is added to the <PATH> variable. To verify this information, run the echo $PATH command.
Download the ping-central-1.7.0.zip file and extract its
You can delete this file after the upgrade is complete.
If PingCentral is running, shut it down.
This maintains the integrity of the H2 database file and ensures that you are running 1.7 as you complete the installation.
Make a copy of the existing PingCentral version product directory so that the
older version can be restored if the upgrade process fails.
If PingCentral has been configured to use an external database, such as MySQL, or PostgreSQL, make a copy of that database so that it can be restored if the upgrade process fails.
Go to the
directory and run the appropriate file:
Option Description Windows Run bin\upgrade.bat "--existing=PINGCENTRAL_HOME" Linux Run bin/upgrade.sh --existing=PINGCENTRAL_HOMEThe upgrade process begins. The upgrade utility uses the extracted contents of the ping-central-1.7.0.zip file to copy and replace the appropriate information in the existing version location.Note:
When the upgrade is complete for this release, PingCentral 1.7 will run from the directory in which PingCentral was initially installed. For example, if PingCentral 1.2 was initially installed and you upgraded to 1.3, and now to 1.7, PingCentral 1.7 will run from the original 1.2 directory. The same is true if you upgraded directly from 1.2 to 1.7.
To update the license file (conf/pingcentral.lic), add
--license=<file> at the end of the upgrade command
and specify the path to the new license.
As the upgrade continues, a message displays that reminds you to shut down PingCentral if you have not already done so.
To continue, type yes.
A message displays that reminds you to back up your PingCentral program files.
To continue, type yes.
The upgrade continues and the system displays a message when the upgrade is complete.Note:
If PingCentral was installed as a service by one user, and the upgrade is performed by another user, the service will no longer start. To resolve this issue, run the following command to update the installation files to match the existing ownership:
chown -R [user]:[group] [INSTALL_DIR]
Where the user and group match the existing installation:
chown -R pingcentral:pingcentral /usr/local/pingcentral-1-1.7.0/
Inspect the upgrade utility output for warnings regarding required manual
Other than the application.properties file, which is merged automatically, you must manually merge customizations you consider important. These customizations might include changes you made to the conf/log4j2.xml file, or changes you made to a file in the /bin directory.
Start PingCentral 1.7.
Option Description Windows Run /<PINGCENTRAL_HOME>/bin/run.bat. Linux Run /<PINGCENTRAL_HOME/bin/run.sh, or by running the systemd service command, systemctl pingcentral-# start.
Sign on to PingCentral using the credentials you used to sign on to the
There is no need to reconfigure PingCentral to run as a Windows or Linux systemv or systemd service after the upgrade.
Upon successful upgrade, delete the 1.7 distribution .zip
file and the directory into which it was extracted.
After the upgrade, advise your users to refresh their browsers if they experience issues.