Compilation date: 2003/11/19
© 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 Cumulative Fix 2 of Version 5.0.2 of the WebSphere Application Server product family.
Enterprise customers installing Base or Network Deployment Cumulative Fix 2 must also install the Enterprise Cumulative Fix 2.
Enterprise customers installing Enterprise Cumulative Fix 2 must also install the Base or Network Deployment Cumulative Fix 2.
Before uninstalling WebSphere Application Server 5.0.2 Cumulative Fix 1 or 2, rename the WAS_HOME/cloudscape50 and WAS_HOME/cloudscape51 to, for example, WAS_HOME/cloudscape50_original and WAS_HOME/cloudscape51_original. Then uninstall the cumulative fix. After uninstalling the cumulative fix, rename the directories back to WAS_HOME/cloudscape50 and WAS_HOME/cloudscape51. This will avoid the directories being removed during the uninstall.
There are several platform-specific cumulative fixes that are each referred to as Cumulative Fix 2 for their respective product and platform. The complete list of fixes appears in a series of tables in the Retrieving Cumulative Fix 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 cumulative fix 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 Cumulative Fix 2 are on the product support Web site at http://www.ibm.com/software/webservers/appserv/support.html.
Install the appropriate Cumulative Fix 2 on top of 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 Cumulative Fix 2 before applying Cumulative Fix 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 Cumulative Fix 2 to the base product without applying it to the Enterprise product causes the Enterprise environment to fail.
A Java Runtime Environment must be available, even if the Java installation is not being updated.
Download Cumulative Fix 2 to a read/write directory as described in Steps for installing Cumulative Fix 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 cumulative fix, 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 the code is installed, the Cumulative Fix 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 cumulative fix, 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 cumulative fix, somewhere between 50 MB to 250 MB, varying by product and platform.
The update installer checks for required space before it installs the cumulative fix. However, there is a bug in the space checker when installing Cumulative Fix 2.
When installing Cumulative Fix 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.
Cumulative Fix 2 platform-specific files for the base WebSphere Application Server product:
| Operating system platform | Cumulative Fix 2 ZIP file | Cumulative Fix 2 ID |
|---|---|---|
| AIX | was502_cf2_aix.zip | was502_cf2_aix |
| HP-UX | was502_cf2_hpux.zip | was502_cf2_hpux |
| Linux | was502_cf2_linux.zip | was502_cf2_linux |
| Linux for Power PC | was502_cf2_linuxppc32.zip | was502_cf2_linuxppc32 |
| Linux for S/390 | was502_cf2_linux390.zip | was502_cf2_linux390 |
| Solaris | was502_cf2_solaris.zip | was502_cf2_solaris |
| Windows NT and Windows 2000 | was502_cf2_win.zip | was502_cf2_win |
Cumulative Fix 2 platform-specific files for the Network Deployment product:
| Operating system platform | Cumulative Fix 2 ZIP file | Cumulative Fix 2 ID |
|---|---|---|
| AIX | was502_nd_cf2_aix.zip | was502_nd_cf2_aix |
| HP-UX | was502_nd_cf2_hpux.zip | was502_nd_cf2_hpux |
| Linux | was502_nd_cf2_linux.zip | was502_nd_cf2_linux |
| Linux for Power PC | was502_nd_cf2_linuxppc32.zip | was502_nd_cf2_linuxppc32 |
| Linux for S/390 | was502_nd_cf2_linux390.zip | was502_nd_cf2_linux390 |
| Solaris | was502_nd_cf2_solaris.zip | was502_nd_cf2_solaris |
| Windows NT and Windows 2000 | was502_nd_cf2_win.zip | was502_nd_cf2_win |
Cumulative Fix 2 platform-specific files for the Enterprise product:
| Operating system platform | Cumulative Fix 2 ZIP file | Cumulative Fix 2 ID |
|---|---|---|
| AIX | was502_pme_cf2_aix.zip | was502_pme_cf2_aix (to extend the base product) |
| was502_pme_nd_cf2_aix (to extend the Network Deployment product) | ||
| HP-UX | was502_pme_cf2_hpux.zip | was502_pme_cf2_hpux (to extend the base product) |
| was502_pme_nd_cf2_hpux (to extend the Network Deployment product) | ||
| Linux | was502_pme_cf2_linux.zip | was502_pme_cf2_linux (base) |
| was502_pme_nd_cf2_linux (Network Deployment) | ||
| Linux for Power PC | was502_pme_cf2_linuxppc32.zip | was502_pme_cf2_linuxppc32 (base) |
| was502_pme_nd_cf2_linuxppc32 (Network Deployment) | ||
| Linux for S/390 | was502_pme_cf2_linux390.zip | was502_pme_cf2_linux390 (base) |
| was502_pme_nd_cf2_linux390 (Network Deployment) | ||
| Solaris | was502_pme_cf2_solaris.zip | was502_pme_cf2_solaris (base) |
| was502_pme_nd_cf2_solaris (Network Deployment) | ||
| Windows NT and Windows 2000 | was502_pme_cf2_win.zip | was502_pme_cf2_win (base) |
| was502_pme_nd_cf2_win (Network Deployment) |
# cd /usr/WebSphere/DeploymentManager/update (Linux or UNIX) > cd \WebSphere\update (Windows platforms)
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 problem is caused by 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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.