RDM 16.1.0 Upgrade Notes

From 16.1.0, RDM Web Application is able to detect changes in the RDM Server configuration repository.

In earlier versions, after changing the URL to the configuration repository (or the specific branch), you had to select the new configuration (commit) manually from the RDM Admin Console in order for the RDM Server to start. Otherwise, RDM Webapp would try to apply the previously used configuration, which could no longer be retrieved from the repository, and the server would fail to start.

RDM Webapp can now successfully handle changes to the repository without user intervention. However, if your upgrade to 16.1.0 also includes changes to the repository URL or branch, the change might not be correctly processed.

In that case, if the server does not start, you still need to select a commit manually from the repository before retrying. To do this, go to Admin Console > Server Dashboard. In Server configurations section, find the configuration you want to use and select its ID in the RESTART column. This will restart the server with the selected configuration.

This section provides the information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.

The following table lists the configuration files that were added, changed, or removed.