Install interim fixes, cumulative fixes, and fix packs: WAS ND

Installing interim fixes, cumulative fixes, and fix packs

Overview

Fix packs are also known as fixpacks, FixPaks and program temporary fixes, or PTFs.
Fix packs can be downloaded from...

IBM Support site for IBM HTTP Server
The readme file that is bundled with the interim fix describes how to install the interim fix. You do not use the update installer program for the WAS (also known as the updateInstaller program or the Update Installation wizard) to install interim fixes for the IBM HTTP Server feature.
WebSphere MQ Service download site
Download the readme file for a description of how to install the interim fix. You do not use the update installer for the WAS to install interim fixes for the embedded messaging feature.
IBM Support site for WebSphere Application Server
WAS cumulative fixes and fix packs include service for the IBM HTTP Server powered by Apache 1.3 feature and for the embedded messaging feature. Interim fixes for a WAS product do not include service for the IBM HTTP Server feature or the embedded messaging feature.
The readme file that is bundled with the WAS interim fix, the cumulative fix, or the fix pack describes how to use the update installer program for WAS products to install the interim fix, the cumulative fix, or the fix pack.

There are two interfaces to the update installer application...

The wizard interface is the updateWizard command.
The silent, command-line interface is the updateSilent command.

Both the updateSilent command and the updateWizard command call the update installer program to install and uninstall interim fixes, cumulative fixes, and fix packs for WAS products.

Installation roots

The variable install_root represents the root directory for WAS. By default, this varies per product and operating system:
Base WebSphere Application Server product:

Platform Path
AIX /usr/WebSphere/AppServer
Linux /opt/WebSphere/AppServer
HP-UX and Solaris /opt/WebSphere/AppServer
Windows drive\Program Files\WebSphere\AppServer

Network Deployment product:

Platform Path
AIX /usr/WebSphere/DeploymentManager
Linux /opt/WebSphere/DeploymentManager
HP-UX and Solaris /opt/WebSphere/DeploymentManager
Windows drive\Program Files\WebSphere\DeploymentManager

WebSphere Business Integration Server Foundation

Platform Path
AIX /usr/WebSphere/AppServer
Linux /opt/WebSphere/AppServer
HP-UX and Solaris /opt/WebSphere/AppServer
Windows drive\Program Files\WebSphere\AppServer

WebSphere Business Integration Server Foundation for Network Deployment

Platform Path
AIX /usr/WebSphere/DeploymentManager
Linux /opt/WebSphere/DeploymentManager
HP-UX and Solaris /opt/WebSphere/DeploymentManager
Windows drive\Program Files\WebSphere\DeploymentManager

Space requirements

Space requirements vary depending on what you are installing. The size of each download is available on the Support site. After unpacking the ZIP file you download, delete the ZIP file to free space.
For a fix pack, 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, which is typically /opt for a Linux platform and for all UNIX platforms except for AIX, which is typically /usr, or approximately 800 MB of free space on the disk drive where you are installing on a Windows platform.

Interim fixes require much less space to install.

Additional space is required for backup files in the install_root/properties/version/backup directory. When installing a fix pack the space required is typically about the same as the size of the fix pack, that is, between 50 MB and 300 MB, depending on the particular fix pack.

The update installer program checks for required space before it installs an interim fix, a cumulative fix, or a fix pack. Fixes require much less space to install than do cumulative fixes or fix packs. The space requirement varies per cumulative fix. For example, Cumulative Fix 3 for V5.1 (5.1.0.3) requires 248 MB in the /tmp directory and another 248 MB in the partition that contains the installation root directory. That is a total of 496 MB.

The system temporary directory is determined by the JVM and by the operating system. It is possible for the system temporary directory and the installation root directory to be on the same partition.

Older versions of the update installer, including the version current at the time that Cumulative Fix 3 was released, check for the total space requirement but report each requirement separately. Unfortunately, the messages are misleading. If you have 300 MB of free space on a partition but both the /tmp directory and the installation root are on the partition, you do not have enough space for both.

