Originally posted on IBM Developer blog “Exploring PureApplication System, Software Service and more” by Hendrik van Run on 25 January 2017 (9949 visits)
Fixpack 11 for WAS 8.5.5 was released on 23 December 2016, so a number of clients have a desire to use this when building building out new infrastructure. However when using version 2.2.2.0 of the WebSphere Application Server Patterns on PureApplication and Bluemix Local System 2.2.2, the only way to install WAS 8.5.5.11 is to:
- Import WAS 8.5.5 Fixpack 11 into your Installation Manager repository
- Deploy a pattern instance using a WAS 8.5.5.10 software component
- Upgrade to WAS 8.5.5.11 after deploying the pattern instance using the Instance Console
Applying WAS 8.5.5.11 a patch on top of WAS 8.5.5.10 or earlier works fine, because the Java installation is already in place in that case. However when you attempt to deploy a pattern instance using a WAS 8.5.5.11 software component directly, it will fail with the following error in the trace.log:
[Wed 18 Jan 2017 08:25:58 PM UTC] vsys/im.py 140667681728256 pid=15292 DEBUG Run IM cmd : sudo -u virtuser /home/virtuser/IBM/InstallationManager/eclipse/tools/imcl -acceptLicense input /opt/IBM/maestro/agent/usr/servers/OS_Node.11484770835603/scripts/Appserver/responsec.xml -log product_install.log -variables wasProfile=V8x,eclipseCache=/opt/IBM/InstallationManager_AppServer_Shared,web20Home=/opt/IBM/WebSphere/Web20Mobile,wctHome=/opt/IBM/WebSphere/Toolbox,wasBitness=64,wasArch=x86,ws=gtk,wasRepositoryURL=http://IBMWorkloadDeployer:8585/IMRepository/Compo,wasHome=/opt/IBM/WebSphere/AppServer,wasOfferingId=com.ibm.websphere.ND.v85,wasOfferingVersion=8.5.5011.20161206_1434,arch=x86,osType=linux -secureStorageFile/home/virtuser/IBM/InstallationManager/eclipse/tools/credential.store -masterPasswordFile/home/virtuser/IBM/InstallationManager/eclipse/tools/master_password_file.txt [Wed 18 Jan 2017 08:25:58 PM UTC] maestro 140667681728256 pid=15292 DEBUG WARNING: shell=True used for subprocess command execution; might be insecure. [Wed 18 Jan 2017 08:26:13 PM UTC] vsys/im.py 140667681728256 pid=15292 DEBUG rc is 1 [Wed 18 Jan 2017 08:26:13 PM UTC] vsys/im.py 140667681728256 pid=15292 DEBUG out is ERROR: Support for using Java SE 6 with WebSphere Application Server ends in April 2018. Java SE 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 6, but no service can be provided after the end of support date, which could expose your environment to security risks. You must specify the default Java SDK version on the 'user.wasjava' property. To install the Java 8 SDK, specify '-properties user.wasjava=java8'. To install the Java 6 SDK, specify '-properties user.wasjava=java6'. [Wed 18 Jan 2017 08:26:13 PM UTC] stdout 140667681728256 pid=15292 DEBUG Installation Error: <class 'maestro.debugUtil.CallError'> <traceback object at 0x25405a8> [Wed 18 Jan 2017 08:26:13 PM UTC] invoker 140178774116096 pid=15862 DEBUG Start: /opt/IBM/maestro/agent/usr/servers/OS_Node.11484770835603/scripts/Part/stop.py
Because IBM Java 6.0 SE in WebSphere Application Server V8.5 will reach End of Service (EOS) in September 2017, from version 8.5.5.11 the WebSphere installation process now requires you to explicitly specify which Java version to install (i.e. Java 6.0 SE or Java 8.0 SE). That is the reason that deployment of a pattern instance using the WAS 8.5.5.11 software component fails when using the 2.2.2.0 WebSphere Application Patterns.
There is good news however. IBM released version 2.2.3.0 of the WebSphere Application Server Patterns in December 2016. This version includes support for the aforementioned change in the WebSphere installation process. You can find more details about this here in the WebSphere Application Server Patterns Knowledge Center.
Note: Unlike with the version 2.2.2.0 release of the WebSphere Application Server Patterns, version 2.2.3.0 does not requires your PureApplication or Bluemix Local System to be on 2.2.3.0 firmware. As long as you are on 2.2.2 firmware, you should be able to download and import the 2.2.3.0 WebSphere Application Server Patterns.
Refer to the Release information for WebSphere Application Server Patterns for links to download the 2.2.3.0 pattern types:
- WebSphere Networkk Deployment 2.2.3.0 pattern type
- WebSphere Base 2.2.3.0 pattern type
- WebSphere Liberty Core 2.2.3.0 pattern type
IBM Cloud Pak System 