Compilation date:
2003/06/11
© Copyright International Business Machines Corporation 2003. All rights
reserved.
US Government Users Restricted Rights – Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Abstract: Documentation for Fix Pack 2 of
Version 5 of the WebSphere Application Server product family.
Table
of Contents
If you are installing Fix Pack 2 on a Windows NT system, you might encounter an error that causes the Fix Pack installation to fail. The error occurs when installing the component prereq.jsse. You are notified of the error by the message "Fix Pack installation failed".
The message refers to an installation log, which contains this entry for the error:
Exception: WUPD0248E: Fix pack update failure: The processing of fix pack was50_fp2_win, component prereq.jsse failed.
If you get this error, click Finish in the installation GUI to immediately exit the installation GUI program. Open a command prompt window. Go to the java subdirectory under the installation root directory where WebSphere Application Server, Version 5 is installed. For example, change directory to "C:\Program Files\WebSphere\AppServer\java. Run this command:
attrib -r /s
Install Fix Pack 2 again by running the updateWizard.bat command script. The Wizard shows Fix Pack 2 as partially installed, which you can ignore. The installation program continues the installation with the 'prereq.jsse' component. The final component 'webui' takes about 5 minutes to install.
The problem is related to the read-only file attribute being set for a number of files in the install_root/java directory and subdirectories.
There are several platform-specific
fix packs that are each referred to as Fix Pack 2 for their respective product
and platform. The complete list of fix packs appears in a series of tables in
the Retrieving Fix Pack 2 section, which is organized
by product as follows:
This document also describes
prerequisites, space requirements, download instructions, and where to find
detailed installation instructions and more information about the update
installer application.
You can find additional information
in the Version 5 InfoCenter located at http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=ApplicationServer.
The readme_updateinstaller.html file in the fix pack contains more
detailed information about applying fix packs to more than one product on a
machine. It also has detailed information about each of the two interfaces to
the update installer application, which are the updateSilent and updateWizard
interfaces.
The list of fixes and the Release
Notes for Fix Pack 2 are on the product support Web site at http://www.ibm.com/software/webservers/appserv/support.html.
Install the appropriate Fix Pack 2 on
top of the Application Server client, the Express product, the base WebSphere
Application Server product, the Network Deployment product, or on top of the
A Java runtime environment must be
available, even if the Java installation is not being updated.
Download Fix Pack 2 to a read/write
directory as described in Steps for installing Fix Pack 2.
Installing from a read only drive is not supported.
All required hardware and software
prerequisites are described in the Supported hardware and software Web site at
http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Space requirements vary depending
on what you are installing. The size of each download is available on the
Support site. For a fix pack, have approximately 400 MB of free space in the /tmp directory and another 400 MB in
the file system that hosts the WebSphere Application Server image (typically /usr) on a UNIX-based platform, or
approximately 800 MB of free space on the disk drive where you are installing
on a Windows platform.
Verify that the free space is
available before beginning the installation. After unpacking the ZIP file, you
can delete the ZIP file to free space if necessary. After it is installed, the
Fix Pack 2 code increases the IBM WebSphere Application Server installation and
run-time footprints by a small amount.
Space is also required for the /update directory of the product
installation root. The space required is about the same as the size of the fix
pack, typically somewhere between 50 MB to 250 MB.
Space is also required for backup
files in the /properties/version/backup directory of the product
installation root. The space required is about the same as the size of the fix
pack, somewhere between 50 MB to 250 MB, varying by product and platform.
The update installer checks for
required space before it installs the fix pack. However, there is a bug in the
space checker when installing Fix Pack 2.
When installing Fix Pack 2, the
update installer checks for required disk space in the /tmp directory and in the backup directory. If there is not enough
space in the /tmp directory or there is not enough
space in the backup directory, the update installer
issues a warning message.
A temporary problem exists where
the update installer issues the warning for both directories when it should
issue a warning message for the /tmp directory only. For example, if there is less than 248 MB
in the /tmp directory and more than 248 MB in
the installation root, messages similar to these appear:
"Insufficient disc space found in /tmp. This fix pack installation requires 248 megabytes." "Insufficient disc space found in /WebSphere/AppServer/properties/version/backup. This fix pack installation requires 248 megabytes."
To fix the problem, allocate enough
space in the /tmp directory. Neither message will
appear.
Fix Pack 2 platform-specific files
for the WebSphere Application Server - Express product:
|
Operating system platform |
Fix Pack 2 ZIP file |
Fix Pack 2 ID |
|
AIX |
was50_express_fp2_aix.zip |
was50_express_fp2_aix |
|
HP-UX |
was50_express_fp2_hpux.zip |
was50_express_fp2_hpux |
|
Linux |
was50_express_fp2_linux.zip |
was50_express_fp2_linux |
|
Solaris |
was50_express_fp2_solaris.zip |
was50_express_fp2_solaris |
|
Windows NT and
Windows 2000 |
was50_express_fp2_win.zip |
was50_express_fp2_win |
Fix Pack 2 platform-specific files
for the base WebSphere Application Server product:
|
Operating system platform |
Fix Pack 2 ZIP file |
Fix Pack 2 ID |
|
AIX |
was50_fp2_aix.zip |
was50_fp2_aix |
|
HP-UX |
was50_fp2_hpux.zip |
was50_fp2_hpux |
|
Linux |
was50_fp2_linux.zip |
was50_fp2_linux |
|
Solaris |
was50_fp2_solaris.zip |
was50_fp2_solaris |
|
Windows NT and
Windows 2000 |
was50_fp2_win.zip |
was50_fp2_win |
Fix Pack 2 platform-specific files
for the Network Deployment product:
|
Operating system platform |
Fix Pack 2 ZIP file |
Fix Pack 2 ID |
|
AIX |
was50_nd_fp2_aix.zip |
was50_nd_fp2_aix |
|
HP-UX |
was50_nd_fp2_hpux.zip |
was50_nd_fp2_hpux |
|
Linux |
was50_nd_fp2_linux.zip |
was50_nd_fp2_linux |
|
Solaris |
was50_nd_fp2_solaris.zip |
was50_nd_fp2_solaris |
|
Windows NT and
Windows 2000 |
was50_nd_fp2_win.zip |
was50_nd_fp2_win |
Fix Pack 2 platform-specific files
for the
|
Operating system platform |
Fix Pack 2 ZIP file |
Fix Pack 2 ID |
|
AIX |
was50_pme_fp2_aix.zip |
was50_pme_fp2_aix (to extend the base product) |
|
was50_pme_nd_fp2_aix (to extend the Network Deployment product) |
||
|
HP-UX |
was50_pme_fp2_hpux.zip |
was50_pme_fp2_hpux (to extend the base product) |
|
was50_pme_nd_fp2_hpux (to extend the Network Deployment product) |
||
|
Linux |
was50_pme_fp2_linux.zip |
was50_pme_fp2_linux (base) |
|
was50_pme_nd_fp2_linux (Network Deployment) |
||
|
Solaris |
was50_pme_fp2_solaris.zip |
was50_pme_fp2_solaris (base) |
|
was50_pme_nd_fp2_solaris (Network Deployment) |
||
|
Windows NT and
Windows 2000 |
was50_pme_fp2_win.zip |
was50_pme_fp2_win (base) |
|
was50_pme_nd_fp2_win (Network Deployment) |
Fix Pack 2 platform-specific files
for the WebSphere Application Server client:
|
Operating system platform |
Fix Pack 2 ZIP file |
Fix Pack 2 ID |
|
AIX |
was50_client_fp2_aix.zip |
was50_client_fp2_aix |
|
HP-UX |
was50_client_fp2_hpux.zip |
was50_client_fp2_hpux |
|
Linux |
was50_client_fp2_linux.zip |
was50_client_fp2_linux |
|
Solaris |
was50_client_fp2_solaris.zip |
was50_client_fp2_solaris |
|
Windows NT and
Windows 2000 |
was50_client_fp2_win.zip |
was50_client_fp2_win |
1.
Run
the backupConfig command to back up configuration files. See Backing
up and restoring administrative configurations (trun_svr_conf_backup) in
the online InfoCenter located at
http://publib.boulder.ibm.com/infocenter/wasinfo/topic/com.ibm.websphere.base.doc/info/welcome_base.html.
2.
Verify
required disk space.
3.
After
backing up the configuration and before installing Fix Pack 2, stop all Java
processes that use the IBM Developer Kit that WebSphere Application Server
provides to support the Java 2 SDK on your operating system platform, such as
the IBM Developer Kit for AIX, Java Technology Edition.
Stop all application server processes, the nodeagent process, the deployment
manager process, and all server processes, such as the jmsserver process, that
belong to serviceable features. Features with server processes include the IBM
HTTP Server and the embedded messaging feature. Stop all Java processes, if
necessary. If you do install a fix pack while a WebSphere Application
Server-related Java process is running, IBM does not guarantee that the product
can continue to run successfully, or without error.
4.
Obtain
each Fix Pack 2 file that you need from the product support Web site located at
http://www-3.ibm.com/software/webservers/appserv/was/support/.
Download the files into the install_root/update directory, which you can create.
Note: The update installer may hang during the base Fix Pack
was50_fp2_<platform> installation when installing in the recommended
order (Base 5.0, Enterprise Edition 5.0, Base Fix Pack 2, Enterprise Edition
Fix Pack 2). If this happens install in
this order Base 5.0, Base Fix Pack 2, Enterprise Edition 5.0, Enterprise
Edition Fix Pack 2. To do this:
1.
Stop Base
Fix Pack 2 installation by killing the process.
2.
Uninstall
Enterprise Edition 5.0.
3.
Ensure
server starts successfully.
4.
Stop
the server.
5.
Install
Base Fix Pack 2.
6.
Repeat
steps 3 and 4.
7.
Install
Enterprise Edition 5.0.
8.
Install
Enterprise Edition Fix Pack 2.
9.
Repeat
steps 3 and 4.
Note: When applying a Fix Pack to a remote WebServer, use the base
Fix Pack was50_fp2_<platform> , not the
Network Deployment or Enterprise Edition Fix Pack. This is because you initially
installed the remote WebServer using the base IBM WebSphere Application Server, Version 5.
5.
At a
system command prompt, change the directory to where you downloaded the file,
for example:
# cd /usr/WebSphere/DeploymentManager/update
6.
Unzip
the file.
Note: On Windows platforms, the pkunzip utility might not decompress the
download image correctly. Use another utility (such as WinZip) to unzip the
image.
7.
(Optional) Delete the ZIP file if you need
more space.
8.
At a
system command prompt, call the updateWizard.sh or the updateWizard.bat script to begin the installation. Refer to the readme_updateinstaller.html (or PDF) file for detailed
information about using the updateWizard script.
On some platforms, the updateWizard interface to the
update installer program does not recognize the existing WebSphere Application
Server product. This is due to a limitation in the InstallShield for
MultiPlatforms (ISMP) program that the update installer program uses.
The ISMP program does not recognize previous installations
of WebSphere Application Server on some operating platforms.
To work around the problem, click Specify product
information and type the fully qualified installation root directory for
the existing product in the Installation directory field of the updateWizard
panel.
Open
the readme_updateinstaller file in the format of your choice
for more information about using the updateWizard.sh or the updateWizard.bat scripts, and for information about using the updateSilent.sh or updateSilent.bat scripts. The updateSilent scripts
let you install a fix pack silently without interaction. It is useful for
installing a fix pack in an environment that does not provide a graphical user
interface, for example.
The
readme_updateinstaller file describes an overall
procedure for installing multiple fix packs on machines with multiple products,
including how to install an Enterprise product fix pack, and how to install fix
packs on nodes in a deployment manager cell.
The
readme_updateinstaller file describes how to verify that
you have successfully installed the fix pack.
The
readme_updateinstaller file also describes how to
uninstall a fix pack.
The following terms are trademarks of IBM Corporation in
the United States, other countries, or both:
Java
and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.
Microsoft,
Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Intel,
Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in
the United States, other countries, or both.
UNIX
is a registered trademark of The Open Group in the United States and other
countries.
SET
and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.
Other
company, product, or service names may be trademarks or service marks of
others.