WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Uninstalling maintenance packages

This topic describes how to use the Update Installer for WebSphere Software to uninstall interim fixes, fix packs, and refresh packs. The Update Installer for WebSphere Software is also known as the update installer program, the updateInstaller program, and the Update installation wizard.

Before you begin

Use the proper authorizations to successfully uninstall product updates. Use the update installer program as the root user on a Linux or UNIX platform, or as the administrator on a Windows platform.

[AIX HP-UX Linux Solaris Windows] The Update Installer wizard is an InstallShield for Multiplatforms wizard that runs with either a graphical user interface or in silent mode with a response file.

The following descriptions contain reference information about uninstalling interim fixes, fix packs, and refresh packs on WebSphere Application Server products:
Overview of the uninstallation procedure
To uninstall a maintenance package:
  1. Use the update installer to install the maintenance package, which creates a backup file in the app_server_root/properties/version/nif/backup directory. IBM does not support user modifications to backup files.
  2. Use the update installer program to remove the maintenance package as described in this topic.
Viewing the fix level of the node
You can use the versionInfo command in the app_server_root/bin directory to display the exact fix and version level of the product. However, do not use the versionInfo command while installing or uninstalling a maintenance package.

[AIX HP-UX Linux Solaris Windows] Do not launch multiple copies of the Update Installer wizard at one time: Concurrent launches of the update installer program are not supported. Performing more than one update at the same time can produce unpredictable results, which might include a failed or faulty installation.

[AIX HP-UX Linux Solaris Windows] New or updated for this feature pack Use the Update Installer wizard provided with a feature pack to uninstall a fix pack or interim fix: If you have a feature pack installed, do not use the Update Installer wizard provided with the Version 6.1 WebSphere Application Server product to uninstall a fix pack or interim fix because that wizard might uninstall a maintenance package required by the feature pack. Use the Update Installer wizard provided with the feature pack.

Required information

The graphical interface requires the following information that you must supply:
Table 1. Information required when uninstalling a maintenance package
Field Valid values Description
File path of the installation root directory of the WebSphere product and the Update Installer Identify the installation root directory for one of the following products:
  • IBM WebSphere Application Server
  • IBM WebSphere Application Server - Express
  • Embedded version of the IBM WebSphere Application Server - Express
  • IBM WebSphere Application Server Network Deployment
  • IBM Application Client for WebSphere Application Server
  • Web server plug-ins for WebSphere Application Server

The Update Installer application defaults to the last-visited product location.

File name of the maintenance package to uninstall. Select a maintenance package to uninstall from the app_server_root/properties/version/ update/backup directory. The default maintenance package is the package with the latest date stamp and time stamp in the app_server_root /properties/version/ update/backup directory.

About this task

The following procedure describes how to uninstall a maintenance package.

