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 OS.
Environment
IBM i 7.1, 7.2, 7.3, 7.4 OS
5770JV1 Option 16 & 17
IBM WebSphere Application Server v8.5.x All Editions
Steps
| 1. |
Open a 5250 Telnet Client session to your IBM i server.
|
| 2. |
Ensure JDK 8.0 LPPs 5770JV1 Option 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 your IBM WebSphere Application Server (WAS) product is at 8.5.5.9 Fix Pack version or newer.
To determine your currently installed WAS Fix Pack version, follow these steps:
<edition> = Express, Base, ND
<?xml version="1.0" encoding="UTF-8"?>
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 newer before you can change your WAS product and profiles to use JDK 8.0. Information on how to install a WAS v8.5.x Fix Pack on the IBM i OS can be found here .
|
| 4. |
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.
|
| 5. |
End all v8.5.x WebSphere Application Servers.
<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
Repeat the stopServer command for each active application server instance. You can view all active v8.5.x application server instances using the"WRKACTJOB SBS(QWAS85)" CL command. If an application server is not ending using the stopServer script, you can use "ENDJOB JOB(x/x/x) OPTION(*IMMED)" CL command to end the job immediately.
|
| 6. |
Execute the following Qshell commands to change your WAS v8.5.x product and profiles to use JDK 8.0.
<edition> = Express, Base, ND
<sdk> = 1.8_32, 1.8_64
NOTE: IBM recommends using the 1.8_64 SDK version for WAS v8.5.x.
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
Express and Base Editions
managesdk - enableProfileAll -sdkname <sdk> -enableServers
Network Deployment Edition
NOTE: For a Deployment Manager and Federated Node topology, you will need to change the JDK version for the Deployment Manager profile(s) first. Then, you will need to start the Deployment Manager profile(s) before you change the JDK version for the Federated Nodes.
managesdk -enableProfile -profileName <dmgr> -sdkname <sdk> -enableServers
startManager -profileName <dmgr>
managesdk -enableProfileAll -sdkname <sdk> -enableServers
Example for WAS v8.5 Express and 1.8_64 (JDK 8.0 64bit)
cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin
Example for WAS v8.5 ND and 1.8_64 (JDK 8.0 64bit)
cd /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin |
| 7. |
Verify your WAS v8.5.x product and profiles are now using SDK name 1.8_32 or 1.8_64 (JDK 8.0).
<edition> = Express, Base, ND
cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin
Example output:
> cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin |
| 8. |
Once you have verified your command and new profile defaults and all profiles are using JDK 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
Your v8.5.x WebSphere Application Servers will now start using JDK 8.0. You can use the WRKJVMJOB Option 5 CL command to verify the JVM version used by WAS JVM jobs.
|
| 9. |
If you are performing the above steps in preparation for an IBM i OS VRM upgrade, you will need to complete one of items below AFTER you upgrade your IBM i OS to 7.2, 7.3, or 7.4. NOTE: This is a post-migration step and is required to update the WAS *PGM/*SRVPGM objects to be compatible with the new IBM i OS VRM.
1) Install a new WAS v8.5 Fix Pack version.
Refer to the IBM Technical Document, How To Install an IBM WebSphere Application Server (WAS) v8.0 and v8.5 Fix Pack Using the IBM Web Administration for i Console, for more information on how to install a WAS v8.5 Fix Pack. 2) Execute the WAS _postfpexit script. - Sign into a 5250 Telnet client session with an IBM i user profile with *ALLOBJ explicit special authority. - Ensure the IBM i system value QALWOBJRST is set to *ALL. CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL) - Stop all WAS v8.5 application servers for the WAS v8.5 product installation Run the Qshell command /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin/stopServer -profileName <profile> for each WAS profile that is currently started. You can see which servers are started using the WRKACTJOB SBS(QWAS85) command. - Execute the _postfpexit script. STRQSH cd /QIBM/ProdData/WebSphere/AppServer/V85/<edition>/bin _postfpexit /QIBM/ProdData/WebSphere/AppServer/V85/<edition> where <edition> = Express, Base, ND i.e.
STRQSH
cd /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin _postfpexit /QIBM/ProdData/WebSphere/AppServer/V85/Express |
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"WebSphere Application Server","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V8.5.x","Edition":"Express, Base, and Network Deployment (ND)","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"}}]
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
ibm10795736