WebSphere v3.5 Install Notes
This web page contains notes from an install I did
to get familiar with the WebSphere family of products. This is just my
notes of which maybe you will find some helpful information. I decided to
share this knowledge after many installs, uninstalls, reading, and frantic
searching for information. This load process will take a full 8 hours
(more or less depending on how much you read and have problems).
I created these notes while installing on a Win NT 4.0 Server. At that
time you needed Service Pack 5 or higher. As I load on other platforms
I'll try to update the site.
- For non-IBMers try the evaluation/trial copies:
(NOTE: I would choose software versions around support for the
WebSphere version you plan on installing!)
- Install Platforms I've Installed & Tested:
Beware!!! Some of this software is very very version and Platform
specific!!! You may need to carefully read the look at the download
sites notes and readme files.
- Win NT 4.0 w/ Service Pack 6
I loaded all of the software from the "Windows PC DEMOpkg"
available to IBM employees only (12 CD's from Edition 39 3Q00).
- JDK v1.2.2 Release 7 (CD#4)
- IBM HTTP Server for WinNT v1.3.63 (CD#3)
- Visual Age for Java (VAJ) Professional Ed v3.5
- IBM WebSphere Application Server Adv Ed V3.5
- IBM WebSphere Studio Adv Ed v3.5
- DB2 UDB Enterprise Edition v7.1 FixPack 1
- Win 2000 Service pack 2 (Under
Construction, then aborted efforts.)
Downloaded all the software from IBM's standard internet sites.
It looks like all you need to do is install WAS 4.0. It will
install the JDK, Websever and all other components. I got WAS 4.0
installed but I aborted my attempts because I did not have the knowledge
to integrate the Struts framework that my project called for.)
- IBM HTTP Server V1.3.19 (works with WAS 4.0) 31Meg
- IBM WAS Advanced Edition 4.0
- IBM WAS Studio v____
- IBM VAJ v4.0 Enterprise Entry Edition &
IBM Enterprise JDK 1.2.2 for IBM VAJ v4.0
- IBM Java JDK 1.3.0 for WAS 4.0
- DB2 Universal Database Enterprise Edition v7.2
- I used the following IBM Redbook: Servlet & JSP Programming
w/ Studio & VAJ SG245755. Chapter 3 "Product
Install" physical pdf pgs 45-68 or book pgs 17-40 (Internet: www.redbooks.com,
IBM Employees: w3.education.ibm.com, the choose "redbooks".)
- WAS - Websphere Application Server
- JDK - Java Development Kit (compile Java source code)
- JRE - Java Runtime Environment
Install Steps for Websphere 3.5 Products
These install steps are my abbreviated notes. For your information I
installed all of the software below on the D: drive, not the default C: drive.
Log on as Administrator
- I've been advised to login as Administrator for Win 2000. On Win NT
4.0, I have loaded all of the following software logged in a user (not
Administrator) that had administrator rights.
- If you have VPN software (like Aventail) make sure that it is not running.
- Might be good to disable anti-virus software also.
Add MS Loopback Adapter (if running on Standalone-no network)
- Note: I'm not sure what symptoms occur if you don't do these
steps. I was have massive problems and then completed the procedures
and it seems like things worked better. Sorry - don't have a real good
techy answer - just hocus-pocus!
- If using Win NT w/ TCP/IP installed then add MS Loopback Adapter.
- Win NT Steps.
Win NT install CD available.
- Start, Settings, Control Panel, Network
- Click on "Adapters" Tab.
- Click on "Add" and find "MS Loopback Adapter"
- Frame Type = 802.3
- Specify an IP Address
- IP Address = 188.8.131.52
- Subnet Mask = 255.255.255.0
- Default Gateway = <leave blank>
- Next, ReBoot.
- Note: If you need to modify the information then Start, Settings,
Control Panel, Network
- Click on the "Protocols" tab
- Click TCP/IP, then click Properties
- Then select the Adapter in the pull down list.
- Note: I use a Token Ring Adapter, a Ethernet Adapter, and the MS
Loopback Adapter without any conflicts.
Virtual Memory (300mb-initial, 400mb max)
- Start, Settings, Control Panel, System
- Click on the "Performance" tab.
- Make settings at least: Virtual Memory = Initial size = 300mb,
Max size = 400mb
- If you had to make changes, then reboot.
Create a User(s) w/admin rights for: IBM HTTP Server, Websphere, & DB2
- Access the User Manager.
Win NT: Start, Programs, Administrative Tools, User Manager for Domains.
Win 2000: Start, Settings, Control Panel, Users and Passwords
You need to create an admin user for: IBM HTTP Server, IBM Websphere,
and DB2. I've suggested some user names. I have IBM HTTP Server
& Websphere sharing user names.
- Admin user for IBM HTTP Server: webadmin
- Admin user for IBM Websphere: webadmin
- Admin user for DB2: db2admin
- User Options
- User options I selected: "User cannot change password"
and "Password never expires".
- Then I clicked on Groups and made them a member of
- If Win 2000 - Give User ID "Logon as a service right.
Start, Settings, Control Panel, Administrative Tools, Local Security
Policies, Local Policies, User Rights Assignments, Log on as a
service. Now add the 2 users.
- When installing the IBM HTTP Server, you are prompted for a login ID and
password. The ID you select must have the capability to log on as a service.
If you get an error when you try to start the Administration Server,
indicating a failure to start as a service, try the following:
On Windows NT:
- Select Start>Programs>Admin
- Select the user from the User Manager list.
- Click Policies>User Rights.
- Check the Show Advanced User Rights box.
- Choose Log on as a Service, from the right drop-down
On Windows 2000:
- Select Start>Settings>Control
- Open Administrative Tools.
- Open Services. The local user you select is created
in Local Users and Groups, under Computer Management.
- Select Service>Actions>Properties.
- Choose the Log on tab.
- Select this account option and click Browse to select
the user to associate with the service.
Java Development Kit (JDK/SDK)
- Install a JDK that is approved for Websphere.
- Read the version notes at the download sites. Make sure you
match the correct versions or your open for problems.
- If you install the IBM JDK, you will see it in the pick-and-choose list
when installing WebSphere Application Server.
- Generally, you can install multiple versions of the JDK without
problems because each application (IDE, Application Server) will
register the path to the JDK. I always suggest reinstalling
the JRE after you install a JDK/SDK but that is a preference.
- Test: From the DOS prompt: c:\> <fullpath to JDK>\bin\java -fullversion
Now verify the version.
- Additional Resources
IBM HTTP Server
- Install directory note: "c:\Program Files\IBM HTTP Server"
- Choose "Typical" install.
- When asked for the user/pswd, use the one created above (ex: webadmin)
- Now Re-boot.
- From a DOS prompt set the admin username/password:
CD "\Program Files\IBM HTTP Server"
htpasswd -c conf/admin.passwd webadmin
- Test Install:
- From a browser: http://localhost
- you should see the IBM HTTP Server screen.
- CGI Test (Warning: looks like some versions don't include this test
- Test the IBM HTTP Administration module.
You may need to start the "IBM HTTP Admin" service
first. Try "Programs, IBM HTTP Server" or "Control
From a browser: http://localhost:8008
- Log in with the user/pswd from the step above where you set the
username & password. You can also access from http://localhost
then click on "Configure Server".
I had to uninstall Aventail 4.0 (a Virtual Private Network)
to get the Admin Services running on Win 2000. Win NT 4.0 &
Aventail works OK.
- Admin Server Problems:
Log files are keep in the "log" directory (see: admin_error.log).
Also use WinNT's "Event Viewer".
- FYI Services Installed: (WinNT: Start, Settings, Control Panel, Services;
Win 2000: Start, Settings, Adminstration, Services).
- IBM HTTP Server (defaults to Automatic) and should start on boot.
- IBM HTTP Administration (defaults to Automatic) and should start on
boot unless you have problems.
DB2 w/ Fix packs
I've installed this several types but did not take good notes so here is what
- I installed from CD #2: DB2 UDB Enterprise Edition v7.1 FixPack 1
- Choose "Typical" install.
- Enter the user/pswd created in the steps above (ex: db2admin)
- After reboot, DB2's First Step window will appear.
- Click on "Create the Sample Database"
- Test Install:
- Click on "View the Sample Database"
VisualAge for Java
- I installed from
- Note: If you installed the IBM JDK 1.2.2 above it is release
7. If you are running JDK 1.2.2 and under release 6b then upgrade
to 6b or higher. On the IBM CD#4 there is a link to "Install
JDK v1.2.2 6b." Then you can install VAJ.
- Install VAJ Products.
- VisualAge for Java
- Install VAJ
- If you downloaded multiple files from IBM's internet site you
will need to extract all files first, then run the setup.exe in
the directory you extracted to.. Click on the first file
you need to extract and read the directions carefully.
- Choose "Complete" install.
- Once the VAJ install is finished, then Install Distributed Debugger.
- Load VAJ: Start, Programs, VAJ etc...
- Choose "Go to the Workbench"
- Add Features to VisualAge for Java: WebSphere Test Environment. This
is not neccessary but you'll probably what to do this down the road if you
want to be able to test WebSphere applications without leaving VAJ.
- File->Quick Start.
- Features, Add Feature
- Select "IBM Websphere Test Environment"
- Test Install of New Feature:
- Workspace, Tools - look for WebSphere Test Environment. If you
load the "WebSphere Test Environment" be patient - it may take
awhile to load.
WebSphere Application Server
- I installed from CD #12: IBM WebSphere Application Server Adv Ed v3.5
- Choose "Custom" Install.
- Select all components.
- If you are using another JDK that the install does not recognize, then
click on the "Other JDK" button and point to the JDK's
"bin" directory (I think?).
- Next screen, select IBM HTTP Server v1.3.6
- WAS User name/pswd - enter the user name that will be used to load WAS (ie:
- Choose the database type that the repository information will be stored in
- DB Type: DB2
- DB Name: was
- DB User ID/Pswd: Note: Make sure you use the one you used when
you installed DB2: (ie db2admin)
- Next the install will look for the file: "httpd.conf". You
will need to point to the following directory: d:\program files\ibm
http server\conf (remember, the default install is C: not D:)
- Next, Reboot
- NOTE: the WAS database will be created after you reboot, if not you
will need to run a batch file to create it. You can find the batch
file @ d:\WebSphere\AppServer\bin\createdb2.bat
- Start the "IBM WS AdminServer"
- Start, Settings, Control Panel, Services
- Select: "IBM WS AdminServer"
- Click on Start. (Warning: You can also start the AdminServer
from the Start, Programs's menu "Start Admin Server", but you
can't see errors if they occur!)
- If you want this service to load on startup, click
"Startup", then choose "Automatic".
- If you have problems starting the WS Admin Server your problem is
probably in the config file: d:\WebSphere\AppServer\bin\admin.config
. Check the User ID's and passwords.
- Also click on "Startup" and check the "Log On
As" account user name (ie: webadmin).
- Now, launch the Admin Console: Start, Programs, IBM WebSphere,
Application Server v 3.5, Administrator's Console.
- In "Administrator's Console" start the Default Server.
- Click on View, the Topology (you probably are in this veiw already).
- Open up the "WebSphere Administrative Domain" in the
- Click on your computer's name.
- Now select the "Default Server". If the server is not
running (look at Current state), then click on the "Run" icon
in the upper left.
- Test Install:
- Java Servlet Test
(or SnoopServlet or snoop2) - you should see around 2-3 pages of Request/Client information.
Note: On your server the file maybe stored in:
(or HelloWorldServlet)- you should see the words "Hello World" on you browser.
Note: On your server the file maybe stored in:
- I installed from CD #12: IBM WebSphere Studio Adv Ed v3.5
- There is 4 applications in the Studio.
- IBM WebSphere Studio 3.5
- IBM WebSphere Applet Designer
- IBM WebSphere Page Detailer
- IBM Distributed Debugger
- WARNING: - "Page Detailer" will
cause a process (msdtc.exe) to take over 99% of your CPU. You can
uninstall just this item if you do load it for testing. It may work
fine for you.
Enjoy and have fun!