In this example, you have 300 MB when you need 496 MB in the partition. Each space checking message states that you do not have enough space and that 248 MB is required. 300 MB is more than 248 MB so the message is misleading. The message should state that you need 496 MB in the partition, 248 MB of which is for the /tmp directory. The second message should state that you need 496 MB in the partition, 248 MB of which is for the installation root requirement.

Command name

updateSilent and updateWizard command-line interfaces to the installer.jar file.

Prerequisite environment setting

The JAVA_HOME environment setting must point to the IBM SDK for WAS products. Source the appropriate command:

Source the command on UNIX platforms.
. install_root/bin/setupCmdLine.sh

Source the command on Linux platforms.
source install_root/bin/setupCmdLine.sh

Windows platforms only)
install_root\bin\setupCmdLine.bat

Download from

Download the updateInstaller.zip file from the WebSphere Application Server Support page. The files that comprise the ZIP file are also part of each fix pack ZIP file package. Fix packs are named according to the Application Server product, the fix pack sequence, and the operating system platform.
Interim fixes are named according to the tracking number used for the defect that the interim fix solves. For example, PQ81989 is an interim fix. See 1.3.1 Java SDK, Java Tech Edition for WebSphere Application Server V5 for an example of a download page for an interim fix.

Cumulative fixes use a naming scheme that identifies the product, the cumulative fix number, and the operating system. The following example shows names for Cumulative Fix 3 for V5.1:
Cumulative Fix 3 names for WebSphere Application Server, V5.1

Operating system platform Cumulative Fix 3 ZIP file Cumulative Fix 3 ID Default repository in installation root directory
AIX was510_cf3_aix.zip was510_cf3_aix ../update/ fixpacks
Linux was510_cf3_linux.zip was510_cf3_linux
Linux for S/390 was510_cf3_linux390.zip was510_cf3_linux390
Solaris was510_cf3_solaris.zip was510_cf3_solaris
HP-UX was510_cf3_hpux.zip was510_cf3_hpux
Windows was510_cf3_win.zip was510_cf3_win ..\update\ fixpacks

Cumulative Fix 3 names for WebSphere Application Server Network Deployment, V5.1

Operating system platform Cumulative Fix 3 ZIP file Cumulative Fix 3 ID Default repository in installation root directory
AIX was510_nd_cf3_aix.zip was510_nd_cf3_fp2_aix ../update/fixpacks
Linux was510_nd_cf3_linux.zip was510_nd_cf3_linux
Linux for S/390 was510_nd_cf3_linux390.zip was510_nd_cf3_linux390
Solaris was510_nd_cf3_solaris.zip was510_nd_cf3_solaris
HP-UX was510_nd_cf3_hpux.zip was510_nd_cf3_hpux
Windows platforms was510_nd_cf3_win.zip was510_nd_cf3_win ..\update\ fixpacks

See WebSphere Application Server 5.1 Cumulative Fix 3 for an example of a download page for a cumulative fix.

Fix packs use a naming scheme that identifies the product, the fix pack sequence number, and the operating system.

The names of the cumulative fixes that the WebSphere Business Integration Server Foundation product installs for the base product and for the Network Deployment products are shown in the following table:
Cumulative Fix 2 names for WebSphere Application Server, V5.1

Operating system platform Cumulative Fix 2 ZIP file Cumulative Fix 2 ID Default repository in installation root directory
AIX was510_cf2_aix.zip was510_cf2_aix ../update/ fixpacks
Linux was510_cf2_linux.zip was510_cf2_linux
Linux for S/390 was510_cf2_linux390.zip was510_cf2_linux390
Solaris was510_cf2_solaris.zip was510_cf2_solaris
HP-UX was510_cf2_hpux.zip was510_cf2_hpux
Windows was510_cf2_win.zip was510_cf2_win ..\update\ fixpacks

Cumulative Fix 2 names for WebSphere Application Server Network Deployment, V5.1

