WebSphere 5.1 Installation for PeopleSoft

backdamagedInternet and Web Development

Jul 30, 2012 (5 years and 17 days ago)

592 views


1



WebSphere Application Server
Version 5.1 Installation




























2


Table of Contents


Task 2
-
1:

Prerequisites for WebSphere Application Server Version 5.1

...............

3

WebSphere 5.1 Product Packaging for PeopleSoft
................................
.................

7

Task 2
-
2:

Installing WebSphere 5.1 Base on Windows 2000

................................
.

8

Order of Installation

................................
................................
................................

8

Installing WebSphere Base

................................
................................
.....................

8

Verifying WebSphere Base Installation

................................
................................

14

Uninstall the Default Application

................................
................................
.........

15

Task 2
-
3:

Installing WebSphere 5.1 Base on UNIX

................................
.............

17

Order of
Installation

................................
................................
..............................

17

Installing WebSphere Base

................................
................................
...................

17

Begin Installation For Each platform

................................
................................
....

18

Task 2
-
4:

Installing the WebSphere 5.1 Plugin

................................
....................

20

Installing the Plugin

................................
................................
..............................

20

IBM HTTP Server & plugin

................................
................................
.................

21

IBM HTTP Server plugin (only)
................................
................................
...........

21

Sun One plugin (only)

................................
................................
...........................

22

MicroSoft IIS plugin (only)

................................
................................
..................

22

Set up on Http Server machine

................................
................................
.............

23

Task 2
-
5:

Installing WebSphere 5.1 Network Deployment

................................
..

25

Verifying WebSphere Network Deployment Installation
................................
.....

28

Un
-
Installing WebSphere ND

................................
................................
...............

29

Task 2
-
6:

Installing We
bSphere 5.1 with Silent Option


Windows or UNIX

....

31

Verifying WebSphere Base Installation

................................
................................

32

Task 2
-
7:

Un
-
Installing WebSphere Base
after Silent Install

...............................

34

Starting, Stopping, and Administering WebSphere Base Server

..............................

35

Starting WebSphere

................................
................................
..............................

38

Stopping WebSphere

................................
................................
............................

38

Finding Ports Used by WebSphere

................................
................................
.......

39

WebSphere Logs

................................
................................
................................
...

40

Administering WebSphere

................................
................................
....................

41

Setting Java Home

................................
................................
..............................

42














3







Ove
rview and Order of Installation


1.

Ensure that minimum system requirements, including hardware and software, have
been meet.
Task 2
-
1

describes these
prerequisites

in detail.


2. Install IBM WebSphere Application Server (Base).



It can be installed ei
ther in GUI or silent mode.

Task 2
-
2

describes the Base
installation procedure using GUI and
Task 2
-
7

explains

the installation in silent
mode.

IBM HTTP Server

(IHS)

can also be installed along with WebSphere Base
install. Refer to
section
-

IBM HTTP Ser
ver &
plugin
,

if planing to install
IHS

seperately in silent mode.




3. Verify Base installation using
IVT

program
.


4.
Uninstall Default Application

and stop the Base server.



5. Upgrade WebSphere Base using Fix

P
ack 1. Refer to
Task 2
-
6

for steps t
o
upgrade
.


6. Install
IBM WebSphere Network Deployment (ND),

if
planning

to cluster WebSphere
Base environment.

Refer to
Task 2
-
5

for installation details.


7.
Upgrade WebSphere ND

using Fix Pack 1.

Refer to
Task 2
-
6

for steps to upgrade.



4

Task 2
-
1:

Prerequisites
for WebSphere Application Server Version 5.1


The following are prerequisites required for WebSphere Application Server Base and Network Deployment
Version 5.1. Deploy the following minimum base prerequisites before you continue with the WebSphere
Applica
tion Server Version 5.1.

AIX

RS/6000 workstation or
RS/6000 SP Frame at 375 MHz
or faster

Minimum

512 MB

memory

recommended

CD
-
ROM drive

-

AIX 5.1 with Recommended


Mainte
nance package 5100
-
04 or

5100
-

05

Linux on Intel

Intel x86 processor at 500 MHz
or faster

Minimum 256 MB of memory;
512 MB recommended

CD
-
ROM drive

-

Red Hat Advanced Server
V2.1

-

Red Hat Enterprise Linux WS/ES/
AS




for

I
ntel 2.1 or

2.1 Update 3

-

Red Hat Enterprise Linux A
S 3.0



Update

1

Sun Solaris

Sun SPARC workstation at 440
MHz, or faster

Minimum 256 MB memory; 512
MB recommended

CD
-
ROM drive

-

Solaris 8 with Recommended
Patch Cluster of July 200
3

-

Solaris 9 with Recommended
Patch Cluster of July 2003

HP
-
UX

HP 9000 at 440 MHz or faster

Minimum 256 MB of memory;
512 MB recommended

CD
-
ROM drive

-

HP
-
UX 11iv1 with Quality
Pack of J
une 2003 and patch
PHCO_29109

Microsoft® Windows®
2000

Intel Pentium processor at 500
MHz, or faster

Minimum 5
96

MB free disk
space for installation (includes
SDK)

Minimum 256 MB memory; 512
MB recommended

CD
-
ROM drive


-

Windows 2000 Server or
Advan
ced Server with SP4

-

Windows 2003
Standard or
Enterprise


Web browsers


-

Microsoft Internet Explorer
V5.5 with SP2 or V6.0

-

Netscape Communicator 4.79



Note:

WebSphere Application Server Version 5.1 has been tested with the following prerequisite patc
hes
(there are separate links for Version 5.1 Base and Network Deployment). If you already have any
of these patches installed on your system, you do not need to reinstall them. In addition, if the
manufacturer replaces any of these patches with a newer v
ersion, you should use the newer
version.



5



Along with the above given hardware and software
requirement
s
, the
following
prerequisites

are required
for WebSphere Application Server Base and Network Deployment Embedded Messaging service
:


(Microsoft

W
indow
s

only)


a. Define the process user ID with these authorizations:



Assign the user ID to the Administrator group.



Give the user ID the advanced user right, Act as part of the operating system.



Give the user ID the advanced user right, Log on as a service
.

User IDs longer than 12 characters cannot be used for authentication with the
embedded WebSphere JMS provider. For example, the default Windows NT user ID,
Administrator, is not valid for use with embedded WebSphere messaging, because it
contains 13 cha
racters.

b. Allocate space for Base Messaging and Message Broker

The following table lists the default locations for the base messaging functions and the messaging


broker functions (for publish/subscribe messaging).






(UNIX platforms only)



a. Define the operating system groups and users neede
d for
embedded messaging
:




If you have not already done so, create the groups
mqm

and
mqbrkrs
.



Add the users
mqm

and
root

to the
mqm

group.



Add the user
root

to the
mqbrkrs

group.



Login once as mqm

user; then log back in as root
.


Note
s
:


You are reco
mmended to run the JMS server process under the root user ID. If you run the JMS


Server

process under another user ID, add that user ID to the
mqm

and
mqbrkrs

groups.




User IDs longer than 12 characters cannot be used for authentication with the

embedded

WebSphere

JMS provider.














Base messaging

Messaging broker

Installation
directory

C:
\
Program
Files
\
IBM
\
WebSphere
MQ

C:
\
Program
Files
\
IBM
\
WebSphere
MQ
\
WEMPS

Typical
space needed

70 MB (server) or 15 MB
(client)

45 MB (server)


6




b. The file system into which the Embedded Messaging options are installed is fixed.


Installation directory and space needed for

embedded messaging
-

UNIX platforms

are:



























Note:
The /var file system is used to store all the security logging information for the system, and is used to

