IBM Support

How To Change WebSphere Application Server v8.5.x Product and Profiles To Use JDK 8.0 on IBM i 7.4 OS

How To


Summary

This document will provide step-by-step instructions on how to change your IBM WebSphere Application Server v8.5.x product and profiles to use the IBM Developer Kit for Java v8.0 on the IBM i 7.4 OS.

Environment

IBM i 7.4 OS
5770JV1 Option 16 & 17
IBM WebSphere Application Server v8.5.x All Editions
 

Steps


 
1.
Set up your IBM i 7.4 environment.
 
  • Open a 5250 Telnet Client session to your IBM i 7.4 server.
  • Sign in with an IBM i User Profile with explicit *ALLOBJ and *SECADM special authorities.
  • Set the IBM i system value, QALWOBJRST, to *ALL.
    CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
2.
Ensure JDK 8.0 LPPs 5770JV1 Option 16 and 17 are installed.
  • Execute the GO LICPGM CL command.
  • Enter option 10 to display your licensed program products, and press ENTER.
  • Press F11 twice to view the "Product Option" column.
  • Scroll down to Licensed Program 5770JV1 to verify if Options 16 and 17 are installed.

If these options are not installed, please refer to the IBM Technical document, Support of Java Development Kit (JDK) 8.0 on the IBM i OS , for detailed information on downloading and installing 5770JV1 Options 16 and 17 on your IBM i OS.
3. Ensure IBM Installation Manager (IM) v1.8.9.4 or newer is installed. 

Refer to the URL:  http://www-01.ibm.com/support/docview.wss?uid=nas8N1022458 , for information on how to display the current IM version installed on your IBM i OS and then, upgrade the IM product to a newer version if the current version is 18.9.3 or earlier.
4.
Ensure your IBM WebSphere Application Server (WAS) product is at 8.5.5.9 Fix Pack version or newer.
 
Record the WAS 8.5 version for all of your WAS v8.5 installations. You will need to know it for an upcoming step.
To determine the currently installed WAS Fix Pack version, follow these steps:
  • WRKLNK '/QIBM/ProdData/WebSphere/AppServer/V85/<edition>/properties/version/WAS.product'
    where <edition> = Express, Base, ND
  • Enter Option 5 next to the WAS.product file and press ENTER to display its contents.
  • Here is an example showing the contents of the WAS.product file and the 8.5.5.13 Fix Pack version installed.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE product SYSTEM "product.dtd">
<product name="IBM WebSphere Application Server Network Deployment">
<id>ND</id>
<version>8.5.5.13</version>
<build-info date="1/12/18" level="cf131801.05"/>
</product>
If your WAS product is currently at 8.5.5.8 Fix Pack version or older, you will need to install Fix Pack 8.5.5.9 or later version before you can change your WAS product and profiles to use JDK 8.0.  This is 100% required for IBM i 7.4 OS.  IBM recommends you install 8.5.5.16 or later. Information on how to install a WAS v8.5.x Fix Pack on the IBM i OS can be found here .
5.
Start a Qshell Interpreter session by executing the "STRQSH" CL command.
NOTE:  All commands below should be executed in a Qshell interpreter session unless explicitly specified as CL commands.
6.
NOTE:  If your WAS v8.5 fix level is 8.5.5.16 or later, you do NOT need to download and upload the _setupDefaultSDK.sh script.  You can use the <app_server_root/bin/_setupDefaultSDK script instead.

