This topic describes how to use the update installer program to install interim fixes, cumulative fixes, and fix packs on a base WebSphere Application Server node.
Before you begin
If you have not already done so, read Installing interim fixes, cumulative fixes, and fix packs for an overview of installing service to WebSphere Application Server products. You must update the deployment manager node before updating managed base nodes, which are base nodes that you have federated into a deployment manager cell.If
you extended the Application Server node by installing the Enterprise product,
see Using the update installer application to update an extended node.
Why and when to perform this task
Install the interim fix, the cumulative fix, or the fix pack on each base node to which you intend to apply the fix using the following procedure for each node.Steps for this task
./stopNode.sh -user name -password password
See stopNode command for more information about the command.
./stopServer.sh server1 -user name -password password
See stopServer command for more information about the command.
Stop all WebSphere Application Server-related Java processes. On a Windows platform, you can use the task manager to stop Java processes. On a Linux or UNIX-based platform, use the kill command or the killall java -9 command to stop Java processes.
Use the Windows Services panel to stop any Windows service for the nodeagent, and for any other WebSphere Application Server related services, including Application Server processes, the jmsserver process, IBM HTTP Server and WebSphere MQ queue managers.
For example, create the /opt/WebSphere/AppServer/update directory on a Linux platform.
On a Windows platform, create the update directory in a path where none of the directory names includes a space in their names. For example, do not create the C:\Program Files\WebSphere\AppServer\update directory because the Program Files directory has a space in its name.
You can install a fix from the C:\WebSphere\update directory, for example, to the Application Server product in the default installation root directory, C:\Program Files\WebSphere\AppServer. The target directory can have a space; the source directory cannot.
Operating platform | Tip in |
---|---|
Windows platforms | Use another unzip product such as WINZIP, instead of the PKWARE pkunzip utility to unzip the product archive. |
# ls -al drwxr-xr-x 6 root bin 512 Jul 21 08:50 was51fp1_linuxThe directory list in the preceding example shows a Fix Pack 1 file for V5.1 that is not owned by root.
For example:
# chmod -R root:root *
Windows systems:
Linux and UNIX systems:
Use the updateWizard command or the updateSilent command to install the interim fix, cumulative fix, or fix pack on the Application Server node. The choice is whether to use a wizard. For more information about using either command, see the following articles:
For example, assume that you are installing Fix Pack 1 on Version 5.1.0.0. To install the was51_nd_fp1_win fix pack, use this updateSilent command:
C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\Program Files\WebSphere\AppServer" -skipIHS -skipMQ -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -install -fixpackID was51_fp1_winThis example skips applying any service that might be in the fix pack for the IBM HTTP Server feature or the embedded messaging feature.
The command is shown on more than one line for clarity.
Issue the startNode command from the install_root/bin directory of each base node. For example, issue the following command on a Linux platform:
./startNode.shSee startNode command for more information about the command.
./startServer.sh server1
See startServer command for more information about the command.
If you see the interim fix, the cumulative fix, or the fix pack in one of the panels, the fix is installed.
If you see the interim fix, the cumulative fix, or the fix pack in one of the panels, the fix is not installed.
Or, does one of the following files exist in the install_root/properties/version/history directory?
These types of files indicate the installation of a fix. See Product information files for more information.
See Reports for more information about the reports.
See Viewing information about interim fixes for more information.
See Viewing information about cumulative fixes and fix packs for more information.
Results
You can successfully install interim fixes, cumulative fixes, and fix packs on a base node.
What to do next
Return to Installing interim fixes, cumulative fixes, and fix packs to continue.