<<

. 11
( 87 .)



>>

plication Server 5.0 in a secured zone. We are going to install Microsoft IIS
plug-ins on a remote Web server and use an existing WebSphere Application
Server 5.0 on sandbox1.rigorconsultants.com to install the portal.
While there is an option to upgrade the WebSphere Application Server to a
new version, the upgrade will not do the migration of security objects, dep-
recated API, cluster con¬guration, etc. It will just upgrade the server code.

1. On the Web Server, http.rigorconsultants.com, ¬rst check to
see if the plug-ins have been installed in the httpd.conf ¬le. If
you see the following lines then go to step 12:
LoadModule ibm_app_server_http_module
"C:\WebSphere\AppServer/bin/mod_ibm_app_server_http.dll"
WebSpherePluginConfig "C:\WebSphere\AppServer/config/cells/plugin-
cfg.xml"




Figure 2-13 Installations on existing Web server and existing Web application server.
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




Installing WebSphere Portal on Windows 2000 Server 37


2. Stop the Web Server
3. Place the WebSphere Portal CD, which contains the WebSphere
Application Server installation program (for Windows it should be
CD 1.1 of WebSphere Portal V5.0), in http.rigorconsultants.com CD
drive.
4. Launch the WebSphere Application Server installation entering in a
command prompt drive:\was\win\WAS50\install.exe, where
the drive is your CD drive. If you are installing WebSphere Portal
5.0, then WebSphere Application Server Enterprise Fixpack 1 (base
plus frame) must be installed with the additional ¬xes required by
WP. If you are installing WP 5.0.2, then WebSphere Application
Server Enterprise Fix Pack 2 (base plus frame) must be installed
with the additional ¬xes required by WP.
5. Select the language you want to use for the installation, and click
OK.
6. Click Next on the welcome panel, indicate that you accept the
license agreement, and click Next.
7. Select Custom.
8. On the features panel in Figure 2-14, deselect all features except Web
Server Plugins and the entry for the speci¬c Web server for which
you are installing the plug-in. Click Next.




Figure 2-14 IBM WebSphere Application Server features panel.
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




38 Chapter 2


9. Specify the directory path where you want to install the WebSphere
Application Server ¬les. This path must be the same as that used for
the WebSphere Application Server installed on the local machine.
Click Next.
10. Specify the location of the Web server con¬guration ¬le, if
requested. For IIS, it is not requested. Click Next.
11. Finish the installation.
12. Place CD in sandbox1.rigorconsultants.com.
13. Perform steps 1“7 in the previous section. Choose custom
installation.
14. Select Con¬gure to an Existing Install of WebSphere Application
(see Figure 2-15). Click Next.
15. The installation program will then ¬nd the location of your WAS
instance (as indicated in Figure 2-16). If it does not ¬nd it, click on
Browse and locate the directory. Click OK and then Next.
16. The rest of the install is same as steps 11“14 of the quick install.
17. Verify the Web Server is running and create a back-up copy of
<wp_root>/config/wpconfig.properties file.




Figure 2-15 Choosing type of WAS installation.
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




Installing WebSphere Portal on Windows 2000 Server 39




Figure 2-16 Finding the location of the WAS instance.


18. Using a text editor, open <wp_root>/config/wpconfig
.properties, uncomment and set
WpsHostName=localhost
WpsHostPort=80

WpsHostName is the fully quali¬ed host name of the machine
running WebSphere Portal while WpsHostPort is the port number
that your Web Server is listening for HTTP traf¬c. You may not have
to change any settings here.
19. Save the ¬le, open a command prompt, and change the directory to
<wp_root>/config.
20. Enter the command WPSConfig.bat httpserver-config.
21. Restart the Web Server on http.rigorconsultants.com and then
restart the WebSphere Portal.


Installing WebSphere Portal Fixpack 2
In order to run WebSphere Portal 5.0.2, you have to install WebSphere Portal
Fixpack 2. Assume that security is not installed and that this is a Windows
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




40 Chapter 2


installation. Consult the readme ¬les before you update. To do so, perform
the following steps:

