IBM WebSphere Update Installer for WebSphere Software

Readme

How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information.

• To send comments on articles in the WebSphere Application Server information center:
  1. Display the article in your Web browser and scroll to the end of the article.
  2. Click on the Feedback link at the bottom of the information center article, and a separate window containing an e-mail form appears.
  3. Fill out the e-mail form as instructed, and click on Submit feedback .
• To send comments on PDF books or readme files, you can e-mail your comments to: wasdoc@us.ibm.com or fax them to 919-254-0206.

  Be sure to include the document name and number, the WebSphere Application Server version you are using, and, if applicable, the specific page, table, or figure number on which you are commenting.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Applying service

Use the proper authorizations to successfully install 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.

The Update Installer wizard is an InstallShield for Multiplatforms wizard that runs with either a graphical user interface or in silent mode with or without a response file. (When you omit the response file in silent mode, the wizard installs the last maintenance file that you downloaded to the default maintenance directory.)

The following descriptions contain reference information about installing interim fixes, fix packs, and refresh packs on WebSphere Application Server products:

Overview of the installation procedure

To install an interim fix:

1. Download the update installer ZIP or TAR file from the Support Web site into the install_root directory or a temp directory.
2. Unpack the update installer ZIP or TAR file that you downloaded to create the updateinstaller directory and several subdirectories, including the maintenance directory.
3. Download the interim fix from the Support Web site into the maintenance directory.
4. Use the update installer to install the interim fix, which creates a backup file in the install_root/properties/version/update/backup directory. IBM does not support user modifications to backup files.

Viewing the fix level of the node

You can use the versionInfo command in the install_root/bin directory to display the exact fix and version level of the product. However, do not use the versionInfo command while installing an interim fix.

Updating cluster members

Apply the same interim fixes to all of the WebSphere Application Server nodes in a cluster. When all of the cluster members are not at the same service level, the following exception can occur:

DRSCacheApp   E DRSW0008E: 
   Exception is: com.ibm.disthub.impl.jms.JMSWrappedException: 
   {-1361012295|unknown|java.io.OptionalDataException|} 

This error can cause memory replication to not function properly.

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.

Required information

The graphical interface requires the following information that you must supply:

The following procedure describes how to install an interim fix to update an installed product. See Uninstalling service for a description of how to remove an interim fix.

1. Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.

   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. Install the product that you intend to update.

   You have very likely already installed the software that you are now updating. But if not, install the software now.

3. Download the update installer from the Support Web site into the installation root directory.

   Download the ZIP or TAR file for the Update Installer for WebSphere Software from one of the following IBM Web sites:

   • IBM Support site for IBM WebSphere Extended Deployment
   • IBM Support site for WebSphere Application Server

   For example, download the Update Installer to one of the following directories in a Version 6 environment:

   • /usr/IBM/WebSphere/AppServer
   • /opt/IBM/WebSphere/AppServer
   • /opt/IBM/WebSphere/AppServer
   • /opt/IBM/WebSphere/AppServer
   • C:\Program Files\IBM\WebSphere\AppServer

   Or to one of the following directories in a Version 5.1.1.1 Extended Deployment environment:

   • /usr/WebSphere/DeploymentManager
   • /opt/WebSphere/DeploymentManager
   • /opt/WebSphere/DeploymentManager
   • /opt/WebSphere/DeploymentManager
   • C:\Program Files\WebSphere\DeploymentManager
4. Unpack the update installer to create the following directory structure:

   install_root
      /updateinstaller
         /framework
         /lib
         /maintenance
         /responsefiles

   Version information is stored in the version.txt file in the updateinstaller directory. A new version might ship to correspond to any new fix. Information in the version.txt file is displayed prominently in the title bar of the wizard and is also recorded in the updatelog.txt file. Always use the latest version of the Update Installer wizard.

5. Download the interim fix PQ*.pak file from the Support Web site into the maintenance directory.

   Download service for the Update Installer for WebSphere Software to install from the following IBM Web pages:

   • Download interim fixes for IBM WebSphere Extended Deployment, Version 5.1 from the IBM Support site for IBM WebSphere Extended Deployment.
   • Download interim fixes for Version 6 of the WebSphere Application Server products from the IBM Support site for WebSphere Application Server.
   Tip:
   Do not attempt to unzip or unpack the *.pak file.
