Thursday, 13 November 2014

More on WebSphere Application Server Java Versions

Following on from a discussion with one of my colleagues - who hit the precise same problem that I outlined here: -


when creating some JEE code for IBM Operational Decision Manager (ODM), I thought I'd add a bit more detail about the Java version supplied with a popular IBM product, IBM Business Process Manager 8.5.0.1.

So we have BPM Advanced 8.5.0.1 deployed here, on top of WebSphere Application Server 8.5.5.2 as evidenced here: -

/opt/ibm/WebSphere/AppServer/bin/versionInfo.sh


Name                  IBM Business Process Manager Advanced
Version               8.5.0.1
ID                    BPMPC
Build Level           20131107-140634
Build Date            11/7/13
Package               com.ibm.bpm.ADV.v85_8.5.1.20131107_1830
Architecture          PPC64
Installed Features    Business Process Manager Advanced Process Server Non-production
Name                  IBM WebSphere Application Server Network Deployment
Version               8.5.5.2
ID                    ND
Build Level           cf021414.01
Build Date            4/8/14
Package               com.ibm.websphere.ND.v85_8.5.5002.20140408_1947
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

….


Therefore one might assume that we also have the latest available Java JDK/JRE, namely Java 7 aka Java 1.7.0 ??

Nope, as evidenced here: -

/opt/ibm/WebSphere/AppServer/java/jre/bin/java –version

java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr7fp1ifix-20140220_01(SR7 FP1+IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20131230_180580 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR7_20131230_1725_B180580
JIT  - r11.b05_20131003_47443.02
GC   - R26_Java626_SR7_20131230_1725_B180580_CMPRSS
J9CL - 20131230_180580)
JCL  - 20140107_01


/opt/ibm/WebSphere/AppServer/java/bin/java –version

java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr7fp1ifix-20140220_01(SR7 FP1+IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20131230_180580 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR7_20131230_1725_B180580
JIT  - r11.b05_20131003_47443.02
GC   - R26_Java626_SR7_20131230_1725_B180580_CMPRSS
J9CL - 20131230_180580)
JCL  - 20140107_01


Easy when you know :-)

Furthermore, this shows you what SDKs are available: -

/opt/ibm/WebSphere/AppServer/java/bin/managesdk.sh -listAvailable

CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.6_64
CWSDK1001I: Successfully performed the requested managesdk task.


This is the GUI alternative: -


and this shows what's available to install: -

/opt/ibm/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/SWGRepo/WAS85/Base/Product -features -long

/mnt/SWGRepo/WAS85/Base/Product : com.ibm.websphere.BASE.v85_8.5.0.20120501_1108 : IBM WebSphere Application Server : 8.5.0.0 : core.feature,ejbdeploy,thinclient,embeddablecontainer,samples,liberty,com.ibm.sdk.6_32bit,com.ibm.sdk.6_64bit

In other words, we only have the 32-bit and 64-bit Java 6 SDKs with which to play.

Java 7 can be downloaded as part of WAS 8.5.5.X, as per this: -



However, it's not clear to me ( and I've not investigated ) whether IBM BPM, ODM etc. actually support Java 7.

In other words, Your Mileage May Vary (YMMC)





Want to know more about Java and WAS ? Read here ....




2 comments:

SherpaPsy said...

I've heard, from a very reliable source, that Connections 5 does not currently work with Java 1.7.

Dave Hay said...

Ah, OK, so the same may be true for other products that sit astride WAS. Just because one CAN use Java 7, doesn't mean that one SHOULD use it.

If in doubt, check the System Requirements page e.g.

System Requirements for IBM Connections 5

and/or raise a PMR with IBM Support.

Thanks for the tip, Dave

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...