. 10
( 87 .)


properly con¬gured. In a command prompt, ping your server™s fully
quali¬ed domain name and see if your IP comes up and four
successful replies are returned.
4. Make sure that the following ports are not being used by typing
netstat“an in a command prompt:
443 (standard HTTPS port)
523 (DB2 Administration Server)
8008 (IBM HTTP Server Administration port)
50000 (DB2 instance connection port)
50001 (DB2 instance interrupt port)
50002 (DB2 Control Server)
55555 (WAS database port)
9081 (Default Portal Port)
9090 (WAS Administration port)
5. If you are going to set up WebSphere Application Server or IHS as a
service, make sure that the user account you will use to install
WebSphere Portal is a local Windows user ID, part of the
administrators group, and has the user rights to Act as part of the
Operating System and Log on as a service. To add or view User rights
select Start ➪ Programs ➪ Administrative Tools ➪ Local Security
Policy. Double click Local Policies and then double click User Rights
Assignment. Double click on the user right you are interested in and
then modify it if required.
6. Make sure Microsoft Internet Information Services is not running
since it listens on the same port as IBM HTTP Server. Go into Services
under Administrative Tools and stop or disable World Wide
Publishing Service.
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

28 Chapter 2

7. Make sure that PATH environment variable is not set too long. If it is,
you may get a message in the wpsinstalllog.txt stating the
input line is too long or the syntax of the command is incorrect.
8. Disable any ¬rewall products.

Okay, now you are ready to go.

Installing on Your Windows Server
To install WebSphere Portal:

1. Disable any ¬rewall on the server where WP will be installed. After
the install, re-enable it and open the appropriate ports and set
appropriate rules.
2. Insert the Setup disk in the CD drive. The program should
automatically start unless the autostart function is disabled. If it is
so, then run install.bat from the root directory of the CD.
3. Select the language for the install and click OK.
4. The Welcome panel will then be displayed. You will then be given
the option to browse the infocenter if you choose Launch Infocenter.
Otherwise click Next.
5. Figure 2-2 will then appear. This is the license agreement. Review
the license agreement and if you accept click Next. If you don™t then
hit Cancel and return the software.
6. The installation then checks the machine for operating system and
software prerequisites. If you are installing on Windows XP
Professional (yes, you can but it is not supported so users beware!),
you will get an error message but just ignore it and hit Next.
7. Figure 2-3 will then appear giving you a choice of a Full or Custom
install. Choose Full.
8. In Figure 2-4, you will then be asked to specify the directory to
install WebSphere Application Server. If the directory does not exist,
it will be created. By default, IBM suggests that you install in
c:\Program Files\WebSphere\AppServer; however, you
may instead want to install in c:\WebSphere since the directories
are easy to get when you are accessing them in a command prompt.
Enter the directory and click Next.
9. The next screen (see Figure 2-5) asks you to specify the directory to
install the IBM HTTP Server. Choose the default. If the directory
does not exist, it will be created. Click Next.
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

Figure 2-2 WebSphere Portal license agreement.

Figure 2-3 Choosing installation type.

WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

Figure 2-4 Specifying WebSphere Application Server installation directory.

Figure 2-5 Specifying IBM HTTP Server installation directory.

WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

Installing WebSphere Portal on Windows 2000 Server 31

Figure 2-6 Specifying whether you want to run services.

10. Now you are asked (see Figure 2-6) if you want to run WebSphere
Application Server and IBM HTTP as services. If you choose this
option, specify a user name and password that has administrator
privileges. The user ID may have the policy rights to “Log on as a
service and Act as port of the operating system.” If the user ID does
not have them, the installation program will update the user ID and
ask you to log out and log back before continuing with the
installation. You should install WebSphere Application Server and
IBM HTTP as services so they can be run remotely without the
administrator logged in.
11. Specify the node name (see Figure 2-7) where you want the
WebSphere Portal application to be installed within the WebSphere
Application Server cell. This value must be unique and is usually
the host name of the computer. Also enter the fully quali¬ed host
name or the static IP address of the computer running WebSphere
Application Server. Click Next. In Figure 2-6, you choose a node
name sandbox1 and a fully quali¬ed host name sandbox1
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

32 Chapter 2

Figure 2-7 Specifying physical location of WebSphere Portal.

12. In the next screen (see Figure 2-8), you will be asked where you
want to install WebSphere Portal. Usually it is installed off the
WebSphere directory root as a peer to the WebSphere Application
Server. Click Next.
13. Enter the user ID and password for the WebSphere Portal
Administrator (see Figure 2-9). The password and user ID must be
at least ¬ve letters long and contain no blanks. This user ID is
speci¬c to the WebSphere Portal and does not have to be an
Operating System User ID but it must conform to the rules of the
LDAP if you are using an LDAP to manage your users.
14. Verify the components to be installed and click Next.

That™s all the information you need to give. It™s that simple. After you click
Next, the program starts installing the selected components. You see the
progress indicator moving as the components are installed. It will probably
take an hour or two, depending on your system™s performance. When the
installation is ¬nished, a con¬rmation panel is displayed with a listing of
the components installed. The con¬rmation panel will also display the port
number used to access the portal. The port number is also stored in the
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

Figure 2-8 Specifying WebSphere Portal installation directory.

Figure 2-9 De¬ning WebSphere Portal administrator.

WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

34 Chapter 2

Figure 2-10 Starting the Portal Server.

WpsHostport property <wp_root>/config/wpconfig.properties
¬le. Record the property number and click Finish. Menu entries will be
added under Start ➪ Programs for IBM HTTP Server and WebSphere Ap-
plication Server and WebSphere Portal. Since IBM HTTP was set up as a ser-
vice, it will start automatically when you boot the server. However, to start
the Portal Server you will need to click Start ➪ Programs ➪ WebSphere ➪
Portal Server V5.0 ➪ Start the Server. A command box will appear. If you
have a successful start, you will see entries in the command box similar to
Figure 2-10.
To verify the installation was correct, the following steps are necessary:
1. Make sure the IBM HTTP Server is installed and is not in con¬‚ict
with another HTTP server such as IIS or Apache. On your Web
browser enter your fully-quali¬ed host name in the address bar (e.g.,
sandbox1.rigorconsultants.com). You should see a page with
“Welcome to IBM HTTP Server” (see Figure 2-11).
2. Start the portal server by going to Start menu and clicking
Programs ➪ IBM WebSphere ➪ Portal Server V5.0 ➪ Start the Server.
3. Enter in the address bar in your browser the URL
where hostname.yourco.com is the WebSphere Portal fully-quali¬ed
host name and port is the port number in the con¬rmation panel
(usually 9081). In our example. It is http://www
.rigorconsultants.com:9081/wps/portal. Click Go and you
should see the WebSphere Portal Welcome Page as shown in
Figure 2-12. Please note that a full installation does not
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

Figure 2-11 IBM HTTP Server Welcome screen.

Figure 2-12 WebSphere Portal Server Welcome screen.

WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54

36 Chapter 2

con¬gure WebSphere Portal with the IBM HTTP Server even though
it is installed with it. This must be done separately. By default,
WebSphere Portal uses the WebSphere Application Server internal
HTTP server (port 9081).

Installing with an Existing Web Server and an
Existing WebSphere Application Server
This installation is relatively easy. Except in the real world, you rarely install
with a new instance of the Web server and a new instance of WebSphere
Application Server. Here is an example of a more realistic install. Figure 2-13
shows a Web server in the DMZ connected to an existing WebSphere Ap-


. 10
( 87 .)