6. Use the Windows Services panel to stop all services for WebSphere Application Server processes.
7. Stop all Java processes that use the IBM Software Developer Kit (SDK) that the WebSphere Application Server product provides.

   Before installing or 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 install an interim fix while a WebSphere Application Server-related Java process runs, IBM does not guarantee that the product can continue to run successfully, or without error.

8. Determine if you are updating the IBM SDK, Java Technology Edition. If so, copy the IBM SDK from the parent product to the Update Installer wizard directory. For example, copy the install_root/java directory to the install_root/updateinstaller/java directory.

   The Update Installer for WebSphere Software searches known locations for a suitable IBM SDK to use. In order, the Update Installer wizard looks for a valid Java Virtual Machine (JVM) in the following locations:

   1. The install_root/updateinstaller/java directory (when updating the product SDK)
   2. The install_root/java directory (preferred SDK to use)
   3. The directory identified by one of the following environment variables on a Linux or UNIX system:
      1. JAVA_HOME
      2. JAVAHOME
      3. JRE_HOME
      4. JREHOME

      When no JVM is present in one of the first two locations, set one of the environment variables to point the Update Installer wizard to a valid JVM.

   The preferred SDK for starting the Update Installer wizard is the SDK in the parent product. Always use the product SDK when possible.

   Important:
   To install a fix pack or interim fix for the IBM SDK in the parent product, do not start the Update Installer wizard using the product SDK that you intend to update. Using the SDK locks the SDK and prevents the update. Copy the SDK from the install_root/java directory to the install_root/updateinstaller/java directory. The Update Installer wizard uses the SDK in the install_root/updateinstaller/java directory if it is present.

   Alternatively, copy the IBM SDK from the parent product to a temporary location and use the -is:javahome ISMP parameter to identify the location as you run the update installer command:

   update -is:javahome="my_fully_qualified_temp_SDK_location"

9. Verify that the required free space is available before beginning the installation.

   The space required in the product directory for installing an interim fix is approximately three times the size of the downloaded interim fix.

10. Verify that the following prerequisite conditions are met:
    • All of the product hardware and software prerequisites exist.

      The official statement of supported hardware and software is on the IBM WebSphere Application Server supported hardware and software Web site, at http://www.ibm.com/software/webservers /appserv/doc/latest/prereq.html.

    • The WebSphere software that you are updating is correctly installed and is not corrupt.
    • The WebSphere SDK, Java technology edition is not corrupt.
    • The user is root on a Linux or UNIX system or a member of the administrator group on a Windows system.
11. Use the update installer to install the interim fix.

    Install the interim fix on the deployment manager node before installing the interim fix on each application server node that you intend to update.

    Issue one of the following commands to use the graphical interface:

    Table 2. Update installer commands for installing with the graphical interface

    Command example	Type of installation	Description
    update	Graphical interface mode	Initializes the interim fix field with the name of the interim fix that has the most recent date stamp and time stamp. Accept all of the default values to install the interim fix with the most recent time stamp.
    update -W prereqsfailedpanelInstallWizardBean.active= "false"	Graphical interface mode that bypasses prerequisites checking	Initializes the interim fix field with the name of the interim fix that has the most recent date stamp and time stamp. Bypasses prerequisites checking.
    update -options "responsefiles/file_name"	Graphical interface mode with an options file	Overrides all graphical interface values with values that you specified in the options response file. If you omit either value, the default maintenance package is the one with the most recent date stamp and time stamp. The default software is the software installed in the parent directory.
    update -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak"	Graphical interface mode	Overrides the name of the maintenance package to apply.
    update -W product.location="e: \IBM\WebSphere\AppServer"	Graphical interface mode	Overrides the location of the WebSphere software to update.
    update -W product.location="e: \IBM\WebSphere\AppServer" -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak"	Graphical interface mode	Overrides the location of the WebSphere software to update and the name of the maintenance package to apply.

    Issue one of the following commands to use the silent interface:

    Table 3. Update installer commands for installing in silent mode

    Command example	Type of installation	Description
    update -silent	Silent mode	Installs the interim fix with the most recent time stamp to update the software that is installed in the parent directory.
    update -silent -W prereqsfailedpanelInstallWizardBean.active= "false"	Silent mode that bypasses prerequisites checking	Installs the interim fix with the most recent time stamp to update the software that is installed in the parent directory. Bypasses prerequisites checking.
    update -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance \PQ20029.pak" -silent	Silent mode	By default, the wizard installs the interim fix with the most recent date stamp and time stamp. Use the package override to install another maintenance package. You do not need a response file. The default software is the software installed in the parent directory.
    update -silent -options "responsefiles/file_name"	Silent 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 one with the most recent date stamp and time stamp. The default software is the software installed in the parent directory.
    update -W product.location="e: \IBM\WebSphere\AppServer" -silent	Silent mode	Updates the WebSphere software specified in the command with the maintenance package that has the most recent date stamp and time stamp. The silent installation does not refer to a response file.
    update -W product.location="e: \IBM\WebSphere\AppServer" -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance \PQ20029.pak" -silent	Silent mode	Updates the WebSphere software specified in the command with the maintenance package specified in the command. The silent installation does not refer to a response file.

