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.
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:
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 Enterprise product that extends the base product or the Network Deployment product.
Enterprise 5.0 customers must wait for the Enterprise Fix Pack 2 before applying Fix Pack 2 to the base WebSphere Application Server product or to the Network Deployment product. The Enterprise product must be at the same fix level as the base product or the Network Deployment product that it extends. Applying Fix Pack 2 to the base product without applying it to the Enterprise product causes the Enterprise environment to not work.
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 |
Linux for S/390 | was50_express_fp2_linux390.zip | was50_express_fp2_linux390 |
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 |
Linux for S/390 | was50_fp2_linux390.zip | was50_fp2_linux390 |
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 |
Linux for S/390 | was50_nd_fp2_linux390.zip | was50_nd_fp2_linux390 |
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 Enterprise product:
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) | ||
Linux for S/390 | was50_pme_fp2_linux390.zip | was50_pme_fp2_linux390 (base) |
was50_pme_nd_fp2_linux390 (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 |
Linux for S/390 | was50_client_fp2_linux390.zip | was50_client_fp2_linux390 |
Solaris | was50_client_fp2_solaris.zip | was50_client_fp2_solaris |
Windows NT and Windows 2000 | was50_client_fp2_win.zip | was50_client_fp2_win |
# cd /usr/WebSphere/DeploymentManager/update
Note: On Windows platforms, the pkunzip utility might not decompress the download image correctly. Use another utility (such as WinZip) to unzip the image.
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.
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.