1. In your current Policy Editor, complete the steps in Backing up policies.
  2. Stop the Policy Editor.
    $ bin/stop-server
  3. Obtain and unzip the new version of the PingAuthorize Policy Editor in a location outside the existing GUI's installation.
  4. Copy the existing database.

    The new server installation might require changes to the policy database structure. The server setup tool performs these upgrades and generates a new configuration.xml file.

    This example assumes the old installation is in /opt/pingauthorize/PingAuthorize-PAP-previous, and the new installation is in /opt/pingauthorize/PingAuthorize-PAP.

    To upgrade a database from Run this command
    8.1 and later versions
    $ cp /opt/pingauthorize/PingAuthorize-PAP-previous/Symphonic.mv.db opt/pingauthorize/PingAuthorize-PAP
    8.0 and earlier versions
    $ cp /opt/pingauthorize/PingAuthorize-PAP-previous/admin-point-application/db/Symphonic.mv.db opt/pingauthorize/PingAuthorize-PAP
  5. Run setup.

    Updating PingAuthorize Server uses an update tool. PingAuthorize GUI does not have this tool though. Instead of updating the GUI in-place, you install the new GUI.


    The setup tool uses the default credentials to upgrade the policy database. If the credentials no longer match the default values, the server administrator should pass the correct credentials to the setup tool using the --dbAdminUsername, --dbAdminPassword, --dbAppUsername, and --dbAppPassword command-line options. Otherwise, setup fails when it cannot access the policy database, or it might reset credentials to their default values. For more information, see Manage policy database credentials.

    Follow the instructions in one of the following topics:

  6. Start the new GUI.
    Follow the instructions in Post-setup steps (manual installation).
  7. In the new GUI, complete the steps in Upgrading the Trust Framework and policies.