Ensure that:

  • 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-11.0.5.10-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.
  1. Make a copy of the PingCentral version 1.2.0 or 1.3.0 product directory so that the older version can be restored if the upgrade process fails.
  2. If PingCentral is running, shut it down.

    This maintains the integrity of the H2 database file and ensures that you are running 1.4.0 as you complete the installation.

  3. Download the ping-central-1.4.0.zip file and extract its contents to a suitable location.

    You can delete this file after the upgrade is complete.

  4. Go to the <pingcentral_1.4.0_install>/upgrade directory and run the appropriate file:
    • For Windows, run bin\upgrade.bat "--existing=PINGCENTRAL_HOME"
    • For Linux, run bin/upgrade.sh --existing=PINGCENTRAL_HOME

    The upgrade process begins. The upgrade utility uses the extracted contents of the ping-central-1.4.0.zip file to copy and replace the appropriate information in the existing version 1.2.0 or version 1.3.0 location.
    Note: When the upgrade is complete for this release, PingCentral version 1.4.0 will run from the directory in which PingCentral was initially installed. So if PingCentral version 1.2.0 was initially installed and you upgraded to version 1.3.0, and then to version 1.4.0, PingCentral will run from the 1.2.0 directory. The same is true if you upgraded directly from version 1.2.0 to version 1.4.0.
  5. Optional: 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.
  6. Type yes to continue.
    A message displays that reminds you to back up your PingCentral program files.
  7. Type yes to continue.
    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. For example:
    chown -R pingcentral:pingcentral /usr/local/pingcentral-1-1.3.0/
  8. Start PingCentral version 1.4.0.
    • For Windows, run /<PINGCENTRAL_HOME>/bin/run.bat.
    • For Linux, run/<PINGCENTRAL_HOME/bin/run.sh, or by running the systemd service command, systemctl pingcentral-# start.
  9. Sign on to PingCentral using the credentials you used to sign on to version 1.2.0 or 1.3.0.

    There is no need to reconfigure PingCentral to run as a Windows, Linuxv, or Linuxd service after the upgrade.