Operating system platform Cumulative Fix 2 ZIP file Cumulative Fix 2 ID Default repository in installation root directory
AIX was51_nd_cf2_aix.zip was51_nd_cf2_fp2_aix ../update/fixpacks
Linux was51_nd_cf2_linux.zip was51_nd_cf2_linux
Linux for S/390 was51_nd_cf2_linux390.zip was51_nd_cf2_linux390
Solaris was51_nd_cf2_solaris.zip was51_nd_cf2_solaris
HP-UX was51_nd_cf2_hpux.zip was51_nd_cf2_hpux
Windows platforms was51_nd_cf2_win.zip was51_nd_cf2_win ..\update\ fixpacks

The latest available fix pack is Fix Pack 1 for the WebSphere Application Server V5.1.0 family of products:
Fix Pack 1 names for WebSphere Application Server, V5.1.0

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID Default repository in installation root directory
AIX was51_fp1_aix.zip was51_fp1_aix ../update/ fixpacks
Linux was51_fp1_linux.zip was51_fp1_linux
Linux for S/390 was51_fp1_linux390.zip was51_fp1_linux390
Solaris was51_fp1_solaris.zip was51_fp1_solaris
HP-UX was51_fp1_hpux.zip was51_fp1_hpux
Windows was51_fp1_win.zip was51_fp1_win ..\update\ fixpacks

Fix Pack 1 names for WebSphere Application Server Network Deployment, V5.1.0

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID Default repository in installation root directory
AIX was51_nd_fp1_aix.zip was51_nd_fp1_aix ../update/fixpacks
Linux was51_nd_fp1_linux.zip was51_nd_fp1_linux
Linux for S/390 was51_nd_fp1_linux390.zip was51_nd_fp1_linux390
Solaris was51_nd_fp1_solaris.zip was51_nd_fp1_solaris
HP-UX was51_nd_fp1_hpux.zip was51_nd_fp1_hpux
Windows platforms was51_nd_fp1_win.zip was51_nd_fp1_win ..\update\ fixpacks

Fix Pack 1 names for WebSphere Business Integration Server Foundation, V5.1.0

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID Default repository in installation root directory
AIX wbisf51_fp1_aix.zip wbisf51_fp1_aix (to extend the base product) ../update/ fixpacks
wbisf51_nd_fp1_aix (to extend the Network Deployment product)
Linux wbisf51_fp1_linux.zip wbisf51_fp1_linux (base)
wbisf51_nd_fp1_linux (Network Deployment)
Linux for S/390 wbisf51_fp1_linux390.zip wbisf51_fp1_linux390 (base)
wbisf51_nd_fp1_linux390 (Network Deployment)
Solaris wbisf51_fp1_solaris.zip wbisf51_fp1_solaris (base)
wbisf51_nd_fp1_solaris (Network Deployment)
HP-UX wbisf51_fp1_hpux.zip wbisf51_fp1_hpux
wbisf51_nd_fp1_hpux (Network Deployment)
Windows platforms wbisf51_fp1_win.zip wbisf51_fp1_win (base) ..\update\ fixpacks
wbisf51_nd_fp1_win (Network Deployment)

Fix Pack 1 names for WebSphere Application Server Express, Version 5.1.0

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID Default repository in installation root directory
AIX was51_express_fp1_aix.zip was51_express_fp1_aix ../update/ fixpacks
Linux was51_express_fp1_linux.zip was51_express_fp1_linux
Linux for S/390 was51_express_fp1_linux390.zip was51_express_fp1_linux390
Solaris was51_express_fp1_solaris.zip was51_express_fp1_solaris
HP-UX was51_express_fp1_hpux.zip was51_express_fp1_hpux
Windows platforms was51_express_fp1_win.zip was51_express_fp1_win ..\update\ fixpacks

Fix Pack 1 names for WebSphere Application Server, V5.1.0 Application Clients

Operating system platform Fix Pack 1 ZIP file Fix Pack 1 ID Default repository in installation root directory
AIX was51_client_fp1_aix.zip was51_client_fp1_aix ../update/fixpacks
Linux was51_client_fp1_linux.zip was51_client_fp1_linux
Linux for S/390 was51_client_fp1_linux390.zip was51_client_fp1_linux390
Solaris was51_client_fp1_solaris.zip was51_client_fp1_solaris
HP-UX was51_client_fp1_hpux.zip was51_client_fp1_hpux
Windows platforms was51_client_fp1_win.zip was51_client_fp1_win ..\update\fixpacks