store the temporary files for email and printing. Therefore, it is cri
tical that you maintain free space in /var

for these operations. If you do not create a separate file system for messaging data, and /var fills up, al
l

security logging will be stopped on the system until some free space is available in /var.



(Solaris /

HP
-
UX only)


It is recommend that before installing Embedded Messaging, review the machine's configuration
and, if needed, set appropriate kernel settings.

You should set new values for the following messaging
-
related kernel parameters

(along with the
base set of kernel parameters required by IBM WebSphere Application Server
):



The full list of prerequisites for W
ebSphere 5.1 base and ND are available on the following website:

http://www
-
3.ibm.com/software/webservers/appserv/doc/latest/prereq.html


If your operating system is n
ot at the required patch level, a warning message will appear at the beginning
of the installation. It is important to stop the installation and apply the requested patches to the system.




Base code

Broker code

Base da
ta

Broker
data



/usr/mqm

/usr/opt/wemps

/var/mqm

/var/wemps

AIX

40MB
(server)
or 15MB
(client)

80MB (server)
or 15MB
(client)

8MB
(server)
or 5MB
(client)


5MB
(server)



/opt/mqm

/opt/wemps

/var/mqm

/var/wemps

Linux/Intel

40MB
(server)
or 15MB
(clien
t)

100MB (server)
or 15MB
(client)

8MB
(server)
or 5MB
(client)

5MB
(server)

HP
-
UX

40MB
(server)
or 15MB
(client)

105MB (server)
or 15MB
(client)

8MB
(server)
or 5MB
(client)

5MB
(server)

Solaris

40MB
(server)
or 15MB
(client)

70MB (server)
or 15MB
(clie
nt)

20MB
(server)
or 15MB
(client)

5MB
(server)


7


8

Task 2
-
2:

Installing WebSphere 5.1 Base on Windows 2000

Note the following steps to install WebSphere Application Server Base Version 5.1.


Note:

PeopleTools 8.44 supports the Http Server embedded within WebSphere

for both http and
https. Use of an external proxy server is optional. Supported proxy servers are IBM Http
Server
,

Sun

ONE Web Server

and Internet Information Server.

Before you begin the
installation, review the PeopleSoft Platforms Database to ma
ke sure you are installing WebSphere
into a supported environment.


Instal l i ng WebSphere Base

Note:

WebSphere Application Server Version 5.1 can be installed using a GUI or silent installation
option. This section explains how the GUI installation works. The silent installation option is
explained in
Task 2
-
5:

Installing WebSphere 5.1 with Silent Option


Windows or UN
IX


Note:

It is recommended that you be a member of the Administrator group to install WebSphere.
If you
plan to install the IBM Http Server, you
must

be a member of
the Administrator group.

Begin installing WebSphere 5.1 by installing the WebSphere Base from CD.

1.

Stop any HTTP Server (IBM Http Server, IIS, or Sun ONE Web Server) running on the system.

2.

Insert the WebSphere CD into your CD
-
ROM drive.

Note:

If using a net
work resource, on Windows map the drive. Do not use UNC paths.

3.

Navigate to the CD
-
ROM drive. You will see the “installBase.bat” file. You can run this command
from the DOS command window and this will start the installation of WebSphere Application Serv
er
5.1 Base.

4.

Type
installBase.bat
. This will invoke the default GUI install. A window may appear requesting a
language to be selected. Select
English

(the default). Click
OK
.


5.

Click
Next

on the “Welcome to IBM WebSphere Applica
tion Server, Version 5.1” panel.


6.

If a warning message appears stating that required patches are missing, stop the installation, apply the
requested patches, and then start the installation again.

7.

On the next “Software License Agreement” panel.,
click
“I accept the terms in the license
agreement”

and Click
Next.


8.

WebSphere will check to see if WebSphere is already installed. If so you will see the panel shown
below.


9

If you are installing WebSphere on a machine that has no other copies of WebSphere on it, you
will not see this panel.

Click on
“modify ports for coexistence”

to allow multiple versions to co
-
exist and run on this computer by
mod
ifying port numbers.



The next panel displays the settings for the listed ports.
If you are installing WebSphere on a
machine that has no other copies of WebSphere on it, you will not see this panel.




10

9.

It is recommended that you set the list
of ports with a value such as 10000 added to each port number
-

i.e., a 1 in front of them in the case of WebSphere co
-
existence. This makes it easy to determine which
collection of ports are associated with a given instance of WAS. (
NOTE:

The install wi
zard suggests
new ports by incrementing various digits in the default ports. For a silent install we have used the
defaults plus 10000.)


The port for
IBM HTTP Server port (Default 80)

should not be changed from port 80. Please
change the value back to
80 if necessary.


Please write down these port changes, especially the
HTTP Transport Port
(Default 9080),
HTTPs
Transport Port

(Default 9443), and
Admin Console Port
(Default 9090).

The installation wizard will ensure all of the prerequisites are satisf
ied. If you have not met all
the prerequisites, you are warned about this situation. The installation of the product, however,
continues.

10.

The next panel that is displayed wants you to choose a Full or Custom install. Ensure
Custom
is
selected.





11.

C
lick
Next.

12.

The selections for the custom installation appear. At this point, it is important to note that there are
several selections that should be de
-
selected for PeopleSoft PeopleTools and applications to function
optimally.

Uncheck the following se
lections: “Applications Server Samples” and “Javadocs”.

If you decide to install the IBM HTTP Server and HTTP proxy server Plugin at this point, you can
keep the selected features for “IBM HTTP Server Version 1.3.28”, “Web Server Plugins” and “IBM
HTTP

Server v1.3” plugin. Other HTTP (web server) proxy plugins (i.e., for IIS or Sun ONE Web
Server) may also be selected only if you have already installed either of these HTTP servers
previously.



11

Note:

HTTP proxy server plugins may also be configured if
you have: 1
-

Previously installed
WebSphere base and did not select an HTTP proxy plugin, or 2
-

Installed WebSphere using the
silent installation method (which does not install the plugin), or 3
-

You are installing the plugin on
a remote machine where you
have already installed an HTTP server. Plugin installation is
described in detail in
Task 2
-
4:

Installing the WebSphere 5.1 Plugin






13.

Click
Next.


14.

The default installation location is
C:
\
WebSphere5
1
\
AppServer
. (We refer to this directory as
<WAS_HOME>.) If you want to change the default installation location, you can simply edit the path
in the edit field
--

there is no need to click the Browse button. On Unix systems this will be the
“current” di
rectory, usually the cdrom drive. You must change this to a directory on a file system with
enough space to install WebSphere. The normal install location for
Solaris, HP
-
UX

and
Linux

is

/opt/WebSphere51/AppServer. For
AIX

it is /usr/WebSphere51/AppServ
er


12

15.

The default installation location fo
r
WebSphere Embedded Messaging
, on Windows,

is
C:
\
Program
Files
\
WebSphere MQ
.

For WebSphere fixpack installation to work in silent mode, it is

highly
recommend

installing

it
in default location.

On UNIX platforms, em
bedded messaging is installed in
fixed location.




































16.

If you have selected the IBM HTTP Server from the prior step, you can keep the default path
C:
\
IBMHttpServer or update the path to, for example, reflect

the version number, e.g.
C:
\
IHS1.3.28
.

17.


18.

Click
Next
.

19.

The next panel allows you to enter your
WebSphere node name

and the
machine’s host name

(or IP
Address). The node name defaults to <hostname>Node where <hostname> is your machine’s
hostname. Host Name
or IP Address defaults to <hostname>. You can modify this field to the fully
qualified hostname of your machine or its IP address.
It is recommended to keep these defaults.

20.

Click
Next
.


13

21.

