Date Created: Sun 01-Feb-2009

Related Document Categories:

Get my WebSphere Application Server course here >>

Installing WebSphere on Redhat Linux

This document is a quick log of the actions I took on installing WebSphere 6.1 ND on RHEL running on a RHEL Virtual appliance downloaded from vmware.
Note: this walk through is by no means the only way and it will vary based on our RedHat version and configuration.It is more a log of what I did on this particular VMWare appliance. I have often found that the RedHAt appliances are only available for a short period of time and often get removed from VMWare and links are given to RedHa';s website were only downloads of DVD etc are available as opposed to pre-installed/configured VMware appliances.


When I installed I use sudo as configured


# Do not remove the following line, or various programs
# that require network functionality will fail. localhost.localdomain localhost websphere

# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# See the sudoers man page for the details on how to write a sudoers file.

# Host alias specification

# User alias specification

# Cmnd alias specification

# Websphere commands
#Cmnd_Alias WAS_CMDS = /apps/was61/wasinstall/install
Cmnd_Alias WAS_CMDS = ALL

# Defaults specification

# User privilege specification
root ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL

# Same thing without a password

# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
wasadm ALL=/apps/was61/wasinstall/WAS/, /etc/rc5.d/[A..z]

Using sudo allowed the installer to auto create the startup script for the deployment manager, I then chown the inst01 folder to wasadm:was -R inst01 to ensure that wasadm can access all resources in the instance. It is not good to leave the installation inst01 as root as wasadm cannot run tool like later for other nodes etc.

For an xclient I used xming, remember to use xforwarding on putty

What I did was edit the sudoer file using visudo as root

%was ALL= /apps/was61, /apps/was61/wasinstall, /apps/was61/wasinstall/WAS, /apps/was61/wasinstall/WAS/install

which allows me to runt he installation utility as root.

sudo ./install

This time I did not get the error message

I am not sure what file install users to find that another install of was nd has been installed? -> need to have a look

Here is where in an enterprise install you would be able to change the ports ie at my work we used 60000 for non functional test and 61000 for production

I chowned everything in the was61 down this is because when I started was group did not have access to /etc/rc5.d to create the startups script

su -

chown wasadm:was -R inst01

I then restated the dmgr

I go an error

[10/7/07 2:57:40:228 BST] 0000000a HostNameMap E HMGR0024W: An error was encountered while looking up the IP address for the host name of a core group member. The host name is and the exception is

This was because I had not edited localhost for, I messed up here.... I had entered the wrong host name, well I was drinking wine while I did this. ha

It is supposed to be websphere, I will have to edit the xmldocument

I edited serverindex.xml to fix my mistake replacing WebSphere with WebSphere

restarted dmgr again = sorted, gee I am good!!
could not get to 9060 to view administration console


/sbin/service iptables restart

if by accident you need to start xwindows login on server and cannot log out then use ..

logout xwindos ctrl-alt-bspace

I was now able to access 9060 and see the admin console

The node is already started

I made a mistake, the cell folder was not used for the node, need to delete the profile.


./ -delete -profileName node01

./ -validateAndUpdateRegistry


rm node01 -r to get rid of the old ndes profile ...

etc ..etc .. etc ..

check logs

job done

well almost cannot start node agent, thinks missing configuration? maybe the problem with my install method?

What I d id then was restart the install from scratch, this allowed me ot learn about using sudo.

find / -name WASRegistry

to find remove registry file

Also, gather the /opt/.ibm/.nif/.nifregistry file. Alternatively, this file may be located in the user's home directory, in a subdirectory named .nif.

Get my WebSphere Application Server course here >>

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many leading brands around the world. Steve specialises in JEE, DevOps and Thought Leadership.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.

  • Linked In
  • Twitter
  • About Me
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide


  • WebSphere Courses


WebSphere Categories

Other Categories