Compilation date: 2004/04/30

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

Abstract: Documentation for Cumulative Fix 4 of Version 5.1.0 of the WebSphere Application Server product family.

Table of Contents

• About Cumulative Fix 4
• Additional information
• Prerequisites
• Space requirements
• Retrieving Cumulative Fix 4
• Steps for installing Cumulative Fix 4
• Known Issues
• Finding the readme_updateinstaller.html file
• Trademarks and service marks

There are several platform-specific cumulative fixes that are each referred to as Cumulative Fix 4 for their respective product and platform. The complete list of fixes appears in a series of tables in the Retrieving Cumulative Fix 4 section, which is organized by product:

• WebSphere Application Server, Version 5, including its features, IBM HTTP Server and the embedded messaging feature, which is based on WebSphere MQ technology
• WebSphere Application Server Network Deployment, Version 5
• WebSphere Application Server Enterprise, Version 5 

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

Back to top

 

Additional information

You can find additional information in the Version 5 information center: 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 4 are on the product support Web site at http://www.ibm.com/software/webservers/appserv/support.html.

Back to top

 

Prerequisites

Install the appropriate Cumulative Fix 4 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.

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

Download Cumulative Fix 4 to a read/write directory as described in Installing Cumulative Fix 4. 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.

 

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

When installing Cumulative Fix 4, 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 4

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

Operating system platform	Cumulative Fix 4 ZIP file	Cumulative Fix 4 ID
AIX	was510_cf4_aix.zip	was510_cf4_aix
HP-UX	was510_cf4_hpux.zip	was510_cf4_hpux
Linux	was510_cf4_linux.zip	was510_cf4_linux
Linux for Power PC	was510_cf4_linuxppc32.zip	was510_cf4_linuxppc32
Linux for S/390	was510_cf4_linux390.zip	was510_cf4_linux390
Solaris	was510_cf4_solaris.zip	was510_cf4_solaris
Windows NT and Windows 2000	was510_cf4_win.zip	was510_cf4_win

 

 

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

Operating system platform	Cumulative Fix 4 ZIP file	Cumulative Fix 4 ID
AIX	was510_nd_cf4_aix.zip	was510_nd_cf4_aix
HP-UX	was510_nd_cf4_hpux.zip	was510_nd_cf4_hpux
Linux	was510_nd_cf4_linux.zip	was510_nd_cf4_linux
Linux for Power PC	was510_nd_cf4_linuxppc32.zip	was510_nd_cf4_linuxppc32
Linux for S/390	was510_nd_cf4_linux390.zip	was510_nd_cf4_linux390
Solaris	was510_nd_cf4_solaris.zip	was510_nd_cf4_solaris
Windows NT and Windows 2000	was510_nd_cf4_win.zip	was510_nd_cf4_win

 

 

Steps for installing Cumulative Fix 4

1. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations (trun_svr_conf_backup) in the online information center 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 Cumulative Fix 4, 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.
4. Obtain each Cumulative Fix 4 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.

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

    # cd /usr/WebSphere/DeploymentManager/update (Linux or UNIX)
    > cd \WebSphere\update (Windows platforms)
   
   
   

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

Back to top

Known Issues

The following problem has been identified with the Web Services Gateway (see APAR PQ85808):
Invoking a Web Service deployed to the Web Services Gateway(with Selective SOAP Parsing disabled) and defined in its WSDL file with style="document" and use="literal" or style="rpc" and use="literal" can produce one of the following errors:

• An incorrect request message is forwarded to the target service by the Web Services Gateway causing an error in the target service. The incorrect request message has a duplicated outer XML Element wrapping the remainder if the message content.
• An Internal Server Error occurs while the Web Services Gateway is processing the target service response (and appears in the logs) as follows: org.xml.sax.SAXException: WSWS3140E: Error: Deserializing parameter 'xxxxxxxxxxxxxxxx': could not find deserializer for type {http://websphere.ibm.com/webservices/}Void

  Solution: This problem is fixed in WebSphere Application Server Network Deployment v5.1.0 Service Pack 4. It's recommended that customers wait for the next service pack, but a test fix can be made available upon request. Please contact your IBM representative for it.
  

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

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.

Other company, product, or service names may be trademarks or service marks of others.

Back to top

---