Introduction
This document describes how Java JRE Changes in 2025.07 affect upgrades on an ADP with both Release Independent and Dependent applications.
Design
The Application Delivery Platform (ADP) is the BroadWorks server that replaces the Xtended Service Platform (XSP) and Profile Server (PS) at version 24.0 and up.
There are two application types, Release Independent (RI) applications and Release Dependent applications, sometimes referred to as Release Anchored (RA):
- Release Dependent applications contain the major BroadWorks release version in the application name. These applications must be updated after the Application Server (AS) is upgraded and are not backward compatible with older major releases of the AS.
- Release Independent applications do not have the major BroadWorks release version in the application name. These applications must be updated before the Application Server (AS) is upgraded and are backward compatible with an older version of the AS.
The ADP is intended to be dedicated to only Release Independent or only Release Dependent applications on a per server basis. However, this is not enforced and the ADP allows both application types to be deployed on a single server.
Impact of Java JRE Changes in 2025.07 and Later
When upgrading a BroadWorks system the Release Independent applications must be upgraded before the Application Server (AS) and the Release Dependent applications must be upgraded after the AS.
Normally this is not a problem and the ADP can be upgraded, Release Independent applications updated and Release Dependent applications updated after the AS is upgraded. However, when upgrading to 2025.07 or later this is not possible.
Release 2025.07 upgrades Java JDK to version 11 for all BroadWorks components. As a result, there is an incompatibility between applications built for Java 8 and the ADP built for java 11. This means that when upgrading to 2025.07 or later, it is mandatory to upgrade all applications at the same time as the ADP. If the ADP has both Release Independent applications and Release Dependent applications deployed on it this becomes a problem. ADPs that are dedicated to only Release Dependent applications (with no RI applications deployed) do not encounter this problem and are upgraded after the AS as normal.
Upgrading an ADP from Release 24.0 with Mixed Applications
When upgrading from release 24 there is a straightforward workaround. Release 24 end of support is July 31, 2026 which means that the release 24 applications have been updated.
Steps to upgrade:
- Install the latest version of the 24.0 Release Dependent applications and Release Independent applications but do not manually update the applications.
- Upgrade the ADP - the upgrade automatically updates the Release Dependent applications and Release Independent applications that use Java 11.
- Upgrade the AS to 26.0.
- Update the Release Dependent applications versions for 26.0.
Some applications, where the file name ends in .war, do not align with the normal naming standard for Release Dependent applications or Release Independent applications such as BWCallSettingsWeb_1.15.20_2.war. These applications need to be updated manually.
Upgrading an ADP from Release 25.0 with Mixed Applications
Release 25 is no longer receiving updates as 2024.07 was the last release of 25 and release 26 begins at 2024.08. This means that the Release Dependent applications for 25 have not been updated. The system must be upgraded in two jumps or the Release Independent and Release Dependent applications be on separate ADPs.
Steps to upgrade:
- Upgrade the ADP to 2025.06.
- Install and update the Release Independent applications.
- Upgrade the AS to release 26 (you can choose a release 26.0 version later than 2025.07).
- Update the Release Dependent applications versions for 26.0 no later than 2025.06.
- Install the latest version of the 26.0 Release Dependent applications and Release Independent applications but do not manually update the applications.
- Upgrade the ADP to 2025.07 or later - the upgrade automatically updates the Release Dependent applications and Release Independent applications that use Java 11.
- Update remaining applications if necessary.
Some applications, where the file name ends in .war, do not alline with the normal naming standard for Release Dependent applications or Release Independent applications such as BWCallSettingsWeb_1.15.20_2.war. These applications need to be updated manually.
Upgrading an ADP from Release 26.0 with Mixed Applications
Upgrading from 26.0 to a later version beyond 2505.07 only requires that Release Dependent applications be installed prior to upgrading.
Steps to upgrade:
- Install the latest version of the 26.0 Release Dependent applications and Release Independent applications but do not manually update the applications.
- Upgrade the ADP - the upgrade automatically updates the Release Dependent applications and Release Independent applications that use Java 11.
- Upgrade the AS.
- Update remaining applications if necessary.
Some applications, where the file name ends in .war, do not align with the normal naming standard for Release Dependent applications or Release Independent applications such as BWCallSettingsWeb_1.15.20_2.war. These applications need to be updated manually.
Feedback