Upgrade
Use the upgrade guide to upgrade on-premises servers. Pay attention to specific upgrade highlights for the relevant version.
Upgrade guides
Use the following guides to upgrade on-premises servers.
Version | 25.1 |
---|---|
Linux Upgrade Guide | ![]() |
Windows Upgrade Guide | ![]() |
General upgrade notes
Note the following general information when upgrading.
Category | Description |
---|---|
Backups | Make sure to have viable accessible backups of your relational database (either Oracle or SQL Server), Elasticsearch, and the repository folder on your file system. |
Cluster | Make sure to stop services for all cluster nodes before upgrading. |
STP/LTP Upgrade |
You can choose between two upgrade paths:
Refer to the release's upgrade path details below. |
Upgrade to 25.1 (LTP release)
Category | Description |
---|---|
Upgrade path |
This version is an LTP release. You can upgrade to this version from 24.3. |
Harden the authentication | You must harden the authentication mechanism by replacing the existing hpssoconfig.xml configuration file and storing the encryption key in a keystore file. For details, see "Harden the authentication" in the 25.1 Upgrade Guide. |
Upgrade to 24.3 (LTP release)
Note the following when upgrading to 24.3 (LTP release).
Category | Description |
---|---|
Upgrade path |
This version is an LTP release. You can upgrade to this version either directly from 16.2.100 (the previous LTP release), or from 24.1. |
Java version |
JDK 21 is required and must be installed before you upgrade. Before you install JDK 21, make a backup copy of the default Java keystore (cacerts) file from the existing JDK 11 installation. Then, after you install JDK 21, use the backup copy to replace the cacerts file that is provided with JDK 21. This avoids potential issues with the new cacerts file. |
Elasticsearch version |
Elasticsearch 8.11 or later is required (version 8.11 is recommended). This is enforced on startup. |
Elasticsearch re-index |
The upgrade triggers Elasticsearch re-index. Indexes are re-indexed to version 8. When a space's post-upgrader is running, its Elasticsearch features are not all disabled during the entire process. Instead, features are in downtime only when an index they are dependent on is in the downtime phase of its re-indexing.
Note: Re-index must be completed successfully, or you cannot upgrade to the next release. |
OData version |
OData 4.0 is required. OData version 2.0 services will no longer work and will be fully replaced by OData version 4.0. To continue using OData, your connection must be updated to OData version 4.0. The OData 4.0 URI format is: <https://<server>/odata/v4/shared_spaces/<space_ID>/workspaces/<workspace_ID>/ |
Upgrade to 24.1
Note the following when upgrading to 24.1.
Category | Description |
---|---|
Upgrade path |
This version is an STP service pack, meaning that you can only upgrade to 24.1 from 23.4. If you have not yet upgraded to 23.4, upgrade now. |
Elasticsearch version |
Elasticsearch 8.x is required. This is enforced on startup. |
Upgrade to 23.4
Note the following when upgrading to 23.4.
Category | Description |
---|---|
Upgrade path |
This version is an STP service pack, meaning that you can only upgrade to 23.4 from 16.2.100. If you have not yet upgraded to 16.2.100, upgrade now. |
Upgrade to 16.2.100 (LTP release)
Note the following when upgrading to 16.2.100 (LTP release).
Category | Description |
---|---|
Upgrade path |
This version is a long term path (LTP) release, meaning that you can upgrade to 16.2.100 either directly from 16.1.100, or from 16.1.200. |
Elasticsearch version |
Elasticsearch 8.6.0 is now supported. We recommend using Elasticsearch 7.17.8 or 8.6.0. |
Elasticsearch re-index |
If you are upgrading directly from 16.1.100, verify that re-index has completed successfully in all spaces. For details, see "LTP Path: Verify Elasticsearch re-indexing (ES version 8.x)" in the 16.2.100 Upgrade Guide. |
MS SQL Server databases |
If you are using MS SQL Server databases with the FILL_EXISTING site_action, the database administrator should set READ_COMMITTED_SNAPSHOT ON on all databases used by OpenText Software Delivery Management, before deploying the new version. For details, see "Changes to MS SQL Server databases" in the 16.2.100 Upgrade Guide. |
Upgrade to 16.1.200
Note the following when upgrading to 16.1.200.
Category | Description |
---|---|
Upgrade path |
This version is an STP service pack, meaning that you can only upgrade to 16.1.200 from 16.1.100. If you have not yet upgraded to 16.1.100, upgrade now. |
Elasticsearch re-index |
In this service pack, Elasticsearch re-index is mandatory.
|
Upgrade to 16.1.100 (LTP release)
Note the following when upgrading to 16.1.100 (LTP release).
Category | Description |
---|---|
Upgrade path |
This version is a long term path (LTP) release, meaning that you can upgrade to 16.1.100 either directly from 16.0.100, or from 16.0.400. |
Elasticsearch re-index |
The upgrade triggers Elasticsearch re-index. It is important to note that the mechanism for Elasticsearch re-index has been changed to significantly minimize downtime. When a space's post-upgrader is running, its Elasticsearch features are not all disabled during the entire process. Instead, features are in downtime only when an index they are dependent on is in the downtime phase of its re-indexing. For details, see "Prepare for Elasticsearch re-indexing" in the 16.1.100 Upgrade Guide. Note that re-index must be completed. You will not be able to use OpenText Software Delivery Management in the next release if re-index was not completed successfully. |
Hazelcast version |
16.1.100 uses Hazelcast v.5.1. This requires changes to the hazelcast.xml configuration file. For details, see "Update the hazelcast.xml configuration file" in the 16.1.100 Upgrade Guide. |
Docker support |
You can now use OpenText Software Delivery Management in Docker. For details, see "Upgrade OpenText Software Delivery Management in Docker" in the 16.1.100 Upgrade Guide. |
Known issue |
When upgrading to 16.1.100 directly from 16.0.100 (LTP upgrade path) in Oracle environments, if you have a space with more than 500 workspaces, you may encounter an error message regarding the FixVulnerabilitiesCountOfWIUpgrader Data upgrader. For a workaround, see “Troubleshooting a Data upgrader failure” in the 16.1.100 Upgrade Guide. |