PingDirectory

Upgrading the PingDirectory, PingDirectoryProxy, and PingDataSync servers

When upgrading your server, there are multiple upgrade scenarios with different implications that you need to consider. Use the server’s update utility to upgrade the current server code version.

Upgrading the server

Use the following steps to upgrade the PingDirectory, PingDirectoryProxy, and PingDataSync servers.

Before you begin

This task shows the upgrade process for the PingDirectory server as an example.

Steps

  1. Download and extract the new version of the PingDirectory server in a location outside the existing server’s installation.

    For these steps, assume the existing server installation is located in /prod/PingDirectory and the new server version is extracted in the /home/stage/PingDirectory location.

  2. Run the update command provided with the new server package to update the existing PingDirectory server.

    Example:

    $ /home/staging/PingDirectory/update --serverRoot /prod/PingDirectory

    The update tool might prompt for confirmation of the server configuration changes if it detects customization.

Reverting an update

After the server has been updated, you can revert to the last version or one level back using the revert-update command.

About this task

The revert-update command accesses a log of file actions taken by the updater to put the file system back to its prior state, including the prior server configuration. If you have run multiple updates, you can run the revert-update command multiple times to revert to each prior update sequentially. You can only revert back one level.

For example, if you have run the update twice since first installing the server, you can run the revert-update command to revert to its previous state, then run the revert-update command again to return to its original state.

When starting up the server for the first time after a revert has been run, and the necessary extra steps have been completed, the server displays warnings about "offline configuration changes," but they aren’t critical and don’t appear on subsequent start ups.

To revert to the most recent server version:

Steps

  • Run the revert-update command in the server root directory to revert back to the most recent version of the server.

    Example:

    $ PingDirectory-old/revert-update

Upgrading or reverting a topology

For servers in a topology, you can upgrade or revert updates by following the steps in Upgrading the server or Reverting an update on each server in the topology.

Troubleshooting revert-update failures

When you run revert-update, if the topology doesn’t have a primary server, the command fails. In this case, you must make one of the remaining updated servers in the topology the primary. This enables the chosen instance to run the revert-update command successfully.

For a given topology, don’t set more than one server at a time as primary. After completing the revert for the topology, set force-as-master-for-mirrored-data back to false for the server you set as primary.

To make a server the primary, run the following command on the server:

$ bin/dsconfig set-global-configuration-prop \
  --set force-as-master-for-mirrored-data:true