Procedure

  1. Log on to the operating system.
    [Linux] [AIX HP-UX Solaris] In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:
    umask
    To set the umask setting to 022, issue the following command:
    umask 022
  2. Change directories to the updi_root directory.
  3. [Windows] Use the Windows Services panel to stop all services for WebSphere Application Server processes.
  4. Stop all Java processes that use the IBM Software Developer Kit (SDK) that the WebSphere Application Server product provides.

    Before uninstalling interim fixes, fix packs, and refresh packs on a machine, stop all Java processes on the machine that use the IBM SDK, Java Technology Edition that WebSphere Application Server provides.

    WebSphere Application Server processes include:
    • Application server processes
    • The nodeagent process on an application server node when the node is federated into a deployment manager cell
    • The dmgr process for the deployment manager server

    Stop all Java processes if necessary. If you uninstall a maintenance package while a WebSphere Application Server-related Java process runs, IBM does not guarantee that the product can continue to run successfully, or without error.

  5. Use the update installer to uninstall the maintenance package.

    Uninstall the interim fix on each application server node in a cell before uninstalling the maintenance package from the deployment manager node.

    [AIX HP-UX Linux Solaris Windows] Issue one of the following commands to uninstall with the graphical interface:
    Table 2. Update installer commands for uninstalling with the graphical interface
    Command example Type of installation Description
    update.bat -W update.type="uninstall" Graphical interface mode Initializes the maintenance package field with the name of the maintenance package that was most recently installed.

    Accept all of the default values to uninstall the maintenance package with the most recent date stamp and time stamp.

    update.bat -W product.location="e: \IBM\WebSphere\AppServer" -W update.type="uninstall" Graphical interface mode Overrides the graphical interface with the location of the WebSphere software to update. The default maintenance package to uninstall is the most recently installed maintenance package for that software.
    update.bat -W backup.package="PQ20029.pak" -W update.type="uninstall" Graphical interface mode Overrides the maintenance package field with the name of the maintenance package to uninstall.
    update.bat -W product.location="e: \IBM\WebSphere\AppServer" -W backup.package="PQ20029.pak" -W update.type="uninstall" Graphical interface mode Overrides the location of the WebSphere software to update and the name of the maintenance package to uninstall.
    update.bat -options "responsefiles/file_name" Graphical interface mode with an options file Overrides all default values with values that you specified in the options response file.

    If you omit either value from the response file, the default maintenance package is the installed package with the most recent date stamp and time stamp. The default software is the software installed in the parent directory.

    [AIX HP-UX Linux Solaris Windows] Issue the following command to use the silent interface:
    Table 3. Update installer command for uninstalling in silent mode
    Command example Type of installation Description
    update.bat -W backup.package="PQ20029.pak" -W update.type="uninstall" Silent mode with an options file Overrides all default values with values that you specified in the options response file.

    Always use a response file that is based on the response file under updi_root/responsefiles.

    Note: The commands for installing and uninstalling maintenance silently are different. Installation requires specifying the maintenance package using maintenance.package and uninstallation requires backup.package

    For example:

    • Install maintenance silently: update.bat -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak"
    • Uninstall maintenance silently: update.bat -W backup.package="PQ20029.pak" -W update.type="uninstall"
    [i5/OS] Issue the following command to use the silent interface for iSeries:
    Table 4. Update installer command for uninstalling in silent mode for iSeries
    Command example Type of installation Description
    update -options "responsefiles/file_name" Silent mode with an options file Overrides all default values with values that you specified in the options response file.

    Always use a response file that is based on the response file under updi_root/responsefiles.

Results

This procedure results in uninstalling maintenance packages to update WebSphere software.

When you uninstall fix pack 6.1.0.11 to the previous release, to ensure that all interim fixes associated with 6.1.0.9 are restored, the Update Installer automatically restores the required interim fixes for that release during the uninstall process.

Note: The Update Installer should not check OS prerequisites when uninstalling Custom Installation Package created by the Install Factory. When you launch the Update Installer to uninstall a Custom Installation Package, additional command line options need to be passed into Update Installer to disable OS prerequisite checking. These command line options are:
-W maintenancewarningprereqcheckactionInstallWizardBean.active=false -W prereqswarningpanelInstallWizardBean.active=false -W maintenanceprereqcheckactionInstallWizardBean.active=false -W prereqsfailedpanelInstallWizardBean.active=false
On Windows issue the command:
update.bat -W maintenancewarningprereqcheckactionInstallWizardBean.active=false -W prereqswarningpanelInstallWizardBean.active=false -W maintenanceprereqcheckactionInstallWizardBean.active=false -W prereqsfailedpanelInstallWizardBean.active=false
On operating systems such as AIX or Linux, issue the command:
./update.sh -W maintenancewarningprereqcheckactionInstallWizardBean.active=false -W prereqswarningpanelInstallWizardBean.active=false -W maintenanceprereqcheckactionInstallWizardBean.active=false -W prereqsfailedpanelInstallWizardBean.active=false

What to do next

After uninstalling maintenance packages, you can continue to use the WebSphere software.

Rolling back changes to existing profiles: Some maintenance packages for WebSphere Application Server products, such as Refresh Pack 2, update existing profiles. If you roll back a maintenance package that contains a profile update, also use any undo scripts provided with the profile update script to roll back changes to the existing profiles.

The readme file for a maintenance package describes scripts that update and scripts that roll back profile fix levels. For example, Refresh Pack 2 for WebSphere Application Server includes required service for the JDBC resource provider templates in existing profiles. See the readme for the profile update and undo scripts for the JDBC-related update for more information.

Deleting profiles created by a service level that is now rolled back: Ensure that all profiles are at the same service level or at a lower service level than the WebSphere Application Server product.

For example, suppose that you install Fix Pack 1 for Version 6.1 (Version 6.1.0.1), create a new profile, and then roll back Fix Pack 1. You must delete the profile that you created at the Version 6.1.0.1 level to avoid possible problems.




In this information ...


Subtopics

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tins_removePTF.html