Installing WebSphere Application Server -- Full Installation option
To install WebSphere Application Server along with the IBM Developer Kit, IBM
HTTP Server and DB2 UDB, do the following:
- Ensure that you will be installing WebSphere Application Server under a local
Windows user ID that is in the Administrative group and has the advanced user
rights "Act as part of the operating system" and "Log on as a service."
- If a Web server on your system is running, stop the Web server.
- Run the downloaded executable if you obtained Version 3.5 from the product
Web site. Or, run
\nt\setup.exe
if you have the product CD.
You will need 100 MB free in your temp directory (usually on the C drive),
even if you are installing on another drive, because the installation shield
package unpacks to the temp directory. This will kick off an installation
shield package.
- Select a language and click OK.
- Click Next to pass the introductory page.
- If WebSphere Application Server is already installed on your system, a dialog
giving you the option to backup and uninstall WebSphere Application Server displays.
You now have two options:
- To backup your files and uninstall WebSphere Application Server, click
Backup and Uninstall and then Next to continue with the installation.
- To install to a different directory, simply click Next and continue
with the installation.
If WebSphere Application Server is not already installed on your system,
proceed to step 6.
- In the Install Options dialog, select Full Installation;
then click Next.
- On the Security Options dialog, fill in the user ID, security password,
and confirming password to use for the application server and click Next.
- Specify the destination directories and click Next.
- On the Database Options panel, click Next to take the defaults where
db2admin is the database user ID and password. Optionally, you can specify
your own database user ID and password. Ensure that the password is 8 or fewer
characters.
- Click Next again to begin the installation.
- Click OK, and it will finish updating the files and installing.
- After WebSphere Application Server and IBM HTTP Server install, you will be
prompted for the WebSphere Application Server CD that contains files for DB2 UDB.
Insert the CD and use the instructions in
"Installing DB2 UDB 6.1" for guidance in installing DB2.
Note that the WebSphere installation program supplies the parameters specified
on the Database Options panel to the DB2 installation program.
- The final page points you to the README and states where the samples have been
installed. For the most recent version of the README or release notes,
go to Library section of the product Web site at
http://www.ibm.com/software/webservers/appserv/.
Click Finish, and choose to restart.
Finishing prerequisite configuration
Ensure that the Web server installed correctly.
As to DB2 UDB, when installing WebSphere Application Server, the installation program
should have created a database to store the administrative configuration used when your
system starts up after rebooting. The database definition is based on the JDBC URL you
specified during installation. The JDBC URL looks like jdbc:db2:was
.
Further, the installation program should have created the WAS database with its DB2
application heap size set to 256.
To ensure that the WAS database exists, do the following:
- Go to the Control Center dialog. If it did not open automatically after rebooting,
open it as follows: from the Start menu, select Programs -> DB2 for Windows NT ->
Administrative Tools -> Control Center.
- In the DB2 Control Center, expand the tree under Systems. Your DB2 databases
are listed under Databases. Examine the list to see if WAS is in it.
If you see WAS in the list, proceed to "Testing the
installation".
If you do not see WAS listed, run the file createdb2.bat in the \AppServer\bin directory.
Or, do the following:
- Go to the Services dialog accessible from a Control Panel and set the startup for
the DB2-DB2 service to Automatic. Also, ensure that the hardware profile for
the DB2-DB2 service is enabled. Then, complete Step 2. Optionally, for information
about why the installation program did not create the WAS database, look at the
wasdb2.log file or look at "Installing DB2 UDB 6.1."
- If the DB2 database WAS has not yet been created, do the
following:
- From the Start menu, select Programs -> DB2 for Windows NT ->
Command Line Processor.
- Enter
CREATE DATABASE WAS
- Wait a minute to allow time for DB2 to create the database.
- Enter
UPDATE DB CFG FOR WAS USING APPLHEAPSZ 256
- Type
quit
to leave the CLP, and then exit
to finish
the command prompt.
- Restart the machine.
If an application heap size of 256 doesn't work for your system, return to the
DB2 Command Line Processor and change the application heap size to, for example,
512 using the command:
UPDATE DB CFG FOR WAS USING APPLHEAPSZ 512