Directory server

This page shows how to upgrade a directory server in place.

Before upgrading, make sure you stop the server. Once you have unpacked the new server files, do not modify the server configuration until after you have completed the upgrade process.

Failure to follow the upgrade instructions can result in the loss of all user data.

Make sure you’ve completed the tasks in Before you upgrade in place.
Stop the server.
Proceed to upgrade the server:
1. When upgrading a server installed from the cross-platform ZIP distribution:
  - Unpack the new files over the old files as described in Unpack files.
  - If the existing server uses a Java version that is no longer supported, follow the steps in Java updates, but do not restart the server yet.
  - Run the upgrade command to bring the server up to date with the new software delivery.
    
    By default, the upgrade command runs interactively, requesting confirmation before making important configuration changes. For some potentially long-duration tasks, such as rebuilding indexes, the default choice is to defer the tasks until after upgrade.
    
    You can use the --no-prompt option to run the command non-interactively. In this case, the --acceptLicense option lets you accept the license terms non-interactively.
    
    When using the --no-prompt option, if the upgrade command cannot complete because it requires confirmation for a potentially long or critical task, then it exits with an error, and a message about how to finish making the changes. You can add the --force option to force a non-interactive upgrade to continue in this case, also performing long-running and critical tasks.
2. When upgrading a server installed from native packages, use the system package management tools.
Although unlikely, when the server configuration has changed in an incompatible way with the previous release, the upgrade command can fail when performing property value substitution for a configuration expression. If this happens, change the configuration to a static value during upgrade. Use the configuration expression again after you successfully run the upgrade command.
When the mutable data mounted at runtime differs from that of the instance where you first run the upgrade command, upgrade only mutable data by running the command again with the --dataOnly option at runtime.

The --dataOnly option can be useful when running the server in a Docker container, for example.
Start the upgraded server.

At this point, the upgrade process is complete. Refer to the resulting upgrade.log file for a full list of operations performed.

Replication updates the upgraded server with changes that occurred during the upgrade process.
If you disabled the Windows service to upgrade, enable it again:
```
C:\path\to\opendj\bat> windows-service.bat --enableService
```

Next steps

Perform these steps before you upgrade
Upgrade each:
Perform these steps after you upgrade

PingDS 7.5.0

Directory server

Next steps