This procedure results in installing interim fixes to update WebSphere software.

After installing an interim fix, continue to use your WebSphere software.

install.txt

Install an update silently using the options response file.

The install.txt file has one directive that identifies the backup file for installing a service update. Comments in the file describe how to set the string value.

The Update Installer for WebSphere Software wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt for a silent installation:

./update -options "responsefiles/myresponsefile.txt" -silent

If you do not use the -silent option, the response file provides initial values for the graphical interface.

Location of the response file

The sample options response file is named install.txt. The file is in the install_root/updateinstaller/responsefiles directory after you unzip the Update Installer for WebSphere Software into the installation root directory of the WebSphere software product.

Installing silently

The options file supplies the values to the Update installer wizard when installing silently. The wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt for a silent installation:

update -options "myresponsefile.txt" -silent

Response file user entry validation

In a silent installation, response file validation is coded into the installation. If the validation does not pass, the failure is recorded in the log files in the install_root/logs/update/tmp directory.

Location of the maintenance package to be installed

Default directive setting

-W maintenance.package=""

Valid setting

You must set this directive to the location of the PAK file. For example, you might specify the following location on a Linux system:

/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PQ20029.pak

Error identifiers:

• Maintenance package maintenance_package_name is already installed on the system.
• Selected product is not supported.
• Configuration failed. The config action that failed was: configuration_action.
• Install the following prerequisite APARs before installing the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ install
• Install the following prerequisite maintenance packages before installing the package you are currently attempting to install: list_ of_ prerequisite_ maintenance_ packages_ to_ install
• Uninstall the following APARs before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall
• Uninstall the following maintenance packages before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall
• Unable to locate the correct version of the_update_installer. Looking for version version_identifier.
• Maintenance_package is not a valid maintenance package.

Alternate product location

Although applying maintenance to another product is possible, always use the Update installer wizard within the directory structure of the product that you are updating. Do not use this directive unless absolutely necessary.

Default directive setting

-W product.location=""

Valid setting

You must set this directive to the installation root directory of the alternate product. For example, you might specify the following location on a Linux system:

/opt/IBM/WebSphere/AppServer2

Error identifiers:

• Maintenance package maintenance_package_name is already installed on the system.
• Selected product is not supported.
• Configuration failed. The config action that failed was: configuration_action.
• Install the following prerequisite APARs before installing the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ install
• Install the following prerequisite maintenance packages before installing the package you are currently attempting to install: list_ of_ prerequisite_ maintenance_ packages_ to_ install
• Uninstall the following APARs before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall
• Uninstall the following maintenance packages before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall
• Unable to locate the correct version of the_update_installer. Looking for version version_identifier.
• Maintenance_package is not a valid maintenance package.
• Alternate_product_directory could not be validated as an existing directory.

Usage notes

• The file is not a read-only file.
• Edit this file directly with your flat file editor of choice, such as Kate on SLES or WordPad on a Windows platform.
• The file must exist to perform a silent installation. The Update installer wizard reads this file to determine installation parameters. Provide the fully qualified file path to the backup file.
• Save the copy of the options file in the responsefiles directory for best results.

Example install.txt file