Download to

Choose a directory for unpacking the update installer program or fix pack zip file that does not have a space in its name. For example, do not use the default installation root on a Windows platform because it is within the Program Files directory. On a Linux or UNIX-based platform, you can use the installation root directory.
Create the install_root/update directory or the no_spaces_path\update directory on Windows platforms. Unpacking a fix pack creates the ../update/fixpacks directory. Create another directory, ../update/fixes, for a repository of fixes you download. If you create the default subdirectories, you can accept default interim fix and fix pack file locations when using the updateWizard interface. Otherwise, browse to locate the fixes or fix packs you are installing or uninstalling.

Location of extfile.jar

WebSphere Application Server product install_root/update/lib (or no_spaces_path\update\lib for Windows platforms)

Location of installer.jar, updateSilent.bat, and updateWizard

WebSphere Application Server product install_root/update (or no_spaces_path\update for Windows platforms)

Location of readme files

WebSphere Application Server product install_root/update/docs (or no_spaces_path\update\docs for Windows platforms)

Location of interim fix Java archive (JAR) files

install_root/update/fixes (or no_spaces_path\update\fixes)

Location of cumulative fix and fix pack JAR files

install_root/update/fixpacks (or no_spaces_path\update\fixpacks)
This directory is automatically created by unpacking the fix pack in the ../update directory.

Files in updateInstaller.zip

Always use the updateSilent (or updateWizard) command file from the updateInstaller.zip or fix pack you download, to use the most recent version. A newer version can manage previously downloaded fixes and fix packs. Files in the updateInstaller.zip package (or the fix pack ZIP package) include:

extfile.jar

installer.jar

readme_updateinstaller.txt

readme_updateinstaller.html

readme_updateinstaller.pdf

updateSilent (or updateSilent.bat)

updateWizard

In addition to the listed files, the cumulative fix pack zip file or the fix pack zip file also has a JAR file, such as the was510_nd_cf3_win.jar file. Each JAR file includes a cumulative fix or a fix pack.

Location of log and backup files

The update installer program records processing results in log files in the install_root/logs/update directory. Backup files created during the installation of fixes and fix packs are in the install_root/properties/version/backup directory. The files are required to uninstall an interim fix or fix pack.

Syntax and panel examples

Using the updateWizard interface to work with interim fixes

See updateWizard examples for interim fixes for more information.

Using the updateWizard interface to work with cumulative fixes and fix packs

See updateWizard examples for cumulative fixes and fix packs for more information.

Using the updateSilent interface to work with interim fixes

See updateSilent examples for interim fixes for more information.

Using the updateSilent interface to work with cumulative fixes and fix packs

See updateSilent examples for cumulative fixes and fix packs for more information.

Overview of the installation procedure

To install an interim fix, create an update/fixes directory on your disk drive, download the interim fix and the update installer from the Support Web site, and use the update installer to install the interim fix.
To install a cumulative fix or fix pack, create the update directory on your disk drive if it does not already exist, download and unzip the cumulative fix or the fix pack from the Support Web site, and use the update installer to install the cumulative fix or fix pack. The ZIP file for the cumulative fix or the fix pack includes the following files:

The update installer application

The two interface programs (updateSilent and updateWizard)

A readme file for the cumulative fix or fix pack

A readme file for the update installer

The cumulative fix or fix pack file

Special rules for applying fixes within a cell

One requirement governs applying an interim fix or fix pack to a cell, to ensure the continued, smooth interaction of the various WebSphere Application Server nodes:
Requirement 1:
The Network Deployment product must be at the highest fix level within the cell.

For example, you cannot use the addNode command to add a V5.1 base WebSphere Application Server node to a V5.0.2 deployment manager cell.

There is no limitation on the fix level of a base Application Server V5 node within its cell, if the fix level of the base node is the same as or lower than that of the deployment manager. There is also no limit on the number of different V5.x fix levels that can coexist or interoperate within a cell, so long as the fix level for each base node is the same as or lower than that of the deployment manager. V5.0.x base nodes can comprise V5.1 deployment manager cells.