On the next panel, you have the option to
Run WebSphere Applicati
on Server as a service
(an
options only for Windows). Enter the password for the userid you are using.
NOTE:

If you select to
run WebSphere as a Windows 2000 service, you can start, stop, and configure startup/recovery options.
By choosing to run the App
lication Server as a service, you can, from a central location (Control
Panel > Administrative Tools > Services), manage the Application Server. You can also start and stop
WebSphere from the command prompt. Specified username has to be part of Administra
tor group on
Windows only.



22.

Click
Next
.


23.

The next panel presented shows the options you have

selected
s




14

Click Next. WebSphere will install. This will take some time.

24.

Uncheck the

Select Register this product no
w
. Click
Next
.

25.

Click
Next

on the Install Shield Wizard window.
NOTE:

The Installation panel may loose focus as
First Steps is launched. If so, return to the Installation Wizard panel and select
Finish
.

26.

You have completed the installation of the WebSphere
Application Server Version 5.1 product.

27.

Refer to the Customer Connection link
ftp://ftp.peoplesoft.com/outgoing/PTools/websphere/5
1
1
PT84
6


to check whether any iFixes are
neede
d. If they are present, you must install them. Refer to the PeopleSoft
-
WAS
-
readme.txt file to
install them.


Note:

Check the logs for any errors encountered during the installation. WebSphere Application
Server’s install log is located in <WAS_HOME>
\
logs
\
log.txt. The IBM HTTP Server log is in
<WAS_HOME>
\
logs
\
ihs_log.txt.

Veri fyi ng WebSphere Base Instal l ati on

1.

The First Steps panel for the WebSphere Application Server is launched after the installer delivers all
of the files.


2.

A window titled
WebSphere
Application Server
-

FirstSteps
should appear. Select
Verify
Installation
.


15

3.

The results of running the Install Verification Test (ivt) should be successful as shown below. Note
that you may see a message saying “WebSphere Application Server is not runnin
g and could not be
started”. If the Application Server is not running it will be automatically started.


IVTL0095I: defaulting to host nathand and port 9080

IVTL0010I: Connecting to the WebSphere Application Server
WebSphereND1 on port: 9080



IVTL0020I:
Could not connect to Application Server, waiting for
server to start

IVTL0025I: Attempting to start the Application Server

IVTL0030I: Running cmd.exe /c
"C:
\
WebSphere51
\
AppServer
\
bin
\
startServer" server1

>ADMU0116I: Tool information is being logged in fi
le

> C:
\
WebSphere51
\
AppServer
\
logs
\
server1
\
startServer.log

>ADMU3100I: Reading configuration for server: server1

>ADMU3200I: Server launched. Waiting for initialization status.

>ADMU3000I: Server server1 open for e
-
business; process id is
3116





IVTL0050I: Servlet Engine Verification Status
-

Passed



IVTL0055I: JSP Verification Status
-

Passed



IVTL0060I: EJB Verification Status
-

Passed



IVTL0070I: IVT Verification Succeeded



IVTL0080I: Installation Verification is complete


4.

The summary
of the test is written to <WAS_HOME>
\
logs
\
ivt.log

5.

If the tests are successful, select
Exit

on the window titled “
WebSphere Application Server
-

First
Steps
” window. This action will also close the window titled FirstSteps Output


Verify Installation
Test.


Note

The WebSphere instance will be started by the ivt test. If you attempt to start WebSphere when it
is already running, you will get a message about the port already in use. Use the stopserver
command to stop WebSphere.








16

Uni nstal l the Defaul t Appl i cati on

Note

Although WebSphere Server Samples will not be installed when unchecked, Web
Sphere’s
default application will still be installed. This default application will cause a conflict with
the PeopleSoft PeopleTools application and may have to be un
-
installed. This conflict is due
to the default use of the context root “/” by both appl
ications.


The Default Application may be installed by default. The PeopleSoft PIA uses the same context root as the
Default Application. The Default Application must be removed to avoid a conflict with the PIA.

1.

Start WebSphere and access the Admin Conso
le (ex. http://hostname:9090/admin or the Web Admin
Console port specified during installation).

2.

From the Admin console, expand
Applications
-
>Enterprise Applciations
.

3.

Select checkbox for the (1) DefaultAppplication. Click Stop and then click uninstall but
ton to uninstall
app. If the DefaultApplication is not present, then it was not installed.

4.

Save configuration and logout.



17

Task 2
-
3:

Installing WebSphere 5.1 Base on UNIX

The following steps describe how to install WebSphere App
lication Server Base Version 5.1 on the
following Unix operating systems.




HP
-
UX 11iv1;
Solaris 8 or 9; UnitedLinux 1.0 or
Red Hat Linux AS 2.1;

AIX 5.1 or 5.2.

Note:

PeopleTools 8.44 supports the Http Server embedded within WebSphere for both http and
ht
tps. Use of an external proxy server is optional. Supported proxy servers are IBM Http
Server,

Sun ONE Web Server and IIS.


Before you begin the installation, review the PeopleSoft Platforms Database to make sure you are
installing WebSphere into a suppor
ted environment.

Order of Instal l ati on



Install any HTTP Proxy Server you plan to use with WebSphere before you install WebSphere.

Supported proxy servers for Unix include IBM Http Server and Sun ONE Web Server.



If you plan to install the proxy server Sun O
NE Web Server and stop the Sun ONE Web Server
Admin Server and Sun ONE Web Server Enterprise Server.



The WebSphere installation includes an option for installing IBM Http Server and it will configure
the plugin for selected proxies (IBM Http Server or Sun
ONE Web Server).


Before you begin the installation, review the prerequisite requirements in
Task 2
-
1

to make sure you are
installing WebSphere into a supported environment.


Unix customers should make sure that their DISPLAY and
TERM environment variables are set properly.

By default, the WebSphere graphical install program lists the cdrom directory as the default location. You
must change this to a valid file system with enough room to install WebSphere. The silent install use
s the
following defaults:



Solaris, HP
-
UX and Linux:

/opt/WebSphere51/AppServer



AIX:

/usr/WebSphere51/AppServer

Instal l i ng WebSphere Base

Begin installing WebSphere 5.1 by installing the WebSphere Base from CD.

Note:

You need to use an X Window System for
a GUI install of WebSphere Application Server.

1.

Check that you are logged onto the host machine with super user (root) privileges.
Install WebSphere
only with root privileges.

2.

Open an xterm so that you can access the command line.

3.

Ensure that your DISPLAY e
nvironment variable is set properly:

If your DISPLAY is not set, set it now.


18

For example:

#export DISPLAY=
hostname
:0.0


-
or
-


#export DISPLAY={IP Address}:0.0


If any HTTP proxy server on your system is running, stop it now.

4.

Insert WebSphere CD into the
CD
-
ROM drive.

Begi n Instal l ati on For Each pl atform

Note:

Before starting installation, you should review the prerequisites section and identify a file
system with enough space to install WebSphere. You can check a file system’s available
space using the c
ommand
df

k
.

HP
-
UX:



Start the <pfs_mountd> daemon, if it is not already started

for example:

$ /usr/sbin/pfs_mountd &



Start the <pfsd> daemon, if it is not already started

for example:

$ /usr/sbin/pfsd 4 &



Mount the CD with file system type as <iso9660> w
ith rock ridge extensions, if it does not mount
automatically

for example:

$ /usr/sbin/pfs_mount

o rr
-
t iso9660 /dev/dsk/c0t0d0 /cdrom



If the above commands do not work, use this command:


$ mount

o rr /dev/dsk/c2t1d0 /cdrom

AIX:



Use the command below
to mount the CD (i.e., create the /mnt/cdrom directory if needed for use
as a mount point):

