Thursday Feb 12, 2009
Tuesday Feb 10, 2009
By sunabl on Feb 10, 2009
Monday Oct 06, 2008
By sunabl on Oct 06, 2008
For WebSphere Application Server (WAS) on Solaris, IBM bundles it with the Sun JVM that contains IBM's modifications (e.g. IBM ORB, XML and Security libraries) as explained in this blog entry by my colleague Dileep Kumar of Sun.
More specifically, you can find the summary of WAS and its Java versions in the table below. Additional details can be located at this IBM site.
|WAS v7.0||Java EE 5||JDK/JRE 6|
|WAS v6.1||J2EE 1.4||JDK/JRE 5|
|WAS v6.0.2||J2EE 1.4||JDK/JRE 1.4.2|
|WAS v5.1.1||J2EE 1.3||JDK/JRE 1.4.2|
|WAS v5.1||J2EE 1.3||JDK/JRE 1.3.x|
In order to tune WAS JVM on Solaris, it is greatly helpful if you understand the performance tuning aspects of Sun JVM such as Java memory management, Garbage Collectors, etc. You can get performance whitepapers for respective JVM versions here and Java Memory Management Whitepaper. Dileep also has blogged about specific recommended JVM options for WAS on Solaris here.
Finally, there are numerous Sun JVM options and one of the references that I strongly recommend is the collection compiled by Joseph D. Mocker of Sun Microsystem. Of course, we have much more specific information about WAS v6.1 on Solaris 10 in this IBM Redbook (e.g. Chapter 9).
Mostly pertaining to Cloud Computing, Application Infrastructure, Oracle Exastack, Exalogic, Solaris, Java and Sun servers for the enterprise!
- Deploying Oracle RAC DB 11gR2 on LDoms Virtualization
- JDK 6 Performance Features and Update
- JDK 6 Performance Update, WAS v7, Fix Pack 7, and the G1 Collector
- WebSphere Portal Server Scalability on the Solaris 10 CMT Platform
- JavaOne 2009 Recap
- Come see us at Impact 2009
- Solaris Network Tuning for WebSphere Application Environment
- March 24 Invitation to Global WebSphere Community Jam
- Typical data needed for WebSphere performance analysis on Solaris
- Co-locating multiple instances of WebSphere on scalable Sun servers