Thursday, 14 June 2012

Patching IBM HTTP Server and WebSphere Plugin Java SDKs

  When patching a WAS environment, there are four things that we usually patch: -

  • IBM HTTP Server
  • IBM WebSphere Plugin
  • IBM WebSphere Java Software Development Kit (SDK)
  • IBM WebSphere Application Server

but we often forget that there are two other Java SDKs to patch: -

  • IBM HTTP Server Java SDK ( /opt/IBM/HTTPServer/java/jre )
  • IBM WebSphere Plugin Java SDK ( /opt/IBM/HTTPServer/Plugin/java/jre )

The Plugin can use the same Java SDK fix pack as WAS, but you may well find that the IHS SDK needs a different one.

This will be definitely be the case for 64-bit Linux, as IHS is only available as a 32-bit binary, and the SDK will have the same "bitness".

As an example, here's a before and after for an IHS SDK update: -

Before applying the WAS 7.0.0.17 Java SDK fix

 $ /opt/IBM/HTTPServer/java/jre/bin/java -version

java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr2-20080818_01(SR2))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20080816_22093 (JIT enabled, AOT enabled)
J9VM - 20080816_022093_lHdSMr
JIT  - r9_20080721_1330ifx2
GC   - 20080724_AA)
JCL  - 20080808_02

After applying the WAS 7.0.0.17 Java SDK fix

$ /opt/IBM/HTTPServer/java/jre/bin/java -version

java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr9fp1ifix-20110401_01(SR9 FP1+IZ95392+IZ95393+IZ97453))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
J9VM - 20110216_075791
JIT  - r9_20101028_17488ifx4
GC   - 20101027_AA)
JCL  - 20110401_02

I'll add more details about the other fixes later ....

No comments:

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="{...