[Version 5.0.2 and later]Using the update installer application to update an extended node

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.

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

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

  1. Install a fix on the deployment manager.
  2. Install a fix on the Enterprise product that extends the deployment manager.
  3. Install a fix on zero, one, or more of the base nodes:
    1. Install a fix on the base product on the node.
    2. Install a fix on the Enterprise product that extends the base node.
  4. Uninstall a fix from the Enterprise product on each base node and from each base node in a cell before you uninstall the fix from the Enterprise product on the deployment manager node and from the deployment manager node.

Steps for this task

  1. Stop the nodeagent process on each managed node that you intend to update in a cell with the stopNode command.
    Use the administrative console or the wsadmin scripting facility from the deployment manager node to stop all node agents on nodes that you intend to update. Or, issue the stopNode command from the install_root/bin directory of each managed node. For example, issue the following command on a managed Linux node:
    ./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.

  2. Stop the deployment manager process with the stopManager command.
    The dmgr Java process is the deployment manager process. Issue the stopManager command from the install_root/bin directory of the deployment manager node. For example, issue the following command on a Linux platform:
    ./stopManager.sh -user name -password password

    See stopManager command for more information about the command.

  3. Create the install_root/update directory on the deployment manager 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/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.

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

  4. 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.
  5. 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 updatedirectory.

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



  7. 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.
  8. 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 was51_fp1_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 * 

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

    Setting the JAVA_HOME environment variable:

    Windows systems:

    1. Open a command prompt window.
    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.
    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.

  10. Install the interim fix, cumulative fix, or fix pack on the deployment manager node.
    1. Use the updateWizard command or the updateSilent command to install the interim fix, cumulative fix, or fix pack on the deployment manager 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\DeploymentManager\update> updateSilent 
         -fixpack 
         -installDir "C:\Program Files\WebSphere\DeploymentManager" 
         -skipIHS 
         -fixpackDir "C:\WebSphere\DeploymentManager\update\fixpacks"
         -install 
         -fixpackID was51_nd_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.

    2. [5.0 only]Install the same level interim fix, cumulative fix, or fix pack on the Enterprise product that extends the network deployment node.
      After installing the interim fix, cumulative fix, or fix pack on the deployment manager node, apply the same level fix to the Enterprise product that extends the network deployment node.

      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_win
      The command is shown here on more than one line for clarity.

  11. Bring the deployment manager node back online with the startManager command.
    Issue the startManager command from the install_root/bin directory of the deployment manager node. For example, issue the following command on a Linux platform:
    # ./startManager.sh

    See startManager command for more information about the command.

  12. Verify that the deployment manager 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 installation 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.

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

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

  14. Install the interim fix, the cumulative fix, or the fix pack on each base node that is managed by the deployment manager and that is a node to which you intend to apply the fix.
    See Using the update installer to update a base node for information about how to perform this step.
  15. [5.0 only]Install the interim fix, cumulative fix, or fix pack on the Enterprise product of each base node.
    After installing the interim fix or fix pack to the base product, apply the same level interim fix or fix pack to the Enterprise product that extends the base node.

    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_win
    The command is shown here on more than one line, for clarity.

  16. Restart each server on the node with the startServer command.
  17. Restart the node agent for the base node with the startNode command if the node is part of a cell.
  18. Verify that the base node is fully functional and that it has the interim fix, the cumulative fix, or the fix pack installed.
  19. Specify that file sets on each base node match those on the deployment manager node.

    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.

  20. Verify that all nodes are online and that the cell is functioning correctly.
  21. Restore your original file synchronization settings, if you changed them.

    The cell is now fully functional. All operations are available and functioning normally.

Results

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

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



Searchable topic ID:   ptfwbisf
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tins_ptfwbisf.html

Library | Support | Terms of Use | Feedback