$ mount
-
rpfv cdrfs /dev/cd0 /mnt/cdrom

Solaris:



Mount the CD if not mounted automatically. Use the following command if the vold daemon does
not mount the CD auto
matically:


$ mount
-
F hsfs
-
r /dev/dsk/c0t6d0s2 /mnt/cdrom


(This will mount the CD
-
ROM under
/mnt/cdrom
. Note that the device name
/dev/dsk/c0t6d0s2

is the
default under Solaris but may be different on your system, depending on your hardware configuratio
n).


19

Linux:



mount
-
t iso9660
-
r /dev/cdrom

/mnt/cdrom


(a symbolic link should already exist to your device file, and an empty directory
/mnt/cdrom

should exist)



5.

Type
./
installBase.sh
. This will invoke the default GUI install. A window may pop up r
equesting a
language to be selected. Select the desired language (
English

is the default). Click
OK
.

6.

If a warning message appears about missing patches, stop the installation, apply the required patches,
and then restart the installation.

7.

The panels for
the Unix GUI installation are similar to those shown in
Task 2
-
2 “Installing
WebSphere 5.1 Base on Windows 2000”

of this document. Refer to that section of the document for
detailed panels for the Unix installation.

Note:

The Un
ix installation will not have a panel for “Run WebSphere Application Server as a
service”. This is strictly for Windows 2000.


To unmount your CD
-
ROM

8.

After the WebSphere base installation completes, unmount the CD
-
ROM and remove it from the
CD
-
ROM drive.

HP
-
UX:

# /usr/sbin/pfs_umount /cdrom

AIX and Linux:

# umount /mnt/cdrom

Solaris:

# umount /mnt/cdrom



-
or
-

(depending on how it was mounted above)


# umount /cdrom/cdrom0


20

Task 2
-
4:

Installing the WebSphere 5.1 Plugin

WebS
phere Application Server Version 5.1 supports a variety of HTTP proxy servers (such as the IBM
HTTP Server, Sun ONE Web Server or IIS). These HTTP proxy servers are necessary for directing traffic
from users' browsers to the applications running in WebSph
ere.


This is achieved by installing the WebSphere plugin on the of proxy servers. As shown in
the following

diagram, the plugin is a module that runs as part of the HTTP proxy server process. It acts a
s a router and
load balancer, deciding what traffic is for WebSphere and what traffic should be handled by the HTTP
proxy server itself.



Instal l i ng the Pl ugi n


Note
.

To install the plugin, s
hut down all HTTP proxy servers you plan to run with WebSph
ere
.

Note:

On Windows, you
must

be a member of the Administrator group to install IBM
Http Server.

Installing the plugin by itself is applicable on a machine where WebSphere 5.1 base has been installed but
did not install the plugin. It is also applicable

when you want to install a plugin on a remote machine and
have already installed the HTTP proxy server (i.e. IBM HTTP Server, Sun ONE Web Server or IIS). Note
that IIS is only applicable as an HTTP server for Windows.

To install the WebSphere plugin for
the HTTP proxy server that you may have selected, you will need to
first manually update a responsefile with the options for the HTTP proxy server that you are using.

21

Template responsefiles are provided with options optimized for the PeopleSoft applicatio
ns. The
responsefiles are located on the installation CD under the “base” directory. After updating the responsefile,
you can run the installer using this file as input as described below.


After installation, The HTTP proxy plugin can be further configu
red in various architectural scenarios.
These configuration steps are part of WebSphere 5.1 administration, and are addressed in the PeopleBooks
section for “WebSphere 5.1 Administration” for PeopleTools 8.44.


Additionally, most production architecture
s will use the WebSphere Network Deployment component.
Such topics are fully addressed in the PeopleSoft redpaper for “Advanced Clustering and Configuration.”

Note
.

All of the examples below require a value for
wasBean.installLocation

as the location for

the
WebSphere plugin code. This value should specify a
different

directory from any existing
WebSphere installs. If you specify the directory of an existing install your application server may
no longer start.

IBM HTTP Server & pl ugi n

The following in
dicates how to set up the responsefile if you are installing
both

the IBM HTTP Server
and
its plugin together.

1.

To install the IBM HTTP Server and its plugin, you must first copy the file IHS_N_Plugin.resp
from the cdrom /base directory to the temp director
y and update the following lines:

-
P wasBean.installLocation="C:
\
WebSphere51
\
plugin"

-
P ihsFeatureBean.installLocation="C:
\
IBMHttpServer"

Set ihsFeatureBean.installLocation to the directory location where you want to install the IBM
HTTP server. Set
wasBean.installLocation to

where you want the plugin modules installed.

2.

From the cdrom /
bas
e/<os>

directory
, issue the command:

install

options /temp/IHS_N_Plugin.resp

This will start the install with just the selected op
tions, and will begin the installation of the plugin silently.
You can monitor the installation by viewing the file log.txt in the temp directory.


5.

This completes the installation of the plugin.
If you are planing to use IBM Http
Server on

a separate
ma
chine,
then run


gskit.sh

(bat)

to upgrade IBM HTTP Server gskit version.
Navigate to
‘UpdateWAS<os>’ folder, and invoke gskit.sh
(bat)

For example:


/opt/UpdateWASlnx/gskit.sh


5.
Reboot
the server machine on Windows platforms
(a
reboot is not necessary on Unix platforms)

IBM HTTP Server pl ugi n (onl y)

The following indicates how to set up the responsefile if you are
only

installing the IBM HTTP Server
plugin
. You would do this if you

have the IBM HTTP Server already installed.

1.

To install the IBM HTTP server plugin, you must first copy the file IHSproxyPlugin.resp from the
cdrom /base directory to the temp directory and update the following lines:

-
P wasBean.installLocation="C:
\
WebSph
ere51
\
plugin"

-
W defaultIHSConfigFileLocationBean.value="C:
\
IBMHttpServer
\
conf
\
httpd.conf"

Set defaultIHSConfigFileLocationBean.value to the full path to the IBM HTTP Server
configuration file (httpd.conf). Set
wasBean.install
Location to

where you want the plugin
modules installed.


22

2.

From the cdrom /
base
/os

directory

(
where
os

can be
sun, win,

aix, hp, and linux
)
, issue the
command:

install

-
options

/temp/IHSproxyPlugin.resp


3.

This will start the install with just the selected op
tions, and will begin the installation of the plugin
silently. You can monitor the installation by viewing the file log.txt in the temp directory.

4.

This completes the installation of the plugin. Reboot the server machine on Windows platforms (a
reboot is

not necessary on Unix platforms).

Sun One pl ugi n (onl y)

The following indicate how to set up the responsefile if you are
only

installing the Sun One (Sun ONE Web
Server) plugin. The Sun One server must already be installed.

1.

To install the Sun One Web Se
rver plugin, you must first copy the file SunOneProxyPlugin.resp
from the cdrom /base directory to the temp directory and update the following lines:

-
P wasBean.installLocation="C:
\
WebSphere51
\
plugin"

-
W defaultIPlanetConfigFileLocationBean.value="C:
\
iPlan
et60
\
conf
\
obj.conf"

Set defaultIPlanetConfigFileLocationBean.value to the full path to the Sun One server
configuration file (i.e., something like C:
\
iPlanet60
\
conf
\
obj.conf). Set wasBean.installLocation
to where you want the plugin modules installed.

2.

F
rom the cdrom /
base
/os

directory

(where
os

can
be sun, win, aix, hp, and linux)

, issue the
command:

install

-
options

/temp/SunOneProxyPlugin.resp


3.

This will start the install with just the selected options, and will begin the installation of the plugin
si
lently. You can monitor the installation by viewing the file log.txt in the temp directory.

4.

