Readme for IBM WebSphere Application Server V5.0.2.17
 Product readme
 
Abstract
Readme documentation for IBM® WebSphere® Application Server 5.0.2 Cumulative Fix 17 (5.0.2.17) for Base, Application Client, Network Deployment and Express Editions. Includes installation instructions, prerequisites, highlights of changes, and any known issues.
 
 
Content
IBM WebSphere Application Server, Version 5.0.2 Cumulative Fix 17
IBM WebSphere Application Server Network Deployment, Version 5.0.2 Cumulative Fix 17
IBM WebSphere Application Server Express, Version 5.0.2 Cumulative Fix 17
IBM WebSphere Application Client, Version 5.0.2 Cumulative Fix 17

Contents
Compilation date: 2006/05/15

© Copyright International Business Machines Corporation 2004. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.



About Cumulative Fix 17
There are several platform-specific cumulative fixes that are each referred to as Cumulative Fix 17 for their respective product and platform. The complete list of cumulative fixes appears in a series of tables in the Retrieving Cumulative Fix 17 section, which is organized by product:
  • WebSphere Application Server, Version 5.0.2.17, including its features and the embedded messaging feature, which is based on WebSphere MQ technology.
  • WebSphere Application Server Network Deployment, Version 5.0.2.17
  • WebSphere Application Server Express Edition, Version 5.0.2.17
  • WebSphere Application Client, Version 5.0.2.17 (applicable to certain platforms)

This document also describes prerequisites, space requirements, download instructions, locations of detailed installation instructions, and more information about the update installer application.

Mandatory JavaSDK Update
Users with WebSphere Application Server 5.0.2.12 and above are required to upgrade their Java SDK to Java SDK 1.3.1 SR8 or higher. Refer to Users with V5.0.2.12, and above on V5.0.2, need to upgrade their Java SDK to Java SDK 1.3.1 SR8 or higher for more details.

Back to top



Additional information
You can find additional information in the WebSphere Application Server Version 5.0 Information Center.

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 related documentation is available from the WebSphere Application Server V5.0.2 Cumulative Fix 17 download page.

Back to top



Prerequisites
Install the appropriate Cumulative Fix 17 on top of WebSphere Application Server Base, Application Client, Network Deployment or Express Edition.

A Java Runtime Environment must be available, even if the Java installation is not being updated.

Download Cumulative Fix 17 to a read/write directory as described in Installing Cumulative Fix 17. Installing from a read-only drive is not supported.

All required hardware and software prerequisites are described in the WebSphere Application Server detailed system requirements.

Back to top



Space requirements
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 Microsoft® 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 17 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, a bug exists in the space checker when installing Cumulative Fix 17.

When installing Cumulative Fix 17, the update installer checks for required disk space in the /tmp directory and in the backup directory. If the /tmp directory or the backup directory have insufficient space, the update installer issues a warning message.

Back to top



Retrieving Cumulative Fix 17
Cumulative Fix 17 platform-specific files for the base WebSphere Application Server product:

Operating system platform
Cumulative Fix 17 ZIP file
Cumulative Fix 17 ID
AIX®
was502_cf17_aix.zip
was502_cf17_aix
HP-UX
was502_cf17_hpux.zip
was502_cf17_hpux
Linux®
was502_cf17_linux.zip
was502_cf17_linux
Linux for Power PC®
was502_cf17_linuxppc32.zip
was502_cf17_linuxppc32
Linux for S/390®
was502_cf17_linux390.zip
was502_cf17_linux390
Solaris
was502_cf17_solaris.zip
was50_cf17_solaris
Windows NT® and Windows 2000
was502_cf17_win.zip
was502_cf17_win

Cumulative Fix 17 platform-specific files for the WebSphere Application Server Express product:

Operating system platform
Cumulative Fix 17 ZIP file
Cumulative Fix 17 ID
AIX
was502_express_cf17_aix.zip
was502_express_cf17_aix
HP-UX
was502_express_cf17_hpux.zip
was502_express_cf17_hpux
Linux
was502_express_cf17_linux.zip
was502_express_cf17_linux
Solaris
was502_express_cf17_solaris.zip
was50_express_cf17_solaris
Windows NT and Windows 2000
was502_express_cf17_win.zip
was502_express_cf17_win

Cumulative Fix 17 platform-specific files for the Network Deployment product:

Operating system platform
Cumulative Fix 17 ZIP file
Cumulative Fix 17 ID
AIX
was502_nd_cf17_aix.zip
was502_nd_cf17_aix
HP-UX
was502_nd_cf17_hpux.zip
was502_nd_cf17_hpux
Linux
was502_nd_cf17_linux.zip
was502_nd_cf17_linux
Linux for Power PC
was502_nd_cf17_linuxppc32.zip
was502_nd_cf17_linuxppc32
Linux for S/390
was502_nd_cf17_linux390.zip
was502_nd_cf17_linux390
Solaris
was502_nd_cf17_solaris.zip
was502_nd_cf17_solaris
Windows NT and Windows 2000
was502_nd_cf17_win.zip
was502_nd_cf17_win

