This topic describes the proper procedure for using the update installer program to install interim fixes, cumulative fixes, and fix packs on an extended 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.The
update installer program installs interim fixes, cumulative fixes, and fix
packs on WebSphere Application Server products, which include Enterprise.
Why and when to perform this task
This topic describes using the update installer
application to install an interim fix, a cumulative fix, or a fix pack for
the Enterprise product on any Application Server product node in an entire
cell, including the deployment manager node. It also describes how to install
the fix for the Enterprise product on a stand-alone base Application Server
node. According to the "Special rules for applying fixes within a cell" guidelines
in Installing interim fixes, cumulative fixes, and fix packs:
Steps for this task
./stopNode.sh -user name -password password
See stopNode command for more information about the command.
Stop all WebSphere Application Server-related Java processes on nodes that you intend to update. Use the administrative console or wsadmin from the deployment manager node. Or go to each managed node and issue the appropriate commands, such as the stopServer command.
You can stop all 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.
If you do not have a deployment manager node, skip to step 14.
./stopManager.sh -user name -password password
See stopManager command for more information about the command.
For example, create the /opt/WebSphere/DeploymentManager/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\DeploymentManager\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 Network Deployment product in the default installation root directory, C:\Program Files\WebSphere\DeploymentManager. The target directory can have a space; the source directory cannot.
You can
choose a different directory to keep from overwriting files when unpacking
a fix pack, cumulative fix, or an interim fix for the Enterprise product.
For example, the fix pack for Enterprise might overwrite files that you unpacked
for the base product if you unpack them both in the update directory.
Add another level to the update directory if you prefer, such as .../update/enterprise.
The only file that gets replaced that is not the same in both fix packs is the product.version file.
Download an interim fix from the Support page to the update/fixes directory. Download a fix pack to the updatedirectory.
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 was51_fp1_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 *
Setting the JAVA_HOME environment variable:
Windows systems:
Linux and UNIX systems:
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\DeploymentManager\update> updateSilent -fixpack -installDir "C:\Program Files\WebSphere\DeploymentManager" -skipIHS -fixpackDir "C:\WebSphere\DeploymentManager\update\fixpacks" -install -fixpackID was51_nd_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.
For example, to install the was51_pme_nd_fp1_win fix pack to the Enterprise product, use this updateSilent command:
C:\WebSphere\DeploymentManager\update> updateSilent -fixpack -installDir "C:\Program Files\WebSphere\DeploymentManager" -skipIHS -fixpackDir "C:\Program Files\WebSphere\DeploymentManager\update\fixpacks" -install -fixpackID wbisf51_nd_fp1_winThe command is shown here on more than one line for clarity.
# ./startManager.sh
See startManager 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.
You can restart all node agents, but you do not need to restart node agents on managed nodes that you intend to update with the interim fix, the cumulative fix, or the fix pack. The interim fix installation, the cumulative fix installation, and the fix pack installation each require you to stop and restart the node agent. You can simply restart the node agent at the appropriate time.
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.
For example, to install the was50_pme_fp2_win fix pack to the Enterprise product, use this updateSilent command:
C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\Program Files\WebSphere\AppServer" -skipIHS -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -install -fixpackID was50_pme_fp2_winThe command is shown here on more than one line, for clarity.
Ensure consistent configuration data across a cell. You can synchronize files on individual nodes or throughout your system. To synchronize files throughout the system, use the deployment manager administrative console page, System administration > Nodes > check_each_node_name > Full Resynchronization. You can use the administrative console page, System Administration > Node Agents > nodeagent > File Synchronization Service, to specify automatic synchronization every minute until all base node servers are brought online.
The cell is now fully functional. All operations are available and functioning normally.
Results
You can successfully install interim fixes,
cumulative fixes, and fix packs on Enterprise-extended nodes.
What to do next
Return to Installing interim fixes, cumulative fixes, and fix packs to continue.