Viewing the fix level of the node

You can use the versionInfo command in the install_root/bin directory to display the exact fix and version level of the product. However, do not use the versionInfo command while installing an interim fix or fix pack.
You can also use the silent update installer application to:

View interim fix information. See Viewing information about interim fixes.

View cumulative fix or fix pack information. See Viewing information about cumulative fixes and fix packs.

Updating cluster members

Platform-specific tips for installing and migrating All platforms Updating all cluster members to the same fix level

Overview

Do not launch multiple copies of the update installer program at one time
The update installer program cannot be launched concurrently with itself. Performing more than one update at the same time can lead to a failed or faulty installation.

See Uninstalling interim fixes, cumulative fixes, and fix packs for a description of how to remove an interim fix or fix pack from an entire cell, or from any part of the cell.

Installing a fix pack or cumulative fix uninstalls all interim fixes that were installed with the update installer. Interim fixes for the IBM HTTP Server feature and the embedded messaging feature cannot be removed. Some of the interim fixes that are uninstalled might have been released after the release of the cumulative fix or the fix pack. Reinstall such interim fixes to bring your system back to the previous interim fix level.

This procedure describes a scenario for updating an entire cell to the same fix pack level. According to the requirements, apply a fix pack to the deployment manager node first. You can then apply the fix pack to zero, one, or more of the base nodes. If you update a base node in a cluster, install the interim fix, cumulative fix pack, or fix pack to each node in the cluster.

Recovering from a failed installation of a fix pack, cumulative fix, or interim fix

Uninstall the fix pack, the cumulative fix, or the interim fix and reinstall it to recover from a failed installation. The installation can fail if you run out of disk space or if you have a process running and the update installer cannot update the locked files.

Steps for this task

Use the Windows Services panel to stop all services for WebSphere Application Server processes.
This includes services for the deployment manager (dmgr) server, Application Servers (such as server1), and WebSphere MQ queue managers.
Stop all Java processes that use the IBM Software Developer Kit (SDK) that WebSphere Application Server provides.
Before installing or uninstalling interim fixes, cumulative fixes, and fix packs on a machine, stop all Java processes on the machine that use the IBM SDK, Java Technology Edition that WebSphere Application Server provides.
WebSphere Application Server processes include:

Application Server processes

All servers, such as the IBMHttpServer process, that belong to serviceable features. Features with servers include the IBM HTTP Server and the embedded messaging feature.

The nodeagent process on a base node when the node is federated into a deployment manager cell

The dmgr process for the deployment manager server
The jmsserver on a base node when the node is part of a cell and the embedded messaging server and client feature is installed

Stop all Java processes, if necessary, with the killall -9 java command or by using the task manager on a Windows platform. If you do install or uninstall an interim fix, a cumulative fix, or a fix pack while a WebSphere Application Server-related Java process runs, IBM does not guarantee that the product can continue to run successfully, or without error.

Stop all WebSphere MQ processes on a Windows platform.

Stop the WebSphere MQ queue manager process.
endmqm queue_manager_ID

Stop all WebSphere MQ network activity:
net stop "IBM MQSeries"

Remove the WebSphere MQ tray icon if it is present on a Windows system.
On a Windows platform, remove the WebSphere MQ tray icon if it is present. The WebSphere MQ tray icon in the lower right corner indicates that a WebSphere MQ process (amqmtbrn.exe) is running. Right click the tray icon and click Hide to remove it.

Reboot to free locked GSkit-related files.
If the fix that you are installing contains service for the GSkit component, it is possible that the operating system might have locked the file. You can manually stop any Windows services as described in the first step and reboot to free all files.

Stop all WebSphere MQ processes on a Linux or a UNIX platform.

Show the state of any queue managers.
dspmq

For each running queue manager run...
endmqm -i

Check for any IPCs.
$ ipcs -a

Delete the IPCs.
ipcrm -[qms] [ID]

