• Make a backup copy of the PingAccess home directory. If the upgrade fails, use the backup copy to restore PingAccess.
  • Review the release notes for every version between your current version and the target version.
  • Verify that each node is using the same PingAccess version. You can check the version by viewing the <PA_HOME>/lib/pingaccess-admin-ui-<version number>.jar file.
  • Verify that the PingAccess administrative node is running.
  • Verify that basic authentication is configured and enabled for the running PingAccess administrative node.
  • Download the PingAccess incremental update .zip file for the target version.

Use the PingAccess incremental update bundle to upgrade a cluster from PingAccess 6.3, the source version, to the most recent maintenance release for PingAccess 6.3, the target version.

Note:

This upgrade procedure causes some downtime. To upgrade a cluster with no downtime, see the Zero Downtime Upgrade guide.

  1. Upgrade the administrative node.
    1. Extract the .zip file for the target version of PingAccess.
    2. Open the readme file included in the extracted .zip bundle.
    3. Make the file changes specified in the readme file.
  2. Upgrade the replica administrative node.
    1. Extract the .zip file for the target version of PingAccess.
    2. Open the readme file included in the extracted .zip bundle.
    3. Make the file changes specified in the readme file.
  3. Upgrade each engine node.
    1. Extract the .zip file for the target version of PingAccess.
    2. Open the readme file included in the extracted .zip bundle.
    3. Make the file changes specified in the readme file.
  4. Shut down the entire cluster.
  5. Start the upgraded administrative node.
  6. Start the upgraded replica administrative node.
  7. Start each upgraded engine node.

After you complete the upgrade, see Performing post-upgrade tasks.