1. Stop your Web server and all WebSphere servers, including WP.
2. On the IBM site, download the WebSphere Application Server base
¬xpack 2 for Windows. It should be about 221 MB. Unzip the ¬les
and install the ¬xpack as per the instructions in the readme.
3. On the IBM site, download the WebSphere Application Server
Enterprise Fix Pack 2 for Windows. It should be about 105 MB.
Unzip the ¬les and install the ¬xpack as per the instructions in the
readme.
4. Restart the servers and ensure they successfully start. Then stop the
servers.
5. On the IBM site, download the WebSphere Portal Fix Pack 2 for
Windows. You need to download the ¬xpack 2 ¬le. It should be
about 359 MB. On the same download page, also download the
WAS 5.0.2 additional ¬xes ¬le. It should be about 14 MB. Unzip the
¬les into a directory called <wp_root>\update.
6. Install the WP_PTF_502.jar using the UpdateWizard. Choose all
the ¬xes and apply them. This applies to additional ¬xes to
WebSphere Application Server so you can install WebSphere
Portal 5.0.2.
7. Set up the Java environment by running
<was_root>\bin\setupCmdLine.bat.
8. Open a command prompt and change the directory to
<wproot>\update.
9. Enter the command, updatePortal -fixpack -installDir
"<wp_root>" -fixpackDir "<wp_root>\update"
-install -fixpackID WP_PTF_502
10. Upon successful completion, change the directory to
<wp_root>\config.
11. Enter the command WPScon¬g.bat WP-PTF-502-
DPortalAdminPWD=portalAdminPassword, where
portalAdminPassword is your WebSphere Portal administrator
password. You must perform this step right after you have applied
the ¬xes or the portal will be corrupted. This command must
complete successfully. It will take quite a while to execute. If it does
not complete successfully, then run WPSconfig.bat UNINSTALL-
WP-PTF-502 DPortalAdminPWD=portalAdminPassword,
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




Installing WebSphere Portal on Windows 2000 Server 41


where portalAdminPassword is your WebSphere Portal
administrator password, correct the problem, and redo this step.
12. Upon successful installation, start the Web Server and WebSphere
Portal and log in. Check the version number on the WebSphere
Portal Welcome Screen. It should now read IBM WebSphere Portal
5.0.2 in the lower left-hand corner.
13. Log in as an administrator. Click Document Manager and update
the search index.


Summary
In this chapter, you have experienced the radically simpli¬ed WebSphere
Portal installation, which provides a dramatic improvement on the cus-
tomer experience. But most customer con¬gurations require special instal-
lations con¬gurations. The next chapter will explore installations for Linux
platforms and examine more complex con¬gurations.
P1: GIG
WY009-02 WY009-BenNatan-v1.cls May 13, 2004 21:54




42
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




CHAPTER

3
Installing WebSphere
Portal on Linux

In the last chapter we showed how to install WebSphere Portal on a Win-
dows 2000 Server platform. From the WebSphere Portal installation manual,
much of the installation process can be extrapolated to the other platforms
by making a few adjustments, right? It would be great if this were true, but
it is not! The differences are a result of the lack of integration into the Linux
user interfaces. The integration is more dif¬cult due to numerous varieties
of Linux user interfaces.
In this chapter you are going to learn how to install and uninstall Web-
Sphere Portal on a Linux platform in either a graphics or a text environment.
Linux was chosen due to the popularity of the platform and the close simi-
larities to the zLinux, Solaris, and AIX installations.



Installing on Linux
So, you™re going to install WebSphere Portal on Linux. First, let™s deal with
the urban legends. Despite what it says in the installation manual, Web-
Sphere Portal does not work with all versions and permutations of Linux
(see Figure 3-1). WebSphere Portal 5.0.2 has been certi¬ed with
RedHat Enterprise Linux AS for Intel, RedHat Linux for Intel (x86) 8.0 2.4,
RedHat Linux for zSeries 7.2 2.4, SuSE Linux for Intel (x86) 7.3 2.4, SuSE
SLES for Intel (x86) 7 2.4, SuSE SLES for Intel (x86) 8 2.4, SuSE SLES for S/390
8 2.4, and SuSE SLES for S/390 7 2.4. For installation, you might be con-
sidering doing a full install. However, this will install IBM HTTP 1.3.26.1,
which is not recommended for Unix systems. IBM HTTP 2.0.42.21 is based


43
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




44 Chapter 3




Figure 3-1 The Linux con¬guration.


on Apache 2.0, which enables for Unix threading in hybrid multiprocess,
multithreaded mode. Realistically, most installations install the IBM HTTP
Server on a separate server.
The installation you should be examining, which we will use as an exam-
ple, is a custom installation using IBM HTTP 2.0.42.2 as the Web server and
an installation of WAS 5.0 with WebSphere Portal 5.0 using Cloudscape on
Red Hat 8.0 with the Gnome desktop.
The hardware requirements are as follows:
A Pentium 4 processor at 1.4 GHz or higher
1 GB of RAM or more per processor (this is very important)
1.5 GB or more disk space on the root directory, 2.5 GB or more on
/opt directory, and 500 MB or more for /home directory
Network connectivity with a static IP address and a con¬gured, fully
quali¬ed host name


Getting Information on Your Linux Server

<<

. 11
( 87 .)



>>