Thursday Mar 06, 2008

New Redbook Published: "WebSphere Application Server V6.1 on the Solaris 10 Operating System"

SG247584 Redbook Cover The final version of the Redbook titled "WebSphere Application Server V6.1 on the Solaris 10 Operating System" has been published. In this book, we document how WebSphere Application Server V6.1 and Solaris 10 can be configured, optimized, and managed. We described how to virtualize and manage WAS installation, deployment strategies and scenarios, the advanced features of Solaris 10 (e.g. SMF, Resource Management, Process Rights, Containers and Zones, ZFS, DTrace), the differences of WAS on Solaris from other platforms (e.g. Sun JDK), how to monitor and tune WAS along with Sun JVM, Solaris, and much more.

I personally would like to thank to all those from both Sun and IBM sides who helped make this project happened as well as those who participated and contributed on the project. I am very appreciative of those reviewers from various Sun and IBM engineering organizations who spent many hours for accuracy and correctness of the content. We tried our best to recognize them in the Preface of the book. If we inadvertently left any of you out, we apologize. I also am thankful for those who sent me great questions and feedback for the book from around the world.

Last but not the least, I must thank my family 'AAAA' for giving me love and support while I was working on the book many weeks and nights away from and at home. Without you, I couldn't have accomplished this. I love you all.

Finally, below are some comments we got so far for the book. Please feel free to send them along, rate it at the Redbook site, or comment here on the blog.

  • "Good informations, we use it a lot", "Excellent Redbook...very informative!"
  • " Good work.", "Great..We have been waiting for."
  • "Excellent", "Very useful, This Redbook is very useful for our Business Partners, because they need the information and technique how to configure/use WebSphere Application Server on Solaris 10 virtualization technology."

So, go download the following and make most use of your Solaris platform -- the best OS on the planet!


Friday Jun 15, 2007

A SMF Service Manifest for WebSphere Application Server on Solaris 10

Service Management Facility (SMF), introduced in Solaris 10, enables a unified model for services and service management on each Solaris system. It is a core part of the Predictive Self-Healing technology available in Solaris 10, which provides automatic recovery from software and hardware failures as well as administrative errors.

One of my colleagues at Sun, Bob Netherthon, has a very nice slide deck on SMF here.

Since many of our customers asked, I have created a basic service manifest and simple instructions for WebSphere Application Server (WAS) as an example.


  1. Put the service manifest file named "was61.xml" to a temporary directory /tmp.
  2. Put the service method file named "svc-was61" in /lib/svc/method/svc-was61.
  3. Edit this service method file to reflect the correct WAS path information, etc.
Follow the steps below.
    bash-3.00# chmod 755 /lib/svc/method/svc-was61
    bash-3.00# svccfg import /tmp/was61.xml
    bash-3.00# svcadm enable was61
    bash-3.00# svcs -l was61
    fmri         svc:/application/was61:was_server1
    name         WebSphere Application Server v6.1
    enabled      true
    state        online
    next_state   none
    state_time   Thu Jun 14 18:23:17 2007
    logfile      /var/svc/log/application-was61:was_server1.log
    restarter    svc:/system/svc/restarter:default
    contract_id  1819
    dependency   require_all/error svc:/milestone/network:default (online)
    dependency   require_all/none svc:/system/filesystem/local:default (online)
    dependency   optional_all/error svc:/system/filesystem/autofs:default (online)

Once you do "svcadm enable was61", WAS should start if the configuration is valid. The log file is located at: /var/svc/log/application-was61:was_server1.log.

If the service need to be removed, do the following:

    bash-3.00# svcadm disable was61
    bash-3.00# svccfg delete was61


Note that in the manifest, the exec_method was defined using the service method (e.g. external shell script: exec="/lib/svc/method/svc-was61 start"). This could be a WAS command itself (e.g. exec="/opt/IBM/WebSphere/AppServer/profiles/AppSvr01/bin/ start"). The service method is a good way to separate the WAS start up/shutdown commands because if you need to change the profile or WAS location for this application service, you just need to modify in the service method script rather than having to re-configuring the service manifest.

In the case you have multiple WAS profiles, applications or versions, this manifest can also be used as a template to create new service manifests (e.g. was61_tradeapp1, was602_storeapp1, etc.).

You can also add other dependencies in the service manifest that the WAS services rely upon (e.g. another standalone application that your application requires to be co-located on the same system or a JMS provider that must be started before the WAS services, etc.).

Another good practice is to have the WAS processes to be started by a non-root user, which you can configure accordingly like this example for Apache.

Best of all, look at OpenSolaris website for:

Finally, you should include useful and concise comments in the service manifest and methods for ease of maintenance.


Mostly pertaining to Cloud Computing, Application Infrastructure, Oracle Exastack, Exalogic, Solaris, Java and Sun servers for the enterprise!


« June 2016