Cumulative Fix 17 platform-specific files for the Application Client product:

Operating system platform
Cumulative Fix 17 ZIP file
Cumulative Fix 17 ID
AIX
was502_client_cf17_aix.zip
was502_client_cf17_aix
Linux
was502_client_cf17_linux.zip
was502_client_cf17_linux
Solaris
was502_client_cf17_solaris.zip
was502_client_cf17_solaris
Windows NT and Windows 2000
was502_client_cf17_win.zip
was502_client_cf17_win

Back to top



Steps for installing Cumulative Fix 17
  1. Back up any Interim Fixes you might have installed as you will need to re-install them after the V.5.0.2. Cumulative Fix 17 is installed on your machine if these fixes are not included in the V.5.0.2 Cumulative Fix 17.

  2. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations in the online information center.

  3. Verify required disk space.

  4. After backing up the configuration and before installing Cumulative Fix 17, 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. The product might not continue to run successfully, or without error if you do install a fix pack while a WebSphere Application Server-related Java process is running.

  5. Obtain the fixes you need from the WebSphere Application Server V5.0.2 Cumulative Fix 17 download page. Download the files into the install_root/update directory, which you can create.

  6. At a system command prompt, change the directory to where you downloaded the file, for example:

    For Linux or UNIX®:

    # cd /usr/WebSphere/DeploymentManager/update

    For Windows:

    > cd \WebSphere\update

  7. 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.

  8. (Optional) Delete the ZIP file if you need more space.

  9. 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 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.

  10. Re-install any Temporary Fixes you might have uninstalled at step 1.


Back to top



Highlights of changes
  • PQ90177: Save Conflict
    When a save conflict occurs in the admin console, the default option is to overwrite the conflicting files. This is not a well chosen default option, because overwriting file changes could lead to repository corruption.

    The default option upon a save conflict has been changed from overwrite to discard. This will help preserving the integrity of the repository. The overwrite option is meant for advanced users. This will also line up administrative console behavior with 'wsadmin', where the default is not to overwrite conflicting files.

  • PQ93396: Disk Cache
    If your server is configured to use disk cache function, you must delete previous disk cache files after installing the Service Pack. For more details on this, see Troubleshooting tips for the dynamic cache service in the information center.
  • Java virtual machine custom properties for tuning the disk cache
    Use this page to set Java virtual machine (JVM) custom properties to maintain cache entries that are saved to disk.

    Steps for this task
    To set any of these JVM custom properties, perform the following steps:
    1. In the administrative console, click Servers > Application servers > server_name > Process definition > Java virtual machine > Custom properties > New
    2. Type the name of the custom property (for example, com.ibm.ws.cache.CacheConfig.htodCleanupFrequency) in the Name field.
    3. Type a valid value for the property in the Value field.
    4. Save the property and restart WebSphere Application Server.

  • com.ibm.ws.cache.CacheConfig.htodCleanupFrequency
    Use this property to change the amount of time between disk cache cleanup.

    By default, the disk cache cleanup is scheduled to run at midnight to remove expired cache entries and cache entries that have not been accessed in the past 24 hours. However, if you have thousands of cache entries that might expire within one or two hours, the files that are in the disk cache can grow large and become unmanageable. Use the com.ibm.ws.cache.CacheConfig.htodCleanupFrequency custom property to change the time interval between disk cache cleanup.

    Units Minutes
    For example, a value of 60 means 60 minutes between each disk cache cleanup
    Default 0
    The disk cache cleanup occurs at midnight every 24 hours


Back to top



Finding the readme_updateinstaller.txt, readme_updateinstaller.html and readme_updateinstaller.pdf files
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.

Back to top



More information
For more information, refer to the Recommended fixes and IBM cumulative fix strategy documents.



Trademarks and service marks
The following terms are trademarks of IBM Corporation in the United States, other countries, or both:
  • Everyplace
  • iSeries
  • IBM
  • Redbooks
  • ViaVoice
  • WebSphere
  • zSeries

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.

LINUX is a trademark of Linus Torvalds in the U.S., other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.

Back to top
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express General AIX, HP-UX, Linux, Solaris, Windows 5.0.2.9, 5.0.2.8, 5.0.2.7, 5.0.2.6, 5.0.2.5, 5.0.2.4, 5.0.2.3, 5.0.2.2, 5.0.2.17, 5.0.2.16, 5.0.2.15, 5.0.2.14, 5.0.2.13, 5.0.2.12, 5.0.2.11, 5.0.2.10, 5.0.2.1, 5.0.2, 5.0 All Editions
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.0.2.17
Software edition:
Reference #: 7007584
IBM Group: Software Group
Modified date: Jul 13, 2006