Flashes (Alerts)
Abstract
Beginning with the IBM WebSphere Application Server v8.5.5.22 Fix Pack level (Targeted GA for the 25th of July, 2022), IBM will no longer support JDK v7.0/7.1 to be configured for IBM WebSphere Application Server v8.5 profiles, command & new profile defaults, and used for installation of the product. All IBM WebSphere Application Server v8.5 profiles and defaults will need to be updated to JDK 8.0 before the 8.5.5.22 fix pack is installed to maintain full support from IBM. IBM JDK 8.0 is supported on IBM i 7.1 and newer.
Content
During the WebSphere Application Server v8.5.5.22 installation process, an informational message will be logged to the Installation Manager's log file discussing the end of support for Java SE 7.0/7.1 with WebSphere Application Server v8.5. Here is the message displayed by the Installation Manager product in its standard out and install logs.
Support for Java SE 7.0/7.1 with WebSphere Application Server traditional ends in July 2022. If you continue to use Java SE 7.0/7.1 after the end of the support date, you might expose your environment to security risks.
=====================================================================================
IBM recommends using IBM JDK v8.0 64 bit as your default JDK version on your IBM i server. Information on how to download and install IBM JDK v8.0 on the IBM i OS at IBM i 7.1 and later can be found in the following IBM Technical Document.Support of Java Development Kit (JDK) 8.0 on the IBM i OS
IMPORTANT!!!
JDK 8.0 support is provided with 8.5.5.9 and later. If you want to switch your IBM WebSphere Application Server product and profiles to use JDK 8.0, you MUST have the WebSphere Application Server fix pack 8.5.5.9 or later currently installed before you will be able to specify the 1.8_64 or 1.8_32 sdkname values on the managesdk command.
Before the WebSphere Application Server v8.5.5.22 fix pack is installed, all WebSphere Application Server profiles, command/new profile defaults will need to be changed to use JDK v8.0.
The following steps can be taken to complete this task.
NOTE: These steps assume the 57xxJV1 Option 17 LPP has already been successfully installed.
STRQSH
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
./managesdk -setNewProfileDefault -sdkname 1.8_64
./managesdk -setCommandDefault -sdkname 1.8_64
For Standalone profiles...
./managesdk -enableProfileAll -sdkname 1.8_64 -enableServers [-user [user] -password [password]]
For a Deployment Manager and Federated profiles...
NOTE: If this is a WebSphere Application Server v8.5 ND federated environment, you will need to end the DMGR and upgrade the DMGR SDK version first.
./stopManager -profileName [dmgr]
./managesdk -enableProfile -profileName [dmgr] -sdkname 1.8_64 -enableServers [-user [user] -password [password]]
After upgrading the DMGR, start the DMGR and upgrade all profiles.
./startManager -profileName [dmgr]
./managesdk -enableProfileAll -sdkname 1.8_64 -enableServers [-user [user] -password [password]]
====================================================================================
More information on the WebSphere Application Server managesdk command and usage examples, please refer to the following IBM Technical Document.
How to use the 'managesdk' command with WebSphere Application Server (WAS) v8.0 and later on the IBM iRelated Information
Was this topic helpful?
Document Information
Modified date:
13 June 2022
UID
ibm16591593