Search for mqm processes.
ps -eaf | grep mqm

or
ps -eaf | grep ^MQ* to

Stop any MQ processes that are running.
kill -9 amq_pid_1 amq_pid_2 ... amq_pid_n

Verify that the required free space is available before beginning the installation. The space required for unpacking the ZIP file is about the same as the size of the fix pack. After unpacking the ZIP file, you can delete the ZIP file if necessary. After it is installed, the fix pack code generally increases the installation and run-time footprints by only a small amount.

Install the interim fix, the cumulative fix, or the fix pack on a deployment manager node

Install the interim fix, the cumulative fix, or the fix pack on a base node

See also

For tutorials on WAS install topics, see:

Installation best practices tutorials
Cumulative Fix Strategy for WAS V5.0 and V5.1

Return to parent topic

Installing WebSphere Application Server products

updateSilent command
updateWizard command
Product version and history information

Platform	Path
AIX	/usr/WebSphere/AppServer
Linux	/opt/WebSphere/AppServer
HP-UX and Solaris	/opt/WebSphere/AppServer
Windows	drive\Program Files\WebSphere\AppServer

Platform	Path
AIX	/usr/WebSphere/DeploymentManager
Linux	/opt/WebSphere/DeploymentManager
HP-UX and Solaris	/opt/WebSphere/DeploymentManager
Windows	drive\Program Files\WebSphere\DeploymentManager

Operating system platform	Cumulative Fix 3 ZIP file	Cumulative Fix 3 ID	Default repository in installation root directory
AIX	was510_cf3_aix.zip	was510_cf3_aix	../update/ fixpacks
Linux	was510_cf3_linux.zip	was510_cf3_linux
Linux for S/390	was510_cf3_linux390.zip	was510_cf3_linux390
Solaris	was510_cf3_solaris.zip	was510_cf3_solaris
HP-UX	was510_cf3_hpux.zip	was510_cf3_hpux
Windows	was510_cf3_win.zip	was510_cf3_win	..\update\ fixpacks

Operating system platform	Cumulative Fix 3 ZIP file	Cumulative Fix 3 ID	Default repository in installation root directory
AIX	was510_nd_cf3_aix.zip	was510_nd_cf3_fp2_aix	../update/fixpacks
Linux	was510_nd_cf3_linux.zip	was510_nd_cf3_linux
Linux for S/390	was510_nd_cf3_linux390.zip	was510_nd_cf3_linux390
Solaris	was510_nd_cf3_solaris.zip	was510_nd_cf3_solaris
HP-UX	was510_nd_cf3_hpux.zip	was510_nd_cf3_hpux
Windows platforms	was510_nd_cf3_win.zip	was510_nd_cf3_win	..\update\ fixpacks

Operating system platform	Cumulative Fix 2 ZIP file	Cumulative Fix 2 ID	Default repository in installation root directory
AIX	was510_cf2_aix.zip	was510_cf2_aix	../update/ fixpacks
Linux	was510_cf2_linux.zip	was510_cf2_linux
Linux for S/390	was510_cf2_linux390.zip	was510_cf2_linux390
Solaris	was510_cf2_solaris.zip	was510_cf2_solaris
HP-UX	was510_cf2_hpux.zip	was510_cf2_hpux
Windows	was510_cf2_win.zip	was510_cf2_win	..\update\ fixpacks

Operating system platform	Cumulative Fix 2 ZIP file	Cumulative Fix 2 ID	Default repository in installation root directory
AIX	was51_nd_cf2_aix.zip	was51_nd_cf2_fp2_aix	../update/fixpacks
Linux	was51_nd_cf2_linux.zip	was51_nd_cf2_linux
Linux for S/390	was51_nd_cf2_linux390.zip	was51_nd_cf2_linux390
Solaris	was51_nd_cf2_solaris.zip	was51_nd_cf2_solaris
HP-UX	was51_nd_cf2_hpux.zip	was51_nd_cf2_hpux
Windows platforms	was51_nd_cf2_win.zip	was51_nd_cf2_win	..\update\ fixpacks

