Wednesday Jan 31, 2007


If you are planning to either setup a website or enhance your current website, you can give Sun's latest Web Server (formerly known as Sun ONE Web Server or iPlanet Web Server) - Sun Java System Web Server 7.0 a try. If you haven't downloaded it, here is the link to download and use it for free ! and here is the What'z New in the release.

These days, I do most of my regular Web Server 7.0 administration tasks using its rich command line interface(CLI).  Hey, I know Web Server 7.0 has a nice GUI as well. It is just that I am not a big GUI person. So, I thought I should write a quick blog on how I use it. Hopefully, some one finds this useful.

The way to kick of the Web Server 7.0 Administration Server is by running the following command

cd <Web Server 7.0 installation root>
bin/wadm --user=<administration login username>  --password= <administration login password>

If you hate typing the above line frequently, then on UNIX / Linux platforms, you can set <Web Server 7.0 installation root/bin> to your PATH  For example, you would do something like
export PATH=$PATH:/sun/webserver7/bin (in sh or bash shell)

On Windows, you will need to do update the 'Path' environment variable with the location of  Web Server 7.0\bin directory. How to Manage Environment Variables in XP link can provide you with insight on how to update the 'Path' variable. You will need to append the 'Path' environment variable to look something like Path=%Path%;"c:\Program Files\Sun\WebServer7\bin"

where  <administration login username> => user name that you chose at the time of installation.
and      <administration login password> => login password that you chose at the time of installation.

Normally, I very much want to reduce my typing in the keyboard and would like to get my job done with as little typing as possible. So, for guys like me, Web Server 7.0 Administration Server allows to save the commonly used command line parameters like 'user name', 'password', 'configuration name' and 'nodename' so that we don't have to type these things frequently.

This is how you can save this information to save you from typing these things repeatedly when you login to the administration server

-> Use your favorite editor and create a file a '.wadmrc' under your home directory. For windows users, this file will need to be created under %HOMEPATH% . Typically, %HOMEPATH% will expand to 'C:\Document and Settings\ on Windows XP. To find the location of your '%HOMEPATH%'. you will need to open a command line windows (Start->Run->cmd) and then type echo %HOMEPATH%

-> Add the following lines to this newly created file


set wadm_user           <Your administrator login user name Example: admin>
set wadm_password  <Your administrator login password  Example: adminadmin>


-> Now save this file and ensure that only 'you' have access to read this file.

On UNIX / Linux platforms, you can do something like chmod 400 $HOME/.wadmrc

The above step is a very important thing to do. You don't want to have other prying eyes to get control of your site's administrator server, do you ?

Though, Web Server 7.0 administration server has been designed from the ground up to manage multiple Web Server instances in a cluster like environment to handle loads like the one you get in web sites like MLB , it can very well manage my single configuration / instance running on Windows XP as well.  Well, if you are a typical customer who is using Sun Java System Web Server 7.0 with a single configuration deployed to a single machine, then you can add the following 2 lines as well to the '.wadmrc' file


set wadm_nodehost  <Your current hostname.domainname For Example natarajan.sun.com>
set wadm_config      <Your Web Server 7.0's configuration name or whatever the configuration that you frequently work with>

Note that Web Server 7.0 installer creates a default configuration that has the same name as your nodename (or hostname.domainname). Still, you can very well, easily create a new configuration using either CLI or GUI. Accordingly, you can update your '.wadmrc' file with the configuration that you frequently work with.

This blog copyright 2009 by natarajan