Node:WAS, Next:, Previous:Introduction, Up:Top



Installing WAS Software and the Main Instance

For Solaris, I assume that your iPlanet web server is already installed and you have verified that it works. If you want my tips for installing and configuring IHS (IBM's Apache server) with WAS, email me.

Download the following files from the IBM web site or wherever.

  1. ae_offline_infocenter_en.zip
  2. ibmwas5_trial_for_*.zip

(The former is available at

ftp://ftp.software.ibm.com/software/websphere/info/appserv/v50/ae/ae_offline_infocenter_en.zip.
Make sure you get it because it is extremely difficult to install it afterwards).

Extract both of those files into an empty directory.

Become root.

SOLARIS ONLY Set the following kernel parameters in /etc/system and reboot.

     
         set shmsys:shminfo_shmmax = 4294967295
         set shmsys:shminfo_shmseg = 1024
         set shmsys:shminfo_shmmni = 1024
         set semsys:seminfo_semaem = 16384
         set semsys:seminfo_semmni = 1024
         set semsys:seminfo_semmap = 1026
         set semsys:seminfo_semmns = 16384
         set semsys:seminfo_semmsl = 100
         set semsys:seminfo_semopm = 100
         set semsys:seminfo_semmnu = 2048
         set semsys:seminfo_semume = 256
         set msgsys:msginfo_msgmap = 1026
         set msgsys:msginfo_msgmax = 4096
         set rlim_fd_cur=1024
     
     
Remove all core dump files from the /var/sadm/pkg directory.

Create the group mqm. (Use different integer if this one already in use). (Skip if in Linux, since Linux will do this automatically when you run the first useradd command below).

         groupadd -g 2001 mqm
     
Create the group mqbrkrs. (Use different integer if this one already in use).
         groupadd -g 2002 mqbrkrs
     
Create the user mqm
         useradd [-M] -d /dev/null -u 2001 -g 2001 -c Mqm -s /bin/false mqm
         # Give -M only in Linux
     
If <MAIN_OWNER> doesn't exist yet, then create that account, adding the user to the mqm and mqbrkrs shared groups.
         groupadd -u 1601 <MAIN_OWNER>    # Not needed for Linux
         useradd -d $WAS_HOME -c WebSphere -u 1601 -m -G mqm,mqbrkrs <MAIN_OWNER>
     
Create your <INST_OWNER> account if it doesn't already exist. Now edit the /etc/group file and add root, <MAIN_OWNER> and <INST_OWNER> to the following groups. (This makes it work. IBM's instructions do not).
         <MAIN_OWNER>
         mqm
         mqbrkrs
     

Log out and log back in as root (in order to pick up the new groups that you just added).

Cd to the directory into which you unzipped the files above and run ./install. You must run install as root since OS packages will be installed and because some mqm programs (at least) are made set-user.

  1. Accept all defaults except where noted here.
  2. Ignore warning about unsupported OS (if RH8.0)
  3. Change paths. I like /usr/local/ws-5.0.
  4. I recommend that you name your node "node" + your hostname with initial cap, like "nodeSaturn". This is to avoid confusing hostname with node name. This document hereafter uses <NODE> to refer to the node name.
  5. For host name, you need to use the name of an address that will always be available locally. I suggest that you allocate a static IP addr just for this purpose. (Everything listens to IPADDR_ANY by default. The problem is just that the queue client programs connect using this host name, so if it's not available the queue commands will fail).
  6. At the end, "install" will start the "First Steps" gui. This is just a pretty wrapper to view release notes, run the verifier, etc. Just close it (because any Admin needs to know how to run the important stuff without this Gui, and the other stuff is useless).

Edit the file $WAS_HOME/bin/setupCmdLine.sh. Search for the "ulimit" command and append "2>&-" to it (this command fails for normal non-super users).

LINUX ONLY
Add "/usr/local/ibm/gsk5/lib" to /etc/ld.so.conf and run "ldconfig -X". If /usr/lib/libdb.so.3 doesn't exist, then make a sym link

         ln -s libdb1.so.2 /usr/lib/libdb.so.3
     
(assuming that the former exists).

Chown the WAS software to <MAIN_OWNER>.

         chown -R <MAIN_OWNER>:<MAIN_OWNER> $WAS_HOME
     

Log in as <MAIN_OWNER> and do the following actions as <MAIN_OWNER>.

Run $WAS_HOME/bin/ivt.sh to verify the installation. (It should "fail to connect" and then start the app server).

Verify that the WAS admin console works.

         http://localhost:9090/admin
     
(Log in with any user name. No password required.)

Verify that a sample application works.

         http://localhost/snoop
     

Shut down the instance.

         $WAS_HOME/bin/stopServer.sh server1
     
You are finished installing the software and the main instance. (There's no need to configure this instance any more since we won't be using it for anything but testing).