Flashes (Alerts)
Abstract
Required action when upgrading to WebSphere Application Server for z/OS Fix Pack 8.5.5.14 or later, since application of Fix Pack 8.5.5.14 will remove any Java 6 SDK from the product directories.
Content
The following information is applicable for customers upgrading from WebSphere Application Server for z/OS Version 8.5 Fix Pack level 8.5.5.13 or below to Fix Pack level 8.5.5.14 or higher .
Because Java SDK 6 is now out of service, application of Fix Pack 8.5.5.14 to WebSphere Application Server for z/OS Version 8.5 will remove any Java 6 SDK in the product's /java and /java64 directories, and replace them with 31-bit and 64-bit copies of Java 8.
If all copies of WebSphere Application Server for z/OS V8.5 were installed with Installation Manager property user.wasjava=java8, you will be unaffected by this change.
However, if there are any WebSphere Application Server V8.5 nodes currently running on copies of WebSphere Application Server code that were installed with user.wasjava=java6, you must upgrade these nodes as follows to ensure that they start correctly.
Perform the following steps on each WebSphere Application Server node. Upgrade any Deployment Managers FIRST.
1.Shut down the target node, then remount product filesystems or change symlinks so that it will start on Fix Pack 8.5.5.14 or later.
2. Before starting any servers in the node, log in to the Unix System Services shell with the cell admin user ID, and run the following commands:
cd <WAS 8.5.5.14_Install_image_location>/bin/sdk
./setupProfileSDK.sh <WAS_HOME>/properties/profileRegistry.xml
This will update the node definition to use the new embedded Java 8.0.
NOTE: After running setupProfileSDK.sh, check the output for the following messages which indicate that the script ran successfully:
CWSDK1022I: New profile creation will now use SDK name 1.8_64_bundled.
CWSDK1001I: Successfully performed the requested managesdk task.
CWSDK1001I: Successfully performed the requested managesdk task.
If these messages are not present, ensure the script is run from a userid with cell admin authority.
- For a Network Deployment cell, upgrade and start the Deployment Manager, then upgrade each managed node.
- For a Standalone Application Server, simply upgrade the server with the setupProfileSDK.sh command and then start it.
As with any system change, you should back up your configuration file systems before and after making any configuration change.
NOTE: The above process does not ensure that your applications will run correctly with Java 8. You should either migrate your servers and applications to Java 7, Java 7.1, or Java 8 before applying Fix Pack 8.5.5.14, or verify by some other method that your applications are compatible with Java 8.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"8.5.5.14","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
26 September 2022
UID
ibm10794207