If you are at version 8.5.5.15 - 8.5.5.9, you will need to...
a. Download the attached _setupDefaultSDK.sh file and upload it to your "<app_server_root>/bin" folder on your IBM i server where <app_server_root> = /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/
& <edition> = Express, Base, ND
a.(8.5.5.15 - 8.5.5.9 only!)  Rename the _setupDefaultSDK scripts to switch in the downloaded script.
STRQSH
cd to <app_server_root>/bin
mv _setupDefaultSDK _setupDefaultSDK.old
mv _setupDefaultSDK.sh _setupDefaultSDK
b. Execute the following commands to update the WAS default SDK and IBM i WAS *SRVPGM/*PGM objects:
STRQSH
cd to <app_server_root>/bin
./_setupDefaultSDK
./_postfpexit <app_server_root>
F12
  
Example:
STRQSH
cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin
./_setupDefaultSDK
./_postfpexit /QIBM/ProdData/WebSphere/AppServer/V85/Express
F12
 
c. Execute the managesdk command to update all existing WebSphere Application Server profile(s)  to use Java SE 8.0.
List all profiles and their SDK's:
STRQSH
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
./managesdk -listEnabledProfileAll
This will display all existing WAS profiles' SDK information.
CWSDK1004I: Profile <wasProfileName> :                                 
CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64                        
CWSDK1008I: Node <wasNodeName> SDK name: 1.7_64            
CWSDK1009I: Server <wasServerName> SDK name: 1.7_64                   
CWSDK1001I: Successfully performed the requested managesdk task.

  If the SDK value of “Server <wasServerNam> SDK name” is "unknown", then you will need to enable the server to use SDK version 1.8_32 or 1.8_64.
Update each WAS profile listed to use SDK 8 32 bit or 64 bit:
 ./managesdk -listAvailable
Verify 1.8_32 or 1.8_64 is displayed.  If you do not see one of these options, your WAS v8.5 product is not at the 8.5.5.9 or newer fix level OR you do not have the required 5770JV1 Option 16 or 17 installed.

./managesdk -enableProfile -profileName <profile> -sdkname <sdk_name> -enableServers [-user user_name] [-password password_value]
where <sdk_name> = 1.8_32 or 1.8_64
OR
./managesdk -enableProfileAll -sdkname <sdk_name> -enableServers
This will update all profiles to the SDK specified.
Example:
cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin

./managesdk -listAvailable

   CWSDK1005I: SDK name: 1.8_32
   CWSDK1005I: SDK name: 1.8_64
   CWSDK1001I: Successfully performed the requested managesdk task.
./managesdk -enableProfileAll -sdkname 1.8_64 -enableServers

Express and Base Editions

./managesdk -enableProfile -profileName WASprofile -sdkname 1.8_64 -enableServers

   CWSDK1017I: Profile WASprofile now enabled to use SDK 1.8_64.
   CWSDK1001I: Successfully performed the requested managesdk task.
Network Deployment Edition
NOTE: For a Deployment Manager and Federated Node topology, you will need to change the SDK version for the Deployment Manager profile(s) first.  Then, you will need to start the Deployment Manager profile(s) before you change the SDK version for the Federated Nodes.
 
  • Change the Deployment Manager profile
managesdk -enableProfile -profileName <dmgr> -sdkname 1.8._64 -enableServers -username <DMGRUser> -password <Dmgrpassword>
  • Start the Deployment Manage profile
startManager -profileName <dmgr>
  • Change all profiles to use JDK 8.0
managesdk -enableProfileAll -sdkname 1.8_64 -enableServers -username <DMGRUser> -password <Dmgrpassword>

Please see  http://www.ibm.com/support/docview.wss?uid=nas8N1019730 for detailed managesdk command usage.

  • Synchronize the nodes to the Deployment Manager:

A) In order to synchronize the node we first need to find the SOAP port for the DMGR. Run the following commands in STRQSH:
 

cd /qibm/userdata/WebSphere/appserver/v85/nd/profiles/DMGR/bin 

./dspwasinst 


Jot down the port number returned for 'SOAP_CONNECTOR_ADDRESS port'

B) Now that we have the SOAP port number, synchronize the node by doing the following commands from STRQSH (replace <NodeName> with your Node Profile Name and 12345 with the SOAP connector port from the previous step):
 
cd /qibm/userdata/WebSphere/appserver/v85/nd/profiles/<NodeName>/bin 

syncnode loopback 12345 


C) After the node is synchronized we now can start the Node Agent and the node by doing the following from STRQSH
 
cd /qibm/userdata/WebSphere/appserver/v85/nd/profiles/<NodeName>/bin 

startnode 

startserver -profileName <NodeName>

D) Now the DMGR, the Node Agent, and the node successfully start under the new JDK

7.
Verify your WAS v8.5.x product and profiles are now using SDK name 1.8_32 or 1.8_64 (SDK 8.0).
<edition> = Express, Base, ND
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
managesdk -getCommandDefault
managesdk -getNewProfileDefault
managesdk -listEnabledProfileAll

Example output:
>cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin
$
> managesdk -getCommandDefault
CWSDK1006I: COMMAND_DEFAULT_SDK = 1.8_64                        
CWSDK1001I: Successfully performed the requested managesdk task.
$
> managesdk -getNewProfileDefault                                 
  CWSDK1007I: New profile creation SDK name: 1.8_64              
  CWSDK1001I: Successfully performed the requested managesdk task.
  $                                                              
> managesdk -listEnabledProfileAll
CWSDK1004I: Profile WAS85 :                                 
CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64                       
CWSDK1008I: Node AS400_WAS85 SDK name: 1.8_64            
CWSDK1009I: Server WAS85 SDK name: 1.8_64                  
CWSDK1009I: Server IHS_WEBSERVER SDK name: 1.8_64             
CWSDK1001I: Successfully performed the requested managesdk task.
$
8.
Once you have verified your command and new profile defaults and all profiles are using SDK 8.0, you can proceed to start your WebSphere Application Server instances.
<edition> = Express, Base, ND
<appServer> = Name of the application server instance
<profile> = Name of the WAS profile
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
startServer <appServer> -profileName <profile>
Your v8.5.x WebSphere Application Servers will now start using SDK 8.0.  You can use the WRKJVMJOB Option 5 CL command to verify the JVM version used by WAS JVM jobs.

Related Information

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"WebSphere Application Server v8.5.x","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"v8.5.x","Edition":"Express, Base, and Network Deployment (ND)","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 March 2021

UID

ibm10796142