IBM WebSphere Application Server - Express, Version 5 Fix Pack 1
IBM WebSphere Application Server, Version 5 Fix Pack 1
IBM WebSphere Application Server Network Deployment, Version 5 Fix Pack 1
IBM WebSphere Application Server Enterprise, Version 5 Fix Pack 1

Compilation date: 2003/04/02

© Copyright International Business Machines Corporation 2002, 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 1 of Version 5 of the WebSphere Application Server product family.

Table of Contents


An Important Note for Windows NT

If you are installing Fix Pack 5.0.1 on a Windows NT system, you may encounter an error that causes the Fix Pack installation to fail. The error will occur when installing the component prereq.jsse. You will be notified of the error by a popup message box with the message "Fix Pack installation failed".

The popup error message will refer to an installation log. This installation log will contain the error:

Exception: WUPD0248E: Fix pack update failure: The processing of fix pack was50_fp1_win, component prereq.jsse failed.

If you get this error, click the Finish button in the installation GUI to immediately exit the installation GUI program. Then open a command prompt window, and go to the java subdirectory under the directory where WebSphere Application Server v5.0 is installed, like c:/Program Files/WebSphere/AppServer/java, and run the command:

attrib -r /s

You can then restart the FixPak installation by running the updateWizard.bat file. The Installation GUI program will show the Fix Pack as being partially installed, which is OK. The installation program will continue 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 WebSphere/AppServer/java directory and subdirectories.

 

About Fix Pack 1

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

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

 

Additional information

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

 

Prerequisites

Install the appropriate Fix Pack 1 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.

A Java runtime environment must be available, even if the Java installation is not being updated.

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 Web site. The update installer application also requires some temporary space. Have approximately 250 MB of free space in the /tmp directory on a Linux or UNIX-based platform, or on the disk drive where you are installing on a Windows platform. After unpacking the ZIP file, delete the ZIP file to free space. After it is installed, the Fix Pack 1 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, somewhere between 50 MB to 150 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 25 MB to 165 MB, varying by product and platform.

The update installer checks for required space before it installs the fix pack.

 

Retrieving Fix Pack 1

Fix Pack 1 platform-specific files for the WebSphere Application Server - Express product:

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID
AIX was50_express_fp1_aix.zip was50_express_fp1_aix
Linux was50_express_fp1_linux.zip was50_express_fp1_linux
Linux/390 was50_express_fp1_linux390.zip was50_express_fp1_linux390
Solaris was50_express_fp1_solaris.zip was50_express_fp1_solaris
Windows NT and Windows 2000 was50_express_fp1_win.zip was50_express_fp1_win

 


 

 

Fix Pack 1 platform-specific files for the base WebSphere Application Server product:

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID
AIX was50_fp1_aix.zip was50_fp1_aix
Linux was50_fp1_linux.zip was50_fp1_linux
Linux/390 was50_fp1_linux390.zip was50_fp1_linux390
Solaris was50_fp1_solaris.zip was50_fp1_solaris
Windows NT and Windows 2000 was50_fp1_win.zip was50_fp1_win

 

 

Fix Pack 1 platform-specific files for the Network Deployment product:

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID
AIX was50_nd_fp1_aix.zip was50_nd_fp1_aix
Linux was50_nd_fp1_linux.zip was50_nd_fp1_linux
Linux/390 was50_nd_fp1_linux390.zip was50_nd_fp1_linux390
Solaris was50_nd_fp1_solaris.zip was50_nd_fp1_solaris
Windows NT and Windows 2000 was50_nd_fp1_win.zip was50_nd_fp1_win

 


 

Fix Pack 1 platform-specific files for the Enterprise product:

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID
AIX was50_pme_fp1_aix.zip was50_pme_fp1_aix (to extend the base product)
was50_pme_nd_fp1_aix (to extend the Network Deployment product)
Linux was50_pme_fp1_linux.zip was50_pme_fp1_linux (base)
was50_pme_nd_fp1_linux (Network Deployment)
Linux/390 was50_pme_fp1_linux390.zip was50_pme_fp1_linux390 (base)
was50_pme_nd_fp1_linux390 (Network Deployment)
Solaris was50_pme_fp1_solaris.zip was50_pme_fp1_solaris (base)
was50_pme_nd_fp1_solaris (Network Deployment)
Windows NT and Windows 2000 was50_pme_fp1_win.zip was50_pme_fp1_win (base)
was50_pme_nd_fp1_win (Network Deployment)

 

Fix Pack 1 platform-specific files for the WebSphere Application Server client:

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID
AIX was50_client_fp1_aix.zip was50_client_fp1_aix
Linux was50_client_fp1_linux.zip was50_client_fp1_linux
Linux/390 was50_client_fp1_linux390.zip was50_client_fp1_linux390
Solaris was50_client_fp1_solaris.zip was50_client_fp1_solaris
Windows NT and Windows 2000 was50_client_fp1_win.zip was50_client_fp1_win



Steps for installing Fix Pack 1

  1. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations (trun_svr_conf_backup) in the online InfoCenter located at http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=ApplicationServer.

  2. After backing up the configuration and before installing Fix Pack 1, 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, if necessary. If you do install a fix pack while a WebSphere Application Server-related Java process is running, IBM does not guarantee that the product can continue to run successfully, or without error.

  3. Obtain each Fix Pack 1 file that you need from the product support Web site located at http://www.ibm.com/software/webservers/appserv/support.html. Download the files into the install_root/update directory, which you can create.

  4. At a system command prompt, change the directory to where you downloaded the file, for example: 
     # cd /usr/WebSphere/DeploymentManager/update
  5. 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.

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

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



Finding the readme_updateinstaller.html and readme_updateinstaller.pdf files

Open the readme_updateinstaller.html file 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, or install a fix pack in an environment that does not provide a graphical user interface.

The readme_updateinstaller.html 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.html file describes how to verify that you have successfully installed the fix pack.

The readme_updateinstaller.html 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.