V5.1.0 Cumulative Fix 1 for SDKs

 

Compilation date: 2004/05/06

© 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 Java 2 SDK 1.4.2 and IBM SDK 1.4.1 Java Technology Edition SR1B. 

Applying this cumulative fix on Microsoft® Windows®, Linux® or AIX® platforms will upgrade your SDK to 1.4.1 Java Technology Edition SR1B (1411-20031011b).
Applying this cumulative fix on the HP-UX platform will upgrade your Java 2 SDK to Java 2 SDK 1.4.1 Service Release 5.
Applying this cumulative fix on the Solaris platform will upgrade your Java 2 SDK to Java 2 SDK 1.4.2 Service Release 3.

 

Table of Contents

About V5.1.0 Cumulative Fix 1 for SDKs

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

 

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 V5.1.0 Cumulative Fix 1 for SDKs 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 V5.1.0 Cumulative Fix 1 for SDKs are on the product support Web site at http://www.ibm.com/software/webservers/appserv/support.html.

 

Prerequisites

Install the appropriate V5.1.0 Cumulative Fix 1 for SDK 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.  This service pack can also be installed on top of any V5.1.0 Cumulative Fix 1 for SDKs that might have already been installed on top of these products.

Before installing this SDK on the Sun or HP-UX platforms, it is required that the latest recommended patches be applied to the system. These can be downloaded from the following sites:

Sun OS recommended Patches
HP-UX OS recommended Patches
 

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

Download V5.1.0 Cumulative Fix 1 for SDKs to a read/write directory as described in Installing V5.1.0 Cumulative Fix 1 for SDKs. 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

Space requirements vary depending on what you are installing. The size of each download is available on the Support site. For a V5.1.0 Cumulative Fix 1 for SDKs, 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 Linux-based or 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 V5.1.0 Cumulative Fix 1 for SDKs 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 V5.1.0 Cumulative Fix 1 for SDKs, 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 Java 2 SDK Service Pack, somewhere between 50 MB to 250 MB, varying by product and platform.

The update installer checks for required space before it installs the V5.1.0 Cumulative Fix 1 for SDKs. However, a bug exists in the space checker when installing V5.1.0 Cumulative Fix 1 for SDKs.

When installing V5.1.0 Cumulative Fix 1 for SDKs, 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.

 

Retrieving V5.1.0 Cumulative Fix 1 for SDKs

V5.1.0 Cumulative Fix 1 for SDKs platform-specific files for the base WebSphere Application Server product:

 

Operating system platform V5.1.0 Cumulative Fix 1 for SDKs ZIP file V5.1.0 Cumulative Fix 1 for SDKs ID
AIX was510_jdk_aix.zip was510_jdk_aix
HP-UX was510_jdk_hpux.zip was510_jdk_hpux
Linux was510_jdk_linux.zip was510_jdk_linux
Linux for Power PC was510_jdk_linuxppc32.zip was510_jdk_linuxppc32
Linux for S/390 was510_jdk_linux390.zip was510_jdk_linux390
Solaris was510_jdk_solaris.zip was510_jdk_solaris
Windows NT and Windows 2000 was510_jdk_win.zip was510_jdk_win


 

 

 

V5.1.0 Cumulative Fix 1 for SDKs platform-specific files for the Network Deployment product:

 

Operating system platform V5.1.0 Cumulative Fix 1 for SDKs ZIP file V5.1.0 Cumulative Fix 1 for SDKs ID
AIX was510_nd_jdk_aix.zip was510_nd_jdk_aix
HP-UX was510_nd_jdk_hpux.zip was510_nd_jdk_hpux
Linux was510_nd_jdk_linux.zip was510_nd_jdk_linux
Linux for Power PC was510_nd_jdk_linuxppc32.zip was510_nd_jdk_linuxppc32
Linux for S/390 was510_nd_jdk_linux390.zip was510_nd_jdk_linux390
Solaris was510_nd_jdk_solaris.zip was510_nd_jdk_solaris
Windows NT and Windows 2000 was510_nd_jdk_win.zip was510_nd_jdk_win

 


 

 


Steps for installing V5.1.0 Cumulative Fix 1 for SDKs

  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 V5.1.0 Cumulative Fix 1 for SDKs, stop all Java processes that use the IBM Developer Kit that WebSphere Application Server provides to support the V5.1.0 Cumulative Fix 1 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 V5.1.0 Cumulative Fix 1 for SDKs 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.



 

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.


 

Trademarks and service marks

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.

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.