Updating the Liberty Java runtime environment or software development kit
Updating to the latest Java™ version ensures that your Liberty environment receives new features and security fixes.
About this task
- Get the Liberty runtime environment and Java in a single package by installing the Liberty with Java EE 8 Web Profile and IBM® Java SDK 8 ZIP file.
- Download IBM SDK, Java Technology Edition from IBM Java SDKs for WebSphere Liberty.
- Download a ZIP file that contains the Liberty runtime environment and Jakarta EE 8 from Get started with Open Liberty.
- Separately download and install another specification-compliant JRE or Java SDK such as Oracle Java SE. For information about obtaining Java SE 11 or later, see the Open Liberty Java SE support page.
Update your Liberty installation to at
least the minimum fix pack that supports the Java version. The more recent the fix pack, the more
features and fixes are included.
- Java SE 20 requires Liberty fix pack 18.104.22.168 or later.
- Java SE 17 requires Liberty fix pack 22.214.171.124 or later.
- Java SE 11 requires fix pack 126.96.36.199 or later.
- Java SE 8 requires fix pack 188.8.131.52 or later.
Thanks to Liberty zero-migration architecture, you can update your installation with minimal impact to your current applications and configuration. For more information about Liberty zero-migration architecture, see Zero-migration architecture on the Open Liberty website.
The method that you use to update Liberty depends on how it was initially installed. If you installed from an archive file, such as a ZIP or JAR file, see Applying a fix pack to a Liberty ZIP archive installation or Applying a fix pack to a Liberty Java archive installation. If you used Installation Manager, see Updating Liberty on distributed operating systems.
For more information, see Installing Liberty interim fixes and fix packs on z/OS® operating systems.
Update the JRE or Java SDK by using one of the following
- If you installed Liberty from the .zip file with IBM Java SDK 8, you also received the latest Java updates. If you previously installed Liberty from this file and want to independently update the Java SDK, download a newer version from IBM Java SDKs for WebSphere Liberty.
- If you installed Liberty by using
Installation Manager, you can also use it to install and update IBM
Java SDKs. If you use IBM
Java, install one of the common IBM
Java SDKs, such as IBM SDK, Java Technology Edition, Version 8. The
IBM SDKs receive security updates faster than the older WebSphere®
Java SDKs because they are not on the WebSphere fix pack schedule. The IBM
Java 8 SDK is also used by WebSphere Application Server traditional V9.0.
For more information about installing IBM Java SDKs by using Installation Manager, see Installing, updating, and uninstalling IBM SDK, Java Technology Edition.
For more information about installing IBM Java SDKs by using Installation Manager, see Installing IBM SDK, Java Technology Edition on z/OS.
- Install a separately downloaded JRE or Java SDK. You can
install any specification-compliant JRE or Java SDK of a
supported Java version.After you install the JRE or Java SDK, change the Java level that Liberty uses by setting the
JAVA_HOMEvariable.Tip: You can specify the Java SDK or JRE location on theAlternatively, you can set the
JAVA_HOMEproperty in the server.env file, as described in Customizing the Liberty environment. When you set the
JAVA_HOMEproperty in the server.env file, Liberty uses the same Java runtime location regardless of the user profile that the Liberty server runs under.
JAVA_HOMEvariable on your operating system:
Go to Environment Variables. Add or edit the. In the Advanced tab of the System Properties window, click
JAVA_HOMEsystem variable so that it points to the jre directory of the Java installation, such as C:\Program Files\IBM\Java80\jre.
If you are running bash shell, you can add the
JAVA_HOMEenvironment variable to the .bashrc file in the user's home directory.
Check for any deprecations or incompatibilities by scanning your applications with the
In most cases, Java SE specifications are upwards binary-compatible with previous Java SE versions except for the incompatibilities and deprecations that are documented in the Oracle Compatibility Guide for JDK 8 and Java SE 7 and JDK 7 Compatibility.Important: Java SE 11 introduced significant breaking changes, primarily the removal of Java EE and CORBA APIs.The Migration Toolkit consists of two separate tools, the Migration Toolkit for Application Binaries and the Eclipse-based WebSphere Application Server Migration Toolkit.
- The application binary scanner provides a detailed migration analysis report for your application, so you can better understand the type and scope of changes that the application might require.
- When you migrate your applications, the Eclipse-based Migration Toolkit provides quick fixes to automatically update your source when possible and provides detailed help for items that must be manually updated.