[Version 5.0.1 and later]Removing a fix from a Network Deployment node

This topic describes the proper procedure for using the update installer application to uninstall an interim fix, a cumulative fix, or a fix pack on a deployment manager node. The update installer program is also known as the updateInstaller program or the Update installation wizard.

Before you begin

The update installer program uninstalls interim fixes, cumulatives fixes, and fix packs from WebSphere Application Server products. See Installing interim fixes, cumulative fixes, and fix packs to install an interim fix, a cumulative fix, or a fix pack.

Why and when to perform this task

This procedure describes a scenario for removing an interim fix, a cumulative fix, or a fix pack from an entire Network Deployment cell, or from any part of the cell. According to the guidelines, uninstall the interim fix, cumulative fix, or fix pack from each base node in a cell before you uninstall the interim fix, cumulative fix, or fix pack from the deployment manager node.

Always uninstall the highest level interim fix, cumulative fix, or fix pack before uninstalling other interim fixes or fix packs.

Steps for this task

  1. Stop all Java processes on the machine that use the IBM SDK that WebSphere Application Server provides to support the Java 2 SDK on your operating system platform, as described in Uninstalling interim fixes, cumulative fixes, and fix packs.
  2. Remove the highest level interim fix, cumulative fix, or fix pack from all base nodes, as described in Removing a fix from a base node.
    If you remove the interim fix, cumulative fix, or fix pack from every base node in the cell, you can also remove the interim fix, cumulative fix, or fix pack from the Network Deployment node. The interim fix level of the Network Deployment node must be equal to, or higher than the interim fix level of any base node in the cell.
  3. Stop the deployment manager with the stopManager command.
  4. Set up and configure your WebSphere Application Server environment.

    Set the JAVA_HOME environment variable for the update installer.

    Windows systems:

    1. Open a command prompt window.
    2. Change directories to the install_root\bin directory.
    3. Issue the setupCmdLine.bat command.
    4. Use the same command prompt window to start the update installer, as described in the appropriate procedure.

    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. Use the same command shell window to start the update installer, as described in the appropriate procedure.

  5. Use the appropriate command to remove the interim fix, cumulative fix, or fix pack from the base node.

    Depending on the interface you use to the update installer:

    [5.0 only][Version 5.0.2]For example, to uninstall the was50_nd_fp2_win fix pack, use this updateSilent command:

    C:\WebSphere\AppServer\update> updateSilent -fixpack
           -installDir "C:\Program Files\WebSphere\AppServer"
           -skipIHS
           -fixpackDir "C:\WebSphere\AppServer\update\fixpacks"
           -uninstall
           -fixpackID was50_nd_fp2_win
    The command is shown here on more than one line, for clarity.

  6. Uninstall the Network Deployment product manually if you cannot successfully uninstall the interim fix, cumulative fix, or fix pack.

    The following platform-specific procedures for uninstalling each describe a manual process that guides you through removing every trace of the products and features you might have installed, including directories that might have changed data.

    Before you begin one of the procedures, back up the config and properties directories in the installation root. Backing up the directories lets you refer to the changed data when you reinstall.

  7. Start the deployment manager node with the startManager command.
  8. 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 removal 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 version and history information 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 Product version and history information 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 TARGET NOT FOUND FOR LOOKUP 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 TARGET NOT FOUND FOR LOOKUP for more information.

    You can also run the installation verification tool on the node to verify that the node is operational. See Using the installation verification test for more information.

  9. Specify that file sets on one 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.

  10. Verify that all nodes are online and that the cell is functioning correctly.
  11. Restore your original file synchronization settings.
    The cell is now fully functional. All operations are available and functioning normally.

Results

You can successfully remove interim fixes, cumulative fixes, and fix packs from a deployment manager node.

What to do next

Return to Uninstalling interim fixes, cumulative fixes, and fix packs to continue.

Related tasks
Uninstalling interim fixes, cumulative fixes, and fix packs
Related reference
updateSilent command
updateWizard command



Searchable topic ID:   tinsnukefixnd
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_nukefixnd.html

Library | Support | Terms of Use | Feedback