Was 8 0 java support

Installing Java SDK 8.0 on WAS 8.5.5.x

NOTE: Java SDK 6, going out of support, is embedded in WebSphere Application Server traditional V8.5 as the default Java SDK. Review details on WebSphere Application Server traditional: Support ends in April 2018. The end of Java SE 6: Where to go from here

Liberty: Support ends on September 2017 and that fix pack (17.0.0.3) will be compiled at the Java 7 level, so will not run. In this blog we will cover WebSphere Application Server traditional in detail.

Existing users updating from previous a fix pack continue to have embedded Java SDK 6 until Java SDK 6 goes End Of Support in April 2018. The next fix pack for 8.5.5.x shipped after April 2018 will replace the default Java SDK 6 with Java SDK 8.0. A warning message will be displayed in the GUI or console and also in the install log if users install or update with embedded Java SDK 6.

New installation of 8.5.5.11 has an option to install with embedded Java SDK 6 or embedded Java SDK 8. The default selection is Java 8 in GUI mode. Users need to explicitly select Java SDK 8 or Java SDK 6 for command line installs.

In this blog we will cover both new and existing Installs along with the options available.

New Install of 8.5.5.11

1. Command Line

New property (via –properties) to choose between Java SDK 8 or Java SDK 6 as the embedded SDK for new installs: user.wasjava=java8 or user.wasjava=java6

• AppServer and AppClient, this property must be specified.
• Supplemental offerings, such as WCT, IHS and PLUGINS, the property value will be default to Java SDK 8 if user.wasjava=java6 not specified.

Sample command to install WebSphere Application Server ND 8.5.5.11 with Java SDK 8 as default:

imcl install com.ibm.websphere.ND.v85_8.5.5011.20161206_1434,core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ibm.sdk.6_64bit -installationDirectory

C:\IBM\WebSphere\AppServer -repositories C:\Rep855,C:\Rep8511 -acceptLicense -showProgress -properties user.wasjava=java8 -preferences

• WebSphere Application Server 8.5.5 Repository : C:\Rep855
• WebSphere Application Server 8.5.5.11 Repository : C:\Rep8511

2. Using Response File

Here is sample response file which can be used to install WebSphere Application Server (Base) 8.5.5.11 with Java SDK 8 as default:

3. Graphical Installation

Add WebSphere Application Server 8.5.5 and fix pack 8.5.5.11 repository to Installation Manager Repositories (File — Preferences — Repositories — Add Repository)

The default is Java SDK 8 unless you select Java SDK 6 as shown in screen shot below:

This is same option for supplemental offerings, such as WCT, IHS and PLUGINS during Graphical Install.

If you install 8.5.5.11 with default Java SDK 8 that is at 8.5.5.11 or higher with above options, then for any Java ifix install the Java SDK 8 ifix that has the naming convention for WebSphere Application Server traditional 8.5.5 embedded Java SDK 8.

iFix – v.r.m.f-WS-[WASJavaSDK | WASBundledJavaSDK8]-[Platform-Arch]-[IFapar-number]

– [java8] 8.5.5.11-WS-WASBundledJavaSDK8-AixPPC64-IFPIxxxxx

– [java6] 8.5.5.11-WS-WASJavaSDK-AixPPC64-IFPIxxxxx

Embedded Java SDK 8 iFix cannot be installed in an installation with embedded Java SDK 6.

Existing Install of 8.5.5.10 or less

When applying fix pack 8.5.5.11 warning message will appear during the install:

WARNING: Your default Java SDK is Java SE 6. After April 2018, service for Java SE 6 can no longer be provided, which could expose your environment to security risks. To stay current and reduce the risk of security exposures, update to Java SE 8 using one of the following options:

— Install WebSphere Application Server 8.5.5.11 or later with Java SE 8.

— Migrate to WebSphere Application Server traditional Version 9. WARNING: Your default Java SDK is Java SE 6. After April 2018, service for Java SE 6 can no longer be provided, which could expose your environment to security risks.

To stay current and reduce the risk of security exposures, update to Java SE 8 using one of the following options:

— Install WebSphere Application Server 8.5.5.11 or later with Java SE 8.

— Migrate to WebSphere Application Server traditional Version 9.