Operating system platform	Fix Pack 1 ZIP file	Fix Pack 1 ID	Default repository in installation root directory
AIX	was51_fp1_aix.zip	was51_fp1_aix	../update/ fixpacks
Linux	was51_fp1_linux.zip	was51_fp1_linux
Linux for S/390	was51_fp1_linux390.zip	was51_fp1_linux390
Solaris	was51_fp1_solaris.zip	was51_fp1_solaris
HP-UX	was51_fp1_hpux.zip	was51_fp1_hpux
Windows	was51_fp1_win.zip	was51_fp1_win	..\update\ fixpacks

Operating system platform	Fix Pack 1 ZIP file	Fix Pack 1 ID	Default repository in installation root directory
AIX	was51_nd_fp1_aix.zip	was51_nd_fp1_aix	../update/fixpacks
Linux	was51_nd_fp1_linux.zip	was51_nd_fp1_linux
Linux for S/390	was51_nd_fp1_linux390.zip	was51_nd_fp1_linux390
Solaris	was51_nd_fp1_solaris.zip	was51_nd_fp1_solaris
HP-UX	was51_nd_fp1_hpux.zip	was51_nd_fp1_hpux
Windows platforms	was51_nd_fp1_win.zip	was51_nd_fp1_win	..\update\ fixpacks

Operating system platform	Fix Pack 1 ZIP file	Fix Pack 1 ID	Default repository in installation root directory
AIX	wbisf51_fp1_aix.zip	wbisf51_fp1_aix (to extend the base product)	../update/ fixpacks
AIX	wbisf51_fp1_aix.zip	wbisf51_nd_fp1_aix (to extend the Network Deployment product)
Linux	wbisf51_fp1_linux.zip	wbisf51_fp1_linux (base)
Linux	wbisf51_fp1_linux.zip	wbisf51_nd_fp1_linux (Network Deployment)
Linux for S/390	wbisf51_fp1_linux390.zip	wbisf51_fp1_linux390 (base)
Linux for S/390	wbisf51_fp1_linux390.zip	wbisf51_nd_fp1_linux390 (Network Deployment)
Solaris	wbisf51_fp1_solaris.zip	wbisf51_fp1_solaris (base)
Solaris	wbisf51_fp1_solaris.zip	wbisf51_nd_fp1_solaris (Network Deployment)
HP-UX	wbisf51_fp1_hpux.zip	wbisf51_fp1_hpux
HP-UX	wbisf51_fp1_hpux.zip	wbisf51_nd_fp1_hpux (Network Deployment)
Windows platforms	wbisf51_fp1_win.zip	wbisf51_fp1_win (base)	..\update\ fixpacks
Windows platforms	wbisf51_fp1_win.zip	wbisf51_nd_fp1_win (Network Deployment)	..\update\ fixpacks

Operating system platform	Fix Pack 1 ZIP file	Fix Pack 1 ID	Default repository in installation root directory
AIX	was51_express_fp1_aix.zip	was51_express_fp1_aix	../update/ fixpacks
Linux	was51_express_fp1_linux.zip	was51_express_fp1_linux
Linux for S/390	was51_express_fp1_linux390.zip	was51_express_fp1_linux390
Solaris	was51_express_fp1_solaris.zip	was51_express_fp1_solaris
HP-UX	was51_express_fp1_hpux.zip	was51_express_fp1_hpux
Windows platforms	was51_express_fp1_win.zip	was51_express_fp1_win	..\update\ fixpacks

Operating system platform	Fix Pack 1 ZIP file	Fix Pack 1 ID	Default repository in installation root directory
AIX	was51_client_fp1_aix.zip	was51_client_fp1_aix	../update/fixpacks
Linux	was51_client_fp1_linux.zip	was51_client_fp1_linux
Linux for S/390	was51_client_fp1_linux390.zip	was51_client_fp1_linux390
Solaris	was51_client_fp1_solaris.zip	was51_client_fp1_solaris
HP-UX	was51_client_fp1_hpux.zip	was51_client_fp1_hpux
Windows platforms	was51_client_fp1_win.zip	was51_client_fp1_win	..\update\fixpacks