This completes the installation of the plugin. Reboot the server machine on Windows platforms (a
reboot is not necessary on Unix platforms).

Mi croSoft IIS pl ugi n

(onl y)

The following indicate how to set up the responsefile if you are
only

installing the MicroSoft IIS plugin.

1.

To install the MicroSoft IIS plugin, you must first copy the file IISproxyPlugin.resp from the
cdrom /base directory to the temp directory a
nd update the following line:

-
P wasBean.installLocation="C:
\
WebSphere51
\
plugin"

Set wasBean.installLocation to where you want the plugin modules installed


2.

From the cdrom /
base
/win

directory, issue the command:

install

-
options

C:
\
temp
\
IISproxyPlugin
.resp


3.

This will start the install with just the selected options, and will begin the installation of the plugin
silently. You can monitor the installation by viewing the file log.txt in the temp directory.

4.

This completes the installation of the plugin. Rebo
ot the server machine on Windows platforms (a
reboot is not necessary on Unix platforms).


Refer to the Customer Connection link
ftp://ftp.peoplesoft.com/outgoing/PTools/websphere/51
1
P
T84
6

to check whether any iFixes are needed. If they are present, you must install them.


Note:

Check the logs for any errors encountered during the installation.
WebSphere Application Server’
s install log is located in

23

<WAS_HOME>
\
logs
\
log.txt. The IBM HTTP Server log is in
<WAS_HOME>
\
logs
\
ihs_log.txt.



Set up on Http Server machi ne

Plugin
-
cfg.xml file on Http Server machine (RPS) reads WebSphere's plugin
-
cfg.xml file to
forward requests t
o WebSphere.


Copy plugin
-
cfg.xml file from WebSphere_HOME/config/cells/plugin
-
cfg.xml to the following
location based on the Http Server.


How to find plugin
-
cfg.xml file on RPS

(Http)

machine


IBM Http Server

Open IBM_HTTP_Server_HOME/conf/
httpd.conf,
search

for plugin
-
cfg.xml file in it to find out the
location of plugin
-
cfg.xml file on RPS machine.


SunOne (
iPlanet)

Open Sun_ONE_HOME/servers/https
-
<machine>.domain>/config/magnus.conf ,search for
plugin
-
cfg.xml file in it to find out the location of pl
ugin
-
cfg.xml file on RPS machine.


Internet Information Server

Open Windows registry
, expand

HKEY_LOCAL_MACHINE > SOFTWARE > IBM > WebSphere
Application Server > 5.0.0.0.Plugin Config key points to plugin
-
cfg.xml file.


Take a back up of the respective plu
gin
-
cfg.xml file on
Http Server

machine.


























24






25

Task 2
-
5:

Installing WebSphere 5.1 Network Deployment

WebSphere Application Server Version 5.1 also contains the Network Deployment (ND) component. If
you a
re planning on implementing a large user or production environment, you should consider
implementing Network Deployment along with the WebSphere Application Server Base.

There are many changes in System Management from WebSphere Version 4.0 to WebSphere Ve
rsion 5.1.
WebSphere Application Server Version 5.1 Network Deployment provides centralized administration of
multiple nodes, allowing you to administer multiple nodes on the same machine, or on multiple machines.

System Management in WebSphere Applicati
on Server Version 5.1 deals with managed processes, nodes
and Cells. A managed process is an individual server (or process) like the Application Server. Each
process runs in its own Java Virtual Machine. A Node consists of a set of managed processes, man
aged by
a Node Agent. A Cell is an aggregation of nodes. A Deployment manager on the Cell controls and
communicates with all of the Node Agent processes on each node of the Cell. File Synchronization is the
process that helps make configuration data cons
istent across a Cell by moving updated configuration files
from the deployment manager to the node(s).


Network Deployment clustering is achieved by adding, or federating, nodes into a Cell. This topic
and other configuration topics are further explained

in the PeopleSoft redpaper for
“Advanced
Clustering and Configuration”.



Note:

You can install WebSphere Application Server Version 5.1 Network Deployment using
either the GUI install method or the silent install method. You only need to choose one of
t
hese methods to install an instance of WebSphere ND.


You only install Network Deployment once, on a single machine, within a Cell. In a
production environment this machine is typically separate from any base servers for
performance reasons. The single i
nstallation of Network Deployment will allow the
centralized administration of all nodes within your Cell.

In order to use Network Deployment, you will first install the Deployment Manager:

1.

First, stop any HTTP Server (IBM Http Server, IIS, or Sun ONE
Web Server) running on the system.

2.

Verify that any WebSphere Application servers on your machine are not running.

3.

If there are any servers running, open a Command prompt window (or xterm) and navigate to
<WAS_HOME>
\
bin,

and type
stopserver server
n

(where “
n
” is the server number
--

e.g., server1).
Wait until you get a confirmation message that the server has stopped.

If you get the error “Could not create SOAP connector”, the server was not running.

4.

Insert the WebSphere CD into your CD
-
ROM drive.

5.

Navigate

to the CD
-
ROM drive. You will see the “installDeployMgr.bat” file for Windows or
“installDeployMgr.sh” for Unix. You can run this command from a DOS command window (on
Windows) or xterm (on Unix) to start the installation of WebSphere Application Serve
r Network
Deployment.

In this case, we will use “installDeployMgr.bat” for WebSphere base on Windows 2000.

6.

Type
installDeployMgr.bat
. This will invoke the default GUI install. A window will pop
-
up
requesting a language to be selected. Select
English

(
the default). Click
OK
.


26

7.

Click
Next

on the welcome screen.

8.

Accept the license agreement and click
Next
.

9.

The install wizard checks prerequisites, which will take awhile.

10.

If you are performing a WebSphere Network Deployment installation on a machine that ha
s
WebSphere Application Server 5.1 Base already installed, a panel will show up that asks whether you
want to add features to ND or install a new copy. Select
Install a new copy.
(Specify path
<install_root>/DeploymentManager
.)

11.

If you have older versions
of WAS installed on you machine you may get a panel that asks whether
you want to migrate the previous version (Do not choose this.), or allow multiple versions to coexist.
(
Choose this
). It will display the default port numbers used by the Deployment M
anager.

12.

The next panel presents you with a checklist of installation components. You only need Deployment
Manager.

13.

The next panel confirms the default installation directory. Be sure the install directory is set to
<install_root>/DeploymentManager, e.
g.
C:
\
WebSphere51
\
DeploymentManager
.


27

14.

The next panel presents you with the default setting for your node, host and cell. If you decide to
change the selections from the default, it is important to have a unique cell name. The node name must
be unique wit
hin the context of the cell name. And the host name must be your host’s DNS name. (A
fully qualified hostname is recommended and not an IP address.)

If you are not sure, it is
recommended that you keep and use the default selections.



15.

In the next
panel, you may choose to run WebSphere App Server as a service or not if this is a
Windows installation. You need to provide a user ID and password if you choose to run it as a service.
Click
Next
.

16.

Click
Next

to begin the in
stallation
. First the Deployment Manager will be installed then the
applications it runs: filetransfer, adminconsole, are installed. This all takes approximately 10 minutes.

17.

Deselect the checkbox for connectin
g to the Internet to register and click
Next
.

18.

Click
Next

on the Install Shield Wizard window.
NOTE:

The Installation panel may loose focus as
First Steps is launched. If so, return to the Installation Wizard panel and select
Finish
.

19.

You have completed the

installation of the WebSphere Application Server Version 5.1 product.

20.

Refer to the Customer Connection link
ftp://ftp.peoplesoft.com/outgoing/PTools/websphere/51
1
PT84
6



Note:

