[Version 5.0.2 and later]Using the update installer to update a base node

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.

[5.0 only][Version 5.0.2]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

  1. Install the interim fix, the cumulative fix, or the fix pack on the deployment manager node first if the base node is part of a cell, as described in Using the update installer application to update a deployment manager node.
    The deployment manager node must have the highest fix level within the cell.
  2. Stop the nodeagent process on a managed base node with the stopNode command if the node is part of a cell and if you have not already done so.
    Issue the stopNode command from the install_root/bin directory of each managed node. For example, issue the following command on a Linux platform:
    ./stopNode.sh -user name -password password

    See stopNode command for more information about the command.

  3. Stop each server process on the base WebSphere Application Server node with the stopServer command.
    Issue the stopServer command from the install_root/bin directory of each managed node. For example, issue the following command on a Linux platform:
    ./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.

  4. Create the install_root/update directory on the Application Server node, if the directory does not already exist. Later, you will also launch the update installer from this directory. Launching the update installer is not supported from a read-only directory, or from a directory with spaces in its name.

    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.

  5. Create the update/fixes repository if you are installing an interim fix.
    It is not necessary to create the fixpacks repository directory. Unpacking a cumulative fix or a fix pack creates the fixpacks directory if the directory does not already exist.
  6. Download the interim fix, the cumulative fix, or the fix pack.
    Download an interim fix from the Support page to the update/fixes directory. Download a fix pack to the update directory.
  7. Unpack the interim fix, the cumulative fix, or the fix pack.
    Unpacking a cumulative fix or a fix pack automatically creates the fixpacks directory.
    Installation tip

    Operating platform Tip in
    Windows platforms Use another unzip product such as WINZIP, instead of the PKWARE pkunzip utility to unzip the product archive.



  8. Download the ZIP file for the current update installer and extract the update installer application to the update directory.
    You can use the update installer application that is packaged as part of a fix pack. Or, you can download the current version of the file even though you might have an update installer from the fix pack or from a previous fix installation. The Support page links to the current installer for the version of the product that you are updating.
  9. Verify that the unpacked files are owned by root on a Linux or UNIX-based platform.
    1. List the contents of the download directory.
      For example:

      # ls -al
      
      drwxr-xr-x    6 root     bin           512 Jul 21 08:50 was51fp1_linux
      The directory list in the preceding example shows a Fix Pack 1 file for V5.1 that is not owned by root.

    2. Change the ownership of any files not owned by root.
      You can change the ownership of all files in the download directory.

      For example:

      # chmod -R root:root * 

  10. Set up the Java environment for the update installer.

    Windows systems:

    1. Open a command prompt window if one is not already open.
    2. Change directories to the install_root\bin directory.
    3. Issue the setupCmdLine.bat command.
    4. Change directories to theinstall_root\update directory.

    Linux and UNIX systems:

    1. Open a command shell window if one is not already open.
    2. Change directories to the /install_root/bin directory.
    3. Issue the . ./setupCmdLine.sh command. Notice the space between the periods. The special format for this command sources the command to make the setting active for all processes started from the command shell.
    4. Change directories to the/install_root/update directory.

  11. Install the interim fix, cumulative fix, or fix pack on the base node.

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

  12. Restart the node agent of the base node with the startNode command if the node is federated.
    Restart the node agent on each managed node to let the node agent continue to communicate with the updated deployment manager node.

    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.sh
    See startNode command for more information about the command.

  13. Restart each server on the base node with the startServer command.
    Issue the startServer command from the install_root/bin directory of each managed node. For example, issue the following command on a Linux platform:
    ./startServer.sh server1

    See startServer command for more information about the command.

  14. Verify that the Application Server node is fully functional and that it has the interim fix, the cumulative fix, or the fix pack applied.
    There are several ways to verify the successful application of an interim fix, a cumulative fix, or a fix pack:
    • Does the fix show up in the wizard panel that lists the appropriate type of installed fix?

      If you see the interim fix, the cumulative fix, or the fix pack in one of the panels, the fix is installed.

    • Does the fix show up in the wizard panel that the appropriate type of installable (not yet installed) fix ?

      If you see the interim fix, the cumulative fix, or the fix pack in one of the panels, the fix is not installed.

    • Does one of the following files exist in the install_root/properties/version/version directory?
      • [interim_fix_ID].efix
      • [cumulative_fix_ID].ptf
      • [fix_pack_ID].ptf

      Or, does one of the following files exist in the install_root/properties/version/history directory?

      • [interim_fix_ID].efixApplied
      • [interim_fix_ID].efixDriver
      • [cumulative_fix_ID].ptf
      • [cumulative_fix_ID].ptf
      • [fix_pack_ID].ptfApplied
      • [fix_pack_ID].ptfDriver

      These types of files indicate the installation of a fix. See Product information files for more information.

    • Do the reports that describe the product version and its history show that the interim fix, the cumulative fix, or the fix pack is installed or that it has been removed?

      See Reports for more information about the reports.

    • Do the updateSilent command options for viewing information about interim fixes show that the interim fix is installed or removed?

      See Viewing information about interim fixes for more information.

    • Do the updateSilent command options for viewing information about cumulative fixes and fix packs show that the cumulative fix or the fix pack is installed or removed?

      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.

Related tasks
Installing interim fixes, cumulative fixes, and fix packs



Searchable topic ID:   ptfbase
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_ptfbase.html

Library | Support | Terms of Use | Feedback