Edit the version of the file that is included in the Update Installer for WebSphere Software ZIP file. The following example is not guaranteed to be an accurate representation of the actual file.

################################################################################
#
# This is the silent install response file for installing maintenance packages
# using the update installer.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, *uncomment* and modify the parameters defined within.
#
# Use the following command line when running the wizard from the update 
# installer directory:
# 
#    update -options responsefiles/install.txt -silent
#
################################################################################


################################################################################
#
# Used to input the maintenance package full filename specification to be installed. 
# Edit as appropriate.
#
# ie. -W maintenance.package="C:\Program Files\WebSphere\AppServer\
#          updateinstaller\maintenance\PQ20029.pak"
#
# Note: If no package is specified, a default of the last downloaded maintenance 
# package will be used (based on timestamp).
#
#-W maintenance.package=


################################################################################
#
# Used to modify the product install location that will be updated. 
# This value should be left commented out if the Update Installer is 
# being run from the recommended location
#
# ie. -W product.location="C:\Program Files\WebSphere\AppServer"
#
# Note: If no location is specified, the parent directory to update installer 
# will be used as default
#
#-W product.location=""



################################################################################
#
# Do not edit these values.
#
#
-W update.type="install"

Uninstalling service

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.

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 uninstall procedure

To uninstall an interim fix:

1. Use the update installer to install the interim fix, which creates a backup file in the install_root/properties/version/update/backup directory. IBM does not support user modifications to backup files.
2. Use the update installer program to remove the interim fix as described in this topic.

Viewing the fix level of the node

You can use the versionInfo command in the install_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 an interim fix.

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.

Required information

The graphical interface requires the following information that you must supply:

The following procedure describes how to uninstall an interim fix.

1. Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.

   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 updateinstaller directory in the installation root directory.

   For example, change directories to one of the following directories in a Version 6 environment:

   • /usr/IBM/WebSphere/AppServer/updateinstaller
   • /opt/IBM/WebSphere/AppServer/updateinstaller
   • /opt/IBM/WebSphere/AppServer/updateinstaller
   • /opt/IBM/WebSphere/AppServer/updateinstaller
   • C:\Program Files\IBM\WebSphere\AppServer\updateinstaller

   Or change directories to one of the following directories in a Version 5.1.1.1 Extended Deployment environment:

   • /usr/WebSphere/DeploymentManager/updateinstaller
   • /opt/WebSphere/DeploymentManager/updateinstaller
   • /opt/WebSphere/DeploymentManager/updateinstaller
   • /opt/WebSphere/DeploymentManager/updateinstaller
   • C:\Program Files\WebSphere\DeploymentManager\updateinstaller
3. 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 install an interim fix 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. Determine if you are removing a fix that updated the IBM SDK, Java Technology Edition. If so, copy the IBM SDK from the parent product to the Update Installer wizard directory. For example, copy the install_root/java directory to the install_root/updateinstaller/java directory.

   The Update Installer for WebSphere Software searches known locations for a suitable IBM SDK to use. In order, the Update Installer wizard looks for a valid Java Virtual Machine (JVM) in the following locations:

   1. The install_root/updateinstaller/java directory (when updating the product SDK)
   2. The install_root/java directory (preferred SDK to use)
   3. The directory identified by one of the following environment variables on a Linux or UNIX system:
      1. JAVA_HOME
      2. JAVAHOME
      3. JRE_HOME
      4. JREHOME

      When no JVM is present in one of the first two locations, set one of the environment variables to point the Update Installer wizard to a valid JVM.

   The preferred SDK for starting the Update Installer wizard is the SDK in the parent product. Always use the product SDK when possible.

   Important:
   To uninstall a fix pack or interim fix for the IBM SDK in the parent product, do not start the Update Installer wizard using the product SDK that you intend to update. Using the SDK locks the SDK and prevents the update. Copy the SDK from the install_root/java directory to the install_root/updateinstaller/java directory. The Update Installer wizard uses the SDK in the install_root/updateinstaller/java directory if it is present.

   Alternatively, copy the IBM SDK from the parent product to a temporary location and use the -is:javahome ISMP parameter to identify the location as you run the update installer command:

   update -is:javahome="my_fully_qualified_temp_SDK_location"