Check t
he logs for any errors encountered during the installation. WebSphere Application
Server’s install log is located in <WAS_HOME>
\
logs
\
log.txt. The IBM HTTP Server log is in
<WAS_HOME>
\
logs
\
ihs_log.txt.


28

Veri fyi ng WebSphere Network Depl oyment Instal l ati on

1.

The First Steps for the WebSphere Application Server is launched after the installer delivers all of the
files.

2.

Run the Installation Verification Test (ivt). You should see the output in the DOS shell:


IVTL0095I: defaulting to host WebSphereND1 and por
t 9091

IVTL0010I: Connecting to the WebSphere Application Server
WebSphereND1 on port: 9091



IVTL0020I: Could not connect to Application Server, waiting for
server to start

IVTL0025I: Attempting to start the Application Server

IVTL0030I: Running cmd.exe /
c
"C:
\
WebSphere51
\
DeploymentManager
\
bin
\
startManager"

>ADMU0116I: Tool information is being logged in file

>
C:
\
WebSphere51
\
DeploymentManager
\
logs
\
dmgr
\
startServer.log

>ADMU3100I: Reading configuration for server: dmgr

>ADMU3200I: Server launch
ed. Waiting for initialization status.

>ADMU3000I: Server dmgr open for e
-
business; process id is 4076

IVTL0070I: IVT Verification Succeeded



IVTL0080I: Installation Verification is complete

3.

Exit the First Steps utiltity.

4.

You can check the install log fil
e in <install_root>/DeploymentManager/logs/log.txt.









29

Task 2
-
6:

Upgrade WebSphere 5.1 Base and/or ND with Fixpack 1


Fixpack Installation Overview:

1. Pre
-
requisites:


If you are planing to use IBM Http Server and WebSphere Base or ND on the same machine, t
hen
install IBM Http Server first before upgrading WebSphere.


1.1 Both IBM WebSphere and IBM HTTP Server should be stopped.



1.2 Ensure

you have adequate space in your respective <base
-
home> and
/or
<ND
-
home> directries for


the

fixpack install


1.3 If WebSphere ND is used in the environment, apply the Fixpack to ND first before upgrading


WebSphere Base.


1.4 JAVA_HOME variable must be set.

2. Run UpdateBase and UpdateND scripts to apply fixpac
ks on Base & ND respectively.

3.

Check version level of both IBM WebSphere and its IBM WebSphere JDK, to verify successful


Installation of the fixpack.



Steps to apply the Fixpack:


1.

From cdrom, invoke UpdateBase.sh (bat) or UpdateDeployMgr.sh (bat) sc
ript to apply fixpack to
WebSphere Base and/or ND respectively.



For example:


/cdrom/UpdateBase.sh

/cdrom/UpdateDeployMgr.sh


2.

You will be prompted with questions to enter WebSphere and IBM Http Server home directory.
The install program wil
l then start to apply the fixpacks based on these user inputs.


3.

Run the versionInfo.sh (bat) program from <WAS
-
HOME>/bin directory to verify the installation
of the fixpack. The WebSphere Installed Product should be at version 5.1.1 and IBM WebSphere
JDK a
t 1.4.2



Upgrade did not complete

successfully



what
to do next?



Refer to
Troubleshootin
g
-

Installation and Upgrade

section.



Upgrade IBM HTTP Server onl y


If you are planing to use IBM Http Server (IHS) on a sepa
rate machine, then invoke UpdateIHSOnly.sh
(bat) script from cdrom to apply the fixpack to IHS only.


UpgradeIHSOnly script skips the installation of all WebSphere Base service but that for the IBM HTTP
Server product.



30


4.






31

Task 2
-
7:

Installing WebSphere 5.1 with
Silent Option


Windows or UNIX

Note:

It is recommended that you be a member of the Administrator group to install WebSphere.


On Unix systems, you must install WebSphere as root. After installation, WebSphere can be
changed to run as a non
-
root user.

If
you have many identical systems to upgrade then doing a silent install would probably be the preferred
method, using a response file to automatically guide the installation. The default responsefile that comes
with the PeopleSoft packaged CD contains those

options that work best with PeopleSoft PeopleTools and
applications. Silent installation for WebSphere 5.1 works on all supported operating systems.

To install WebSphere Application Server Version 5.1 base or Network Deployment (ND) using the silent
op
tion, you specify the appropriate parameter with the custom install script.

Note: You should only install a single WebSphere 5.1 instance using either the GUI install method
or the silent install method. You only need to choose one of these methods to

install an
instance of WebSphere, not both. If you have already installed with the GUI method, you do
not need to follow these steps.

Unix customers should make sure that their DISPLAY environment variable is set properly, otherwise the
First Steps progr
am at the end of the silent installation will not display.

1.

First, stop any HTTP Server (IBM Http Server, IIS, or Sun ONE Web Server) running on the system.

2.

Insert the WebSphere CD into your CD
-
ROM drive.

3.

Navigate to the CD
-
ROM drive. For WebSphere base,

you will see the “installBase.bat” file for
Windows or “installBase.sh” for Unix. For WebSphere ND, you will see the “installDeployMgr.bat”
file for Windows or “installDeployMgr.sh” for Unix. You can run this command from a DOS
command window (Windows)
or xterm (Unix) to start the installation of WebSphere Application
Server component.

Installing Base on Windows

Execute
installBase.bat
-
silent


Installing ND on Windows

Execute
installDeployMgr.bat
-

silent


Installing Base on Unix

Execute
installBas
e.sh
-
silent

Installing ND on Unix

Execute
installDeployMgr.sh
-
silent

4.

The silent install will quietly install WebSphere without interaction. The silent install relies upon the
responsefile (wasBase.resp for WebSphere base; and DeployMgr.resp for WebSpher
e ND). The
responsefile parameters are pre
-
selected for PeopleSoft PeopleTools and application optimization.

The silent installation does not install any HTTP proxy server plugins or the IBM HTTP Server.


32

5.

You can monitor the installation process by viewing

the file log.txt in the temp directory. After the
installation completes this file is moved to the WebSphere logs directory.

6.

Refer to the Customer Connection link
ftp://ftp.peoplesoft.
com/outgoing/PTools/websphere/51
1
PT84
6

to check whether any iFixes are needed. If they are present, you must install them. Refer to the
readme.txt file to install them.


Note:

Check the logs for any errors encountered during the installation. WebSphere
Application
Server’s install log is located in <WAS_HOME>
\
logs
\
log.txt. The IBM HTTP Server log is in
<WAS_HOME>
\
logs
\
ihs_log.txt.


Veri fyi ng WebSphere Base Instal l ati on

1.

The First Steps for the WebSphere Application Server is launched after the installe
r delivers all of the
files.


2. Amidst the windows that may be visible on your workstation, find the window titled
WebSphere
Application Server
-

FirstSteps and

select
Verify Installation
.


33

4.

The results of running the Install Verification Test (ivt) sh
ould be successful as shown below. Note
that you may see a message saying “WebSphere Application Server is not running and could not be
started”. If the Application Server is not running it will be automatically started.


IVTL0095I: defaulting to host nat
hand and port 19080

IVTL0010I: Connecting to the WebSphere Application Server
WebSphereND1 on port: 19080



IVTL0020I: Could not connect to Application Server, waiting for
server to start

IVTL0025I: Attempting to start the Application Server

IVTL0030I: Run
ning cmd.exe /c
"C:
\
WebSphere51
\
AppServer
\
bin
\
startServer" server1

>ADMU0116I: Tool information is being logged in file

> C:
\
WebSphere51
\
AppServer
\
logs
\
server1
\
startServer.log

>ADMU3100I: Reading configuration for server: server1

>ADMU3200I: Se
rver launched. Waiting for initialization status.

>ADMU3000I: Server server1 open for e
-
business; process id is
3116





