WebSphere JVM/JDK on Solaris
By dkumar on Apr 12, 2007
I have seen people getting confused about the version of Java Development Kit(JDK) with WebSphere Application Server (WAS) on Solaris.
Here is the details:
So far all the versions of WAS available on Solaris uses Sun JDK. Then you might be wondering why java -version output is something like this:
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_06-erdist-2006 0404 20060511)
Java HotSpot(TM) Server VM (build 1.5.0_06-erdist-20060404, mixed mode)
IBM Java ORB build orb50-20060511a (SR2)
XML build XSLT4J Java 2.7.4
XML build IBM JAXP 1.3.5
XML build XML4J 4.4.5
This tells us that this particular version of java is equivalent to 1.5.0_06 version of Sun's JDK. However there are pieces that has been either changed or modified some of them you can make out from above and they are:
- ORB has been replaced with something which comes from IBM SR2 release at the same level.
- For XML you can see various package has been replaced and I think names are quite descriptive and they have version information with them.
- Security Frameowrk
All of the above has been replaced by IBM implementation.
More details you can find in your WAS/Java install dir(/opt/IBM/WebSphere/AppServer/java) and the files to look for are:
- README_FIRST - Gives you all the information about the changes and known problems.
- ibmorbguide.htm - Gives you ORB details.
- securityguide.ref.htm - All the information about security implementation.
Now the question is can this JVM is upgraded using Sun JVM - As far as I understand all the updates to JVM/JDK comes as fix packs from IBM so if you violate that then support may not be available so it's not good idea to do that.
Of course, you are free to do whatever you want if you understand the pieces and ready to be on your own. You can replace and test with new version of libjvm.so or upgrade your JVM to higher version but making sure that the pieces that has been changed is incorporated following the docs I pointed out. But if you run into any problem you must figure out yourself because it is not supported and even if it works its not good idea for anything other than testing.