6. Use the update installer to uninstall the interim fix.

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

   Issue one of the following commands to uninstall with the graphical interface:

   Table 5. Update installer commands for uninstalling with the graphical interface

   Command example	Type of installation	Description
   update -W update.type="uninstall"	Graphical interface mode	Initializes the interim fix field with the name of the interim fix that was most recently installed. Accept all of the default values to uninstall the interim fix with the most recent date stamp and time stamp.
   update -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 interim fix to uninstall is the most recently installed interim fix for that software.
   update -W backup.package="PQ20029.pak" -W update.type="uninstall"	Graphical interface mode	Overrides the interim fix field with the name of the maintenance package to uninstall.
   update -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 -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.

   Issue one of the following commands to use the silent interface:

   Table 6. Update installer commands for installing in silent mode

   Command example	Type of installation	Description
   update -W update.type="uninstall" -silent	Silent mode	Uninstalls the interim fix with the most recent date stamp and time stamp to update the software that is installed in the parent directory.
   update -W product.location="e: \IBM\WebSphere\AppServer" -W update.type="uninstall" -silent	Silent mode	Overrides the default location of the WebSphere software to update. The default interim fix to uninstall is the most recently installed interim fix for that software.
   update -W backup.package="PQ20029.pak" -W update.type="uninstall" -silent	Silent mode	Overrides the interim fix field with the name of the maintenance package to uninstall.
   update -W product.location="e: \IBM\WebSphere\AppServer" -W backup.package="PQ20029.pak" -W update.type="uninstall"	Silent mode	Overrides the location of the WebSphere software to update and the name of the maintenance package to uninstall.
   update -silent -options "responsefiles/file_name"	Silent 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.

This procedure results in uninstalling interim fixes to update WebSphere software.

After uninstalling interim fixes, you can continue to use the WebSphere software.

uninstall.txt

Uninstall an update silently using the options response file.

The uninstall.txt file has one directive that identifies the backup file for uninstalling a service update. Comments in the file describe how to set the string value.

The Update Installer for WebSphere Software wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt for a silent uninstall:

./update -options "responsefiles/myresponsefile.txt" -silent

If you do not use the -silent option, the response file provides initial values for the graphical interface.

Location of the response file

The sample options response file is named uninstall.txt. The file is in the install_root/updateinstaller/responsefiles directory after you unzip the Update Installer for WebSphere Software into the installation root directory of the WebSphere software product.

Uninstalling silently

The options file supplies the values to the Update installer wizard when uninstalling silently. The wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt for a silent uninstall:

update -options "myresponsefile.txt" -silent

Response file user entry validation

In a silent uninstall, response file validation has been coded into the installation. If the validation does not pass, the failure is recorded in the log files in the install_root/logs/update/tmp directory.

Location of the maintenance package to be uninstalled

Default directive setting

-W backup.package=""

Valid setting

You must set this directive to the location of the backup file. The backup file reverses the application of the maintenance. For example, you might specify the following location on a Linux system:

/opt/properties/version/update/backup/maintenance_package_to_uninstall

Error identifiers:

• The maintenance package cannot be uninstalled. Uninstalling the maintenance would break the following superseding maintenance packages. Uninstall the superseding maintenance packages first: list_of_superseding_maintenance_packages
• This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the package that you are attempting to uninstall: list_of_dependent_maintenance_packages
• This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the APARs you are attempting to uninstall: list_of_dependent_maintenance_packages
• No installation backup packages are available for uninstalling maintenance.

Alternate product location

Although uninstalling maintenance from another product is possible, always use the Update installer wizard from the directory structure of the product that you are updating. Do not use this directive unless absolutely necessary.

Default directive setting