IVTL0050I: Servlet Engine Verification Status
-

Passed



IVTL0055I: JSP Verification Status
-

Passed



IVTL0060I: EJB Verification St
atus
-

Passed



IVTL0070I: IVT Verification Succeeded



IVTL0080I: Installation Verification is complete


If the tests are successful, select
Exit

on the window titled “
WebSphere Application Server
-

First
Steps
” window. This action will also close the wi
ndow titled FirstSteps Output


Verify Installation
Test.




34

Task 2
-
8:

Un
-
Installing WebSphere Base

If you want to un
-
install WebSphere 5.1, you can do so by invoking the uninstall program.

Note:

On Unix systems, if the DISPLAY variable is set,

then the uninstall program will work in
GUI mode, otherwise the command “uninstall

silent” can be invoked to run the uninstall
process silently.

1.

Stop WebSphere and any HTTP Server (IBM Http Server, IIS, or Sun ONE Web Server) running on
the system.

2.

To un
install WebSphere 5.1, type:
cd <WAS_HOME>
\
_uninst

and
run
the
uninstall.exe

command.

3.

Click
Next

to continue with the uninstall process. Click
Next
again on the next panel.

4.

You will get a panel as follows prior to the uninstall process.




5.

F
inally, click
Finish
to exit the wizard.

6.

The install directory structure must be removed manually. The uninstall is now complete
.

Note:

You may receive a warning that “GSKit cannot be uninstalled as it may be currently in use.”
If this occurs, you wi
ll need to remove that separately.




35

Un
-
Instal l i ng WebSphere Embedded Messagi ng


If you do not have IBM WebSphere MQ installed as a separate product on the machine, the
following steps can be carried out to manually uninstall WebSphere embedded messaging:


LINUX:


If you are certain that there is no embedded messaging data to preserve:

1.

Type
rm
-
fr /var/wemps /opt/wemps.

2.



rm
-
fr /var/mqm /opt/mqm.

3.

Type these commands to search for related packages:

o

rpm
-
qa | grep WS


o

rpm
-
qa | grep MQ

o

rpm
-
qa | gre
p wemps

And then
rpm
-
e <packagename>

to remove any WebSphere Application Server
-
related
packages found in above search.


AIX:

Installp

-
u wemps mqjava mq
m

Reply
y[
es] to all prompts.


SUN:

Use the following command as root to remove the embedded messaging feature from your system:

pkgrm wemps mqjava mqm
-
upd04 mqm

Reply y[es] to all prompts.


HP:

Start the SAM utility and verify that your DISPLAY and TERM
environment variables are set
properly:


1.

Click
Software management
.

2.

Click
View installed software
.

3.

Look for these two entries in the SD list:



MQSERIES
-
> B.11.530.01 WebSphere MQ for HP
-
UX



MQSERIES
-
> B.11.530.03 WebSphere MQ Update (U485562)

4.

Close th
e SD list.

5.

Click
Remove local host software
.

6.

On the
SD Remove list
, remove these instances, if they exist:

MQSERIES
-
> B.11.530.01 WebSphere MQ for HP
-
UX



MQSERIES
-
> B.11.530.03 WebSphere MQ Update (U485562) for
HP
-
UX

b.

Highlight the MQSERIES instances
on the SD List.

c.

Click
Actions > Remove...
.

d.

On
Remove Analysis

dialog, verify that
Status

is
ready
.

e.

Click
OK
.

f.

Check the result message displayed on the dialog.

g.

If the removal fails, follow the instructions that appear.

7.

Return to the
SD Remove List
.

8.

C
lick
IBM HTTP Server, MQSERIES, WEMPS, WSBAA, WSNAA,
and
gsk5bas
.

9.

Click
Actions > Mark for remove
.

10.

Click
Actions > Remove
.

11.

Click
OK

in the
Remove analysis

dialog box.

12.

Click
Logs

to display real
-
time removal of selected

packages.

13.

Exit SAM.


You can also execute this command as root to remove the embedded messaging feature from your
system:


36














WINDOWS:


If you have other instances of WebSphere Application Server products or the WebSphere MQ on the
same machine, and if they use the embedded messaging feature, do not remove the embedded
messaging.

Otherwise,
use the Add/Remove utility to r
emove the following programs, if listed:

1.

IBM WebSphere EMPS

2.

IBM WebSphere MQ


37





























































Un
-
Instal l i ng WebSphere ND

If you want to un
-
install WebSphere 5.1, you can do so by invoking the uninstall program
.

1.

Stop WebSphere and any HTTP Server (IBM Http Server, IIS, or Sun ONE Web Server) running on
the system.

2.

Insert the WebSphere CD into your CD
-
ROM drive.

3.

To uninstall WebSphere 5.1, type:
cd <install_directory>
\
_uninst

and type the
uninstall.exe

command
.

4.

Click
Next

to continue with the uninstall process. Click
Next
again until you get to the uninstall panel.

5.

Finally, click
Finish
to exit the wizard.

The install directory structure must be removed manually. The uninstall is now complete.






38

Starting, Stopping, and Administering WebSphere Base Server

Starti ng WebSphere

Windows

You may start the WebSphere Application Server from the First Steps panel or from a Command Prompt.

Fr
om a Command Prompt window,

1.

Type
cd <WAS_HOME>
\
bin
. (<WAS_HOME> is where WebSphere base was installed).

2.

Type
startServer server1
.

3.

After the server has started, you will see the message: “Server server1 open for e
-
business.”

C:
\
WebSphere51
\
AppServer
\
bin
\
startServer.bat server1

ADMU0116I: Tool information is being logged in file


C:
\
WebSphere51
\
AppServer
\
logs
\
server1
\
startServer.log

ADMU3100I: Reading configuration for server: server1

ADMU3200I: Server launched. Waiting for initialization status
.

ADMU3000I: Server server1 open for e
-
business; process id is 2880

Unix

You may start the WebSphere Application Server from the First Steps panel or using a script.

At a prompt,

1.

Type
cd <WAS_HOME>
\
bin
. (<WAS_HO
ME> is where WebSphere base was installed).

2.

Type
./startServer.sh server1
.

3.

After the server has started, you will see the message:
“Server server1 open for e
-
business.”

# ./startServer.sh server1

ADMU0116I: Tool information is being logged in file



/usr/WebSphere51/AppServer/logs/server1/startServer.log

ADMU3100I: Reading configuration for server: server1

ADMU3200I: Server launched. Waiting for initialization status.

ADMU3000I: Server server1 open for e
-
business; process id is 2880

Stoppi ng WebSpher
e

Windows

You may stop the WebSphere Application Server from the First Steps panel
.

From a Command Prompt
,

1.

Type
cd <WAS_HOME>
\
bin
. (<WAS_HOME> is where you installed your WebSphere base).

2.

Type
stopserver server1
.

3.

Afte
r the server has stopped you will see a message saying “Server server1 stop completed.”


C:
\
WebSphere51
\
AppServer
\
bin
\
stopServer.bat server1

ADMU0116I: Tool information is being logged in file


C:
\
WebSphere51
\
AppServer
\
logs
\
server1
\
stopServer.lo
g

ADMU3100I: Reading configuration for server: server1

ADMU3201I: Server stop request issued. Waiting for stop status.


39

4.

ADMU4000I: Server server1 stop completed.


Unix

You may stop the WebSphere Application Server fr
om the First Steps panel or using a script.


At a prompt,

1.

Type
cd <WAS_HOME>
\
bin
. (<WAS_HOME> is where you installed your WebSphere base).

2.

Type
./
stopserver.sh server1
.

3.

After the server has stopped you will see the message: “S
erver server1 stop completed.”


# ./stopServer.sh server1