This message is only valid for WebSphere Application Server (ND, Base, Express). This can be ignored for Supplemental Offerings (IHS, Plugin, WCT and AppClient). Java is not used by IBM HTTP Server and IBM Plugin for runtime. It is just used by the «configuration related scripts» that are included with these offerings. IBM HTTP Server uses Java SDK for ikeyman also.

The warning message shown during install of fix pack on IBM HTTP Server and IBM Plugins can be ignored. The next fix pack shipped after April 2018 will be packaged to replace Java SDK 6 shipped with IHS and Plugin to supported Java (most likely Java SDK 8). For WebSphere Application Server (ND/BASE/ Express) clients should consider to move to Java SDK 7 or higher (Java SDK 8 is recommended) as soon as possible because applications need to be tested on new Java SDK. This is the prime reason why a warning message is being shown so it gives enough time to test and upgrade Java on WebSphere Application Server.

Please ensure your operating System is supported for Java SDK 8.0 as per prerequisite as noted in the link below :
http://www-01.ibm.com/support/docview.wss?uid=swg27045339

Once Java SDK 6.0 is end of support the OS will also need to be supported to support Java SDK 8.0.

For more details on install of optional Java SDK 7.x on WebSphere Application Server 8.5.x please review my previous blog, Installing optional Java SDK 7.x on WebSphere Application Server 8.5.

For Java SDK 8 on existing install please download Java SDK 8 from 8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 and use managesdk command as mentioned in above blog to switch to Java SDK 8.

Источник

Switching to JAVA SDK 8.0 from JAVA SDK 7.1 on WAS 8.5.5.x

Before trying to update/upgrade the running JAVA SDK on WAS 8.5.5.x you need to check whether your setup is fulfilling the minimum requirements or not. Fix Pack 9 or higher should be applied to your WAS to switch the JAVA SDK 8.0 from JAVA SDK 7.1. In my case, fix pack 12 was applied on WAS 8.5.5 and OS was RHEL 6.8.

Below are the minimum requirements for upgrading the JAVA SDK from 7.1 to 8.0.

Minimum Supported Operating Systems

Linux:

AIX:

HP-UX:

IBM i:

Minimum Fix Pack Level

• The minimum fix pack required for JAVA SDK 8.0 is Fix Pack 9 i.e. your WAS version should be 8.5 .5.9 or above.

End of Support Dates dor JAVA SDKs:

• Java 6 in traditional WAS V8.5: April 30, 2018
• Java 7 in traditional WAS V8.5: September 30, 2019

Follow the steps given below to switch to JAVA 8.0 if your WAS is running on JAVA 7.1. To manage the JAVA SDK on WAS 8.5.5.x you can use the managesdk command.

First, check all versions of the installed JAVA SDK for your system WAS 8.5.5.x.

List all installed JAVA SDK

Use the below command to list all the versions of JAVA SDK installed on your server. There may be only one or maybe more. WAS 8.5.5.0 comes with JAVA SDK 6.0 i.e. 1.6.

[root@DEVWAS1 bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@DEVWAS1 bin]# ./managesdk.sh -listAvailable CWSDK1003I: Available SDKs : CWSDK1005I: SDK name: 1.8_64 CWSDK1005I: SDK name: 1.6_64 CWSDK1005I: SDK name: 1.7.1_64 CWSDK1001I: Successfully performed the requested managesdk task. [root@DEVWAS1 bin]#

Now you have to check the running version of the JAVA on your WAS 8.5..5.x.

Running version of JAVA SDK

Use the below command to check the running version of the JAVA with profiles and dmgr.

[root@DEVWAS1 bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@DEVWAS1 bin]# ./managesdk.sh -listEnabledProfileAll CWSDK1004I: Profile DeploymentManager : CWSDK1006I: PROFILE_COMMAND_SDK = 1.7.1_64 CWSDK1008I: Node CellManager01 SDK name: 1.7.1_64 CWSDK1009I: Server dmgr SDK name: 1.7.1_64 CWSDK1004I: Profile Profile01 : CWSDK1006I: PROFILE_COMMAND_SDK = 1.7.1_64 CWSDK1008I: Node DEVWAS1Node01 SDK name: 1.7.1_64 CWSDK1009I: Server nodeagent SDK name: 1.7.1_64 CWSDK1009I: Server Mem01 SDK name: 1.7.1_64 CWSDK1004I: Profile Profile02 : CWSDK1006I: PROFILE_COMMAND_SDK = 1.7.1_64 CWSDK1008I: Node DEVWAS1Node02 SDK name: 1.7.1_64 CWSDK1009I: Server Mem02 SDK name: 1.7.1_64 CWSDK1009I: Server nodeagent SDK name: 1.7.1_64 CWSDK1001I: Successfully performed the requested managesdk task.