-W product.location=""""

Valid setting

You must set this directive to the installation root directory of the alternate product. For example, you might specify the following location on a Linux system:

/opt/IBM/WebSphere/AppServer2

Error identifiers:

• The maintenance package cannot be uninstalled. Uninstalling the maintenance would break the following superseding maintenance packages. Uninstall the superseding maintenance packages first: list_of_superseding_maintenance_packages
• This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the package that you are attempting to uninstall: list_of_dependent_maintenance_packages
• This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the APARs you are attempting to uninstall: list_of_dependent_maintenance_packages
• No installation backup packages are available for uninstalling maintenance.

Usage notes

• The file is not a read-only file.
• Edit this file directly with your flat file editor of choice, such as Kate on SLES or WordPad on a Windows platform.
• The file must exist to perform a silent uninstall. The Update installer wizard reads this file to determine uninstall parameters. Provide the fully qualified file path to the backup file.
• Save the copy of the options file in the responsefiles directory for best results.

Example uninstall.txt file

Edit the version of the file that is included in the Update Installer for WebSphere Software ZIP file. The following example is not guaranteed to be an accurate representation of the actual file.

################################################################################
#
# This is the silent install response file for uninstalling maintenance packages
# using the update installer.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, *uncomment* and modify the parameters defined within.
#
# Use the following command line when running the wizard from the update 
# installer directory:
# 
#    update -options responsefiles/uninstall.txt -silent
#
################################################################################


################################################################################
#
# Used to input the maintenance backup package filename to be uninstalled. 
# This is the same filename as the package that was originally installed.
# A maintenance package can only be uninstalled if a backup package exists.
#
# ie. -W backup.package="PQ20029.pak"
#
# Note: If no package is specified, a default of the last installed maintenance 
# package will be used.
#
#-W backup.package=""


################################################################################
#
# Used to modify the product install location that will be updated. 
# This value should be left commented out if the Update Installer is 
# being run from the recommended location
#
# ie. -W product.location="C:\Program Files\WebSphere\AppServer"
#
# Note: If no location is specified, the parent directory to update installer 
# will be used as default
#
#-W product.location=""



################################################################################
#
# Do not edit these values.
#
-W update.type="uninstall"

update command

The update installer program installs and uninstalls interim fixes to update WebSphere software.

Overview

The update command calls the update installer program to install and uninstall interim fixes to update WebSphere software. This topic describes the update installer command and its command-line parameters.

The following descriptions contain reference information about the command.

See Applying service and Uninstalling service for information about using the command.

Command options

The following table list commands for installing and uninstalling interim fixes.

Commands for installing interim fixes

Issue one of the following commands to use the graphical interface:

Issue one of the following commands to use the silent interface:

Commands for uninstalling interim fixes

Issue one of the following commands to uninstall with the graphical interface:

Issue one of the following commands to use the silent interface:

Installing multiple interim fixes

Use a script to issue more than one command. Each command identifies one maintenance package to install. For example:

...
update -W maintenance.package="e:\IBM\WebSphere\AppServer\updateinstaller\maintenance\PQ20028.pak" -silent
update -W maintenance.package="e:\IBM\WebSphere\AppServer\updateinstaller\maintenance\PQ20029.pak" -silent

Logging

The following sections describe logging that occurs when installing and uninstalling service.

Logs created when installing service

If no installation log file exists, refer to the temporary log file in the install_root/logs/update/tmp directory. If all validations pass, the installation occurs.

Then the update installer program creates the install_root/logs/update/maintenance_package.install directory.

Within the directory are the updatelog.txt file, the compressed updatetrace.log.gz file, and the compressed updateconfig.log.gz file. The updateconfig.log.gz file exists only when the installation of service uses the internal configuration manager utility to run ANT scripts.

Logs created when uninstalling service

If no log file exists after uninstalling an interim fix, refer to the temporary log file in the install_root/logs/update/tmp directory. If all validations pass, the uninstall procedure occurs.

Then the update installer program creates the install_root/logs/update/maintenance_package.uninstall directory.

Within the directory are the updatelog.txt file, the compressed updatetrace.log.gz file, and the compressed updateconfig.log.gz file. The updateconfig.log.gz file exists only when the removal of service uses the internal configuration manager utility to run ANT scripts.

Indicators of success

The log file includes an indicator of success:

INSTCONFSUCCESS

The current operation was successful. You do not need to review the log file any further.

INSTCONFPARTIALSUCCESS

The current operation was partially successful. System should still be in a usable state, however some non-critical actions have failed. Consult the log file to determine what has failed and how to recover from the failure, if possible.

INSTCONFFAILED

The current operation failed. The system is no longer in a usable state. Consult the log file for more information.

Appendix A. Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

Appendix B. Trademarks and service marks

For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/).