ADMU0116I: Tool information is being logged in file


/usr/WebSphere51/AppServer/logs/server1/stopServer.log

ADMU3100I: Reading configuration for server: server1

ADMU3201I: Server stop req
uest issued. Waiting for stop status.

ADMU4000I: Server server1 stop completed.

Fi ndi ng Ports Used by WebSphere

You can use the administrative console to configure the Version 5 application server, to resolve conflicting
ports. Use this table to determine the default port values for the GUI and silent installations for both Bas
e
and ND and to determine which file the value is configured in.

Port name

WebSphere
Application Server

Network
Deployment

File

GUI

Silent

GUI

Silent

HTTP_TRANSPORT

9080

19080

NA

NA

server.xml

virtualhosts.x
ml

HTTPS Transport Port
(HTTPS_TRANSPORT)

9443

19043

NA

NA

HTTP Adm
in Console Port
(HTTP_TRANSPORT_ADMIN)

9090

19090

9090

19091

HTTPS Admin Console Secure Port
(HTTPS_TRANSPORT_ADMIN)

9043

19443

9043

19043

Internal JMS Server
(JMSSERVER_SECURITY_PORT)

5557

15557

NA

NA

server.xml

JMSSERVER_QUEUED_ADDRES
S

5558

15558

NA

NA

serverindex.x
ml

JMSSERVER_DIRECT_ADDRESS

5559

15559

NA

NA

BOOTSTRAP_ADDRESS

2809

12809

9809

19917

SOAP_CONNECTOR
-
ADDRESS

8880

18880

8879

18889

DRS_CLIENT_ADDRESS

7873

17873

7989


SAS_SSL_SERVERAUTH_LISTEN
ER_ADDRESS

0

0

9401

19819

CSIV2_SSL_S
ERVERAUTH_LIST
ENER_ADDRESS

0

0

9403

19502

CSIV2_SSL_MUTUALAUTH_LIST
ENER_ADDRESS

0

0

9402

19503

IBM HTTP Server Port

80

80

NA

NA

virtualhosts.x
ml

plugin
-
cfg.xml

IBM HTTPS Server Admin Port

8008

18008

NA

NA

plugin
-
cfg.xml

CELL_DISCOVERY_ADDRESS

NA

NA

7277

17278

serverindex.x
ml

ORB_LISTENER_ADDRESS

NA

NA

9100

19703

CELL_MULTICAST_DISCOVERY
_ADDRESS

NA

NA

7272

17272


40

WebSphere Application Server Base Version 5.1 default port definitions



Please note that if the Modify Ports for Coexistent was checked during installation, the port values may be
different

than the above table. A file called Ports.properties is placed in the temp directory (On windows
it’s the user’s temp directory. On Unix the file is placed in /tmp ). The contents of the file look like:

#

#Tue Oct 28 09:41:03 MST 2003

sasSSLServerauthL
istenerAddress=9819

drsClientAddress=7999

csiv2SSLMutualauthListenerAddress=9503

adminConsole=9091

cellDiscoveryAddress=7278

jmsServerQueuedAddress=5568

bootstrapAddress=9917

soapConnectorAddress=8889

httpsTransport=9444

jmsServerDirectAddress=5569

orbList
enerAddress=9703

secureAdminConsole=9044

httpPort=81

csiv2SSLServerauthListenerAddress=9502

httpTransport=9085

jmsServerSecurityPort=5567

httpAdminPort=8009


WebSphere Logs

WebSphere has logs for different components.


Component

Log File

HTTP Server plu
g
-
in

<WAS_HOME>/logs/native.log

JVM Logs

<WAS_HOME>/logs/<server_name>/SystemOut.log

<WAS_HOME>/logs/<server_name>/SystemErr.log

Process (Native) logs

<WAS_HOME>/logs/<server_name>/native_stdout.log

<WAS_HOME>/logs/<server_name>/native_stderr.log

IBM se
rvice (Activity) log

<WAS_HOME>/logs/activity.log


HTTP Server plug
-
in log

The HTTP server plug
-
in log contains error information about the plug
-
in. If the plug
-
in cannot be loaded
or the plugin
-
cfg.xml cannot be accessed, this log will help resolve thos
e issues.


JVM Logs

JVM logs are created by redirecting System.out and System.err streams of the JVMs. These logs contain
information and errors from the JVM. System.out is used to monitor the health of the application and may
contain java exceptions. S
ystemErr.out contains exception stack trace information. Exceptions may appear
in both logs.


Process Logs

The process logs contain the stdout and stderr streams of the native modules. These files will contain
problems from the native WebSphere code.




41



IBM Service Log

The IBM service log is a special log written in a binary format that captures events that show a history of
WebSphere Application Server activities.
By default, the IBM service log is shared among all server
processes for a node.


To view

the service log, use the
showlog
command in the <WAS_HOME>/bin
directory. This command
dumps the binary log file to standard out or a file. The
format is:

showlog binaryFilename [outputFilename]


outputFilename is optional. If no file name is given,
showl
og
dumps the service log file to standard out. For
example:

showlog ../logs/activity.log


Admi ni steri ng WebSphere

To invoke the WebSphere Administration Console

Start WebSphere server1 as described above if it is not already started. You can now invoke th
e
WebSphere Administration Console by typing the URL
http://localhost:9090/admin

(where 9090 is the
default administration port) from a browser window. Type any user ID to enter the Administration console.
The

console is where you can centrally administer the WebSphere base that you have just installed. Note
that port 9090 is the default admin client port without co
-
existence. In the case of co
-
existence, if you
selected any other port (e.g., port 19090), you

will see that port here. To exit the console, simply click on
the exit tab on the top of the console window.

Note

If WebSphere is installed silently or with modified ports, the First Steps link to the Administrative
Console will not work.
Refer to Peopl
eBooks : WebSphere Administration guide for steps to
i
nvoke the WebSphere Administration console.


Note

On AIX systems, the AIX Web
-
based System Manager (
WSM) may be running on port 9090. The
WSM will prevent the WebSphere Admin Console from running on port 9090. Please change the
WebSphere Admin Console Port to prevent this conflict.


Note

On Unix systems, if Netscape is installed in a non
-
default director
y, the link to the Admin Console
in First Steps may fail.






42


Troubl eshooti ng


Instal l ati on and Upgrade


Facing problems
installing WebSphere
Base,

w
here should I look for
clues?



Browse the relevant log files for clues:

o

The main installation log fil
e:
install_dir
/log.txt.

o

IBM Http Server log:
install_dir
/ihs_log.txt.

o

The log file produced when the default application .ear file is installed is:
install_dir
/logs/installDefaultApplication.log.


Ensure that you have installed the correct level of depe
ndent software, such as operating system



version and revision level, by reviewing


http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.htm
l


Not able to Upgrade WebSphere Base or ND.
UpdateBase and/or ND
are

not able to install the
Fix Pack 1 successfully
. What to do next?


1
.
If the installation of the Fix Pack 1 does not complete successfully, browse through the following logs:

o

Unix: /tm
p/fixpacks.log

Windows:

C:/temp/fixpack.log


o

WebSphere update logs:
<was
-
home>/logs/update


2.
You can also apply the Fix Pack using GUI, by
invoking

UpdateWizard.sh

(
bat
)


placed beneath


<was
-
hom
e
>
/update.


Ex: /usr/WebSphere51/AppServer/update/Upd
ateWizard.sh

The GUI Wizard will ask to supply
the relevant WebSphere Base
-
Home

or ND
-
Home

install,
followed
by Fix Pack location.

The location of the Fix Pack
for WebSphere Base
is typically <
was
-
home
>
/update/fixPacks_base

and
ND

-

<ND
-
home>/update/f
ixPacks_nd.