As we can see from the above commands that JAVA 6.0, JAVA 7.1 and JAVA 8.0 are available on our WAS server and our running version of JAVA in JAVA 7.1. Now we need to switch the JAVA for profiles and dmgr from JAVA 7.1 to JAVA 8.0.

The following example demonstrates the sequence of commands to use to list profiles and the SDKs they use, list available SDKs, change the default SDK to a Version 8.0 SDK and, if profiles exist already, enable the profiles to use the Version 8.0 SDK.

Set the command default to the Version 8.0 SDK:

[root@DEVWAS1 bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@DEVWAS1 bin]# ./managesdk.sh -setCommandDefault -sdkname 1.8_64 CWSDK1021I: The command default SDK name is now set to 1.8_64. CWSDK1001I: Successfully performed the requested managesdk task. [root@DEVWAS1 bin]# 

Set the new profile default to the Version 8.0 SDK:

[root@DEVWAS1 bin]# ./managesdk.sh -setNewProfileDefault -sdkname 1.8_64 CWSDK1022I: New profile creation will now use SDK name 1.8_64. CWSDK1001I: Successfully performed the requested managesdk task. [root@DEVWAS1 bin]# 

If profiles already exist, enable the profiles to use the Version 8.0 SDK:

[root@DEVWAS1 bin]# ./managesdk.sh -enableProfileAll -sdkname 1.8_64 

If the above command does not work then pass the -user and -password parameters as given below. In my case, it worked with the -user and -password parameters. Please note that node agents should be running if you are updating the JAVA SDK for the profiles which already exist.

[root@DEVWAS1 bin]# ./managesdk.sh -enableProfileAll -sdkname 1.8_64 -enableServers -user wasadmin -password wasadmin CWSDK1017I: Profile DeploymentManager now enabled to use SDK 1.8_64. CWSDK1024I: The node default SDK setting for federated profile Profile01 has been saved in the master configuration repository. CWSDK1025I: A synchronization operation is required before configuration changes to federated profile Profile01 can be used. CWSDK1017I: Profile Profile01 now enabled to use SDK 1.8_64. CWSDK1024I: The node default SDK setting for federated profile Profile02 has been saved in the master configuration repository. CWSDK1025I: A synchronization operation is required before configuration changes to federated profile Profile02 can be used. CWSDK1017I: Profile Profile02 now enabled to use SDK 1.8_64. CWSDK1001I: Successfully performed the requested managesdk task. [root@DEVWAS1 bin]# 

Now again use the ./managesdk.sh -listEnabledProfileAll command to check whether JAVA SDK updated to version 8.0 or not.

JAVA SDK updated to version 8.0

[root@DEVWAS1 bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@DEVWAS1 bin]# ./managesdk.sh -listEnabledProfileAll CWSDK1004I: Profile DeploymentManager : CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64 CWSDK1008I: Node CellManager01 SDK name: 1.8_64 CWSDK1009I: Server dmgr SDK name: 1.8_64 CWSDK1004I: Profile Profile01 : CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64 CWSDK1008I: Node DEVWAS1Node01 SDK name: 1.8_64 CWSDK1009I: Server nodeagent SDK name: 1.8_64 CWSDK1009I: Server Mem01 SDK name: 1.8_64 CWSDK1004I: Profile Profile02 : CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64 CWSDK1008I: Node DEVWAS1Node02 SDK name: 1.8_64 CWSDK1009I: Server nodeagent SDK name: 1.8_64 CWSDK1009I: Server Mem02 SDK name: 1.8_64 CWSDK1001I: Successfully performed the requested managesdk task. [root@DEVWAS1 bin]# 

Note: The above activities were done on WebSphere Application Server ND 8.5.5.12 running on RHEL 6.8.

Источник