You can choose between two upgrade paths:

• Short-term path (STP). Upgrade to each new service pack (for example, from 23.4 to 24.1). If you choose this path, you need to go through all the interim service packs to upgrade to the following release.

• Long-term path (LTP). Upgrade directly from one release to the next (for example, from 16.2.100 to 24.3, the next LTP release), without having to upgrade to each of the interim service packs.

Refer to the release's upgrade path details below.

This version is an LTP release. You can upgrade to this version from 24.3.

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.

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 8.11 or later is required (version 8.11 is recommended). This is enforced on startup.

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.

For details, see "Prepare for Elasticsearch re-indexing" in the 24.3 Upgrade Guide.

Note: Re-index must be completed successfully, or you cannot upgrade to the next release.

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>/

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 8.x is required. This is enforced on startup.

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.

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 8.6.0 is now supported. We recommend using Elasticsearch 7.17.8 or 8.6.0.

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.

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.

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.

In this service pack, Elasticsearch re-index is mandatory.

• Space re-index. Spaces that have not been re-indexed are not accessible to users. You must complete re-index before upgrading.

  If you do not, you can re-index after upgrading, but access to the shared space is blocked until re-index is completed successfully.

• Site re-index. Re-index is not enforced at the site level. It is the responsibility of the site admin to verify that site re-index is complete.

  If re-index is not complete, the index will not perform properly following upgrade. For example, audit data may be inaccurate. In addition, upgrade to Elasticsearch 8 may fail in future releases.

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.

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.

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.

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.

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.