Before using this information, be sure to read the general information under Appendix A. Notices.
Your feedback is important in helping to provide the most accurate and highest quality information.
Be sure to include the document name and number, the WebSphere Application Server version that 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.
You can use a single instance of the IBM(R) Update Installer for WebSphere(R) Software to install interim fixes, fix packs, and refresh packs for Version 6.0.2.21, V6.1, and V7.0.
Learn about important prerequisites, permissions, and precautions before installing a maintenance package by reviewing the topic Installing maintenance packages overview.
The V7.0 Update Installer supports multiple releases. The V7.0 Update Installer is also compatible with earlier releases; it works with V6.0.2.21 and newer maintenance and any maintenance for V6.1.0.x and V7.0 releases. This allows a single instance of the Update Installer to apply maintenance to more than one version of the application server. For V6.0.2.19 and previous releases, apply maintenance with the V6.0.2.x Update Installer.
The Update Installer has a file permission verification feature. This feature saves time and allows you to resolve potential file permission problems for Application Server maintenance before you install it.
The Update Installer can update language packs to add new languages.
The Update Installer supports updates for DMZ Secure Proxy Server.
The Update Installer is available in .tar format on Unix type operating systems.
When installing the Update Installer, you can choose to create or not create start menu shortcuts.
The following procedure describes how to install a maintenance package. See Uninstalling maintenance packages for a description of how to roll back a maintenance package.
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
If you already have the product installed, proceed to the next step.
Download maintenance packages for the Update Installer for WebSphere Software to install from the following IBM Web pages:
Run the stopServer command on all WebSphere Application Server profiles.
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.
Stop all WebSphere Application Server-related Java processes that are running on the system where you are using the Update Installer program. For example, Java processes can include:
WebSphere Application Server processes include:
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.
See the following technote for more information, Stop all WebSphere Application Server-related Java processes before using the Update Installer for WebSphere software.
The official statement of supported hardware and software is on the Supported hardware and software Web site.
Install the maintenance package on the deployment manager node before installing the maintenance package on each application server node that you intend to update.
For more information on root versus non-root for installing maintenance with the Update Installer, refer to Using root or non-root when installing with the Update Installer.
Use the following command syntax to install the last maintenance package that you downloaded. The Update Installer wizard runs in two modes: the silent mode, as a background process, and the regular mode, using the graphical user interface.
The Update Installer wizard does not display the graphical user interface when running in silent mode:
update.bat -silent -options responsefile
update.exe -silent -options responsefile
./update.sh -silent -options responsefile
There are three types of silent installation procedures that can be used with the Feature Pack for Web Servers. They are listed below:
The procedure using the Feature Pack for Web Services to uninstalling a fix pack, or interim fix, or interim feature are similar when using the silent uninstall.
Or, issue the update command to start the graphical user interface:
update.bat
update.exe
./update.sh
There are three types of installation procedures that use the installation wizard graphical user interface with the Feature Pack for Web Services:
The procedure for uninstalling is similar for fix packs, interim fixes, and interim features. Uninstall only one fix pack, interim fix, or interim feature at a time. To find out more about uninstalling a fix pack or refresh pack, refer to Uninstalling a fix pack, interim fix, interim feature or test fix using the graphic user interface for more information.
The following tables show options that are available when using the update command.
The commands in the first table each start the Update Installer wizard with a graphical user interface. The command in the second table causes the Update Installer wizard to run in silent mode.
Command example | Description |
---|---|
update.bat | Initializes the maintenance package field with the name
of the maintenance package that has the most recent date stamp and time stamp.
Accept all of the default values to install the maintenance package with the most recent time stamp. |
update.bat -options "responsefiles/file_name" | Overrides all graphical interface 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. |
update.bat -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak" | Overrides the name of the maintenance package to apply. |
update.bat -W product.location="e: \IBM\WebSphere\AppServer" | Overrides the location of the WebSphere software to update. |
update.bat -W product.location="e: \IBM\WebSphere\AppServer" -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak" | Overrides the location of the WebSphere software to update and the name of the maintenance package to apply. |
update.bat -OPT disableDiskSpaceCheck=true | Overrides the prerequisite check for disk space. |
Specify an appropriate JOBQ parameter value to have the job run in a different subsystem. Verify that the storage pool that the job runs in has as much memory as possible.
The command in the following table starts the Update Installer wizard in silent mode without the graphical user interface:
Command example | Description |
---|---|
update.bat -silent -options "responsefiles/file_name" | 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. |
This procedure results in installing maintenance packages to update WebSphere software.
Click Relaunch on the last panel of the Update Installer to begin installing a second maintenance package.
After installing all maintenance packages, continue to use your WebSphere software.
Before you install maintenance to your WebSphere product, you should be familiar with the following important considerations and precautions.
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.
Permissions can only be given to one user account. To install and launch the Update Installer, use the same user account that installed WebSphere Application Server, or give permission to another user. If permission is given to a non-root user, then the non-root user should give permission to the root user when finished installing maintenance. If the non-root user does not return permission to the root user, then the root user cannot read or write to the file system.
W -1 mkdirs failed for: file:/home/nonroot/IBM/WebSphere/UpdateInstaller1/logs/tmp1 java.io.IOException: mkdirs failed for: file:/home/nonroot/IBM/WebSphere/UpdateInstaller1/logs/tmp1 at com.ibm.ws.install.ni.framework.io.DiskFileSystem.mkdirs(DiskFileSystem.java:369) at com.ibm.ws.install.ni.framework.io.FileSystemEntry.mkdirs(FileSystemEntry.java:399) at com.ibm.ws.install.ni.framework.logging.TextLoggingBridge.createLogger(TextLoggingBridge.java:159) at com.ibm.ws.install.ni.framework.logging.TextLoggingBridge.init(TextLoggingBridge.java:45) at com.ibm.ws.install.ni.framework.plugin.NIFPlugin.createPlugin(NIFPlugin.java:782)
The Update Installer updates the core product files in a WebSphere Application Server product. Service in a maintenance package might update the following files in the installation root directory:
Some maintenance packages provide required service for existing profiles in addition to service for the core product files. Each maintenance package that has profile maintenance provides a script that changes the profile. The Update Installer prompts you to back up your configuration when installing a maintenance package that has required maintenance for profiles.
Some maintenance packages provide optional service for existing profiles. The readme file for the maintenance package describes whether the maintenance package contains optional service for existing profiles. If so, the readme file describes how to use the script provided with the maintenance package.
Use the backupConfig command to back up the configuration of each profile that the maintenance package can update. Or archive the app_server_root/profiles directory to back up all of the profiles at once.
If you uninstall a maintenance package, the Update Installer does not uninstall the maintenance package from profiles. The reason for not removing the maintenance is that you might have configured the profile after installing the maintenance. To restore an original profile, use the restoreConfig command or copy the profile from the archived profile_root directory to replace the changed profile.
Apply the same maintenance packages to all of the WebSphere Application Server installations 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 function improperly.
The graphical interface requires you to supply the following information:
Field | Valid values | Description |
---|---|---|
File path of the installation
root directory of the WebSphere product or component.
Installation root directory of the Update Installer. See updi_root for more information. |
Identify the installation root directory for one of
the following products:
|
Download, unpack, and install the Update Installer for WebSphere Software. Or install the Update Installer that is on the WebSphere Application Server supplements disc. Install the Update Installer into each component that you intend to update. The Update Installer application updates the product in its parent directory by default. |
File name of the maintenance package to install. | Select a maintenance package to install from the maintenance directory. | The default maintenance package is the package with the latest date stamp and time stamp. |
The Update Installer for WebSphere Software can use a response file to install maintenance packages from a command line interface.
The Update Installer for WebSphere Software reads the response file to determine installation choices. The Update Installer installs the maintenance package in silent mode instead of displaying a graphical user interface.
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 sample response file is named install.txt. The file is in the updi_root/responsefiles directory after you install the Update Installer for WebSphere Software into the installation root directory of the WebSphere software product.
The response file supplies the values to the Update installer when installing silently. The Update Installer reads the response file to determine responses and does not display the graphical user interface.
The following command uses a copy of the response file named myresponsefile.txt to provide installation option responses during a silent installation:
./update.sh -options "responsefiles/myresponsefile.txt" -silent
If you do not use the -silent option, the wizard uses the response file to provide initial values for the graphical interface:
./update.sh -options "responsefiles/myresponsefile.txt"
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 app_server_root/logs/update/tmp directory.
Note: If no package is specified, maintenance packages from the default folder (such as, UpdateInstaller_HOME\maintenance) are installed.
/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PQ20029.pak
/opt/IBM/WebSphere/AppServer2
Edit the version of the response 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 # # Please enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # This section describes how to apply a maintenance package using the full filename specifications to be installed. # There are three ways you can specify installing a maintenance package. They are the following: # (Use the examples below and edit where appropriate.) # # 1. Specify a single maintenance package full filename to be installed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak" # # 2. Specify a multiple maintenance package full filename to be installed. # - Use a semicolon to separate the full filename specifications. # - Update Installer will install the latest applicable maintenance in the order listed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak;/ # QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20030.pak";" # # 3. Specify a full folder name that contains the maintenance packages. # Update Installer will install the latest applicable maintenance in the order listed in the folder. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance" # # Notes: If no package is specified, maintenance packages from the default folder (such as, UpdateInstaller_HOME\maintenance ) # will be installed. # #-W maintenance.package="" ################################################################################ # # Prerequisite Checking # # The update installer checks the system for prerequisites by default. # # Uncomment the following option to notify the installer to continue with # the update and log the warnings even though prerequisite checking # failed. # #-OPT disableNonBlockingPrereqChecking="true" ################################################################################ # # Used to input the product install location that will be updated. # # ie. -W product.location="/QIBM/ProdData/WebSphere/AppServer/V61/Express" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="" ################################################################################ # # Do not edit these values. # -W update.type="install"
If you would like to install maintenance without the graphical user interface, you can use the Update Installer for WebSphere Software to install a fix pack in silent mode.
Ensure that the most recent version of the Update Installer is installed on a target system locally.
For example:
update.bat -silent -options "responsefiles\file_name"
update.exe -silent -options "responsefiles\file_name"
./update.sh -silent -options "responsefiles/file_name"
One of the following results appears in the log:
The following example is a sample response file used in a silent installation:
################################################################################ # # 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 # # Please enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # This section describes how to apply a maintenance package using the full filename specifications to be installed. # There are three ways you can specify installing a maintenance package. They are the following: # (Use the examples below and edit where appropriate.) # # 1. Specify a single maintenance package full filename to be installed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak" # # 2. Specify a multiple maintenance package full filename to be installed. # - Use a semicolon to separate the full filename specifications. # - Update Installer will install the latest applicable maintenance in the order listed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak;/ # QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20030.pak";" # # 3. Specify a full folder name that contains the maintenance packages. # Update Installer will install the latest applicable maintenance in the order listed in the folder. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance" # # Notes: If no package is specified, maintenance packages from the default folder (such as, # UpdateInstaller_HOME\maintenance ) # will be installed. # #-W maintenance.package= ################################################################################ # # Prerequisite Checking # # The update installer checks the system for prerequisites by default. # # Uncomment the following option to notify the installer to continue with # the update and log the warnings even though prerequisite checking # failed. # #-OPT disableNonBlockingPrereqChecking="true" ################################################################################ # # Used to input the product install location that will be updated. # # ie. -W product.location="/QIBM/ProdData/WebSphere/AppServer/V61/Express" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="" ################################################################################ # # Do not edit these values. # -W update.type="install"
You can use the Update Installer for WebSphere Software to install an interim fix, interim feature, or test fix using the silent installation option.
Ensure that the most recent version of the Update Installer is installed on a target system locally.
The following steps lead you through the process of applying maintenance to an interim fix, interim feature, or test fix pack using the silent mode.
In the response file, point to the interim fix, interim feature, or test fix directory that contains the package to be installed.
For example:
update.bat -silent -options "responsefiles\file_name"
update.exe -silent -options "responsefiles\file_name"
./update.sh -silent -options "responsefiles/file_name"
You can find one of the following results in the log:
The following is a sample of a response file used by the Update Installer to install an interim fix, interim feature, or test fix using the silent installer.
################################################################################ # # 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 # # Please enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # This section describes how to apply a maintenance package using the full filename specifications to be installed. # There are three ways you can specify installing a maintenance package. They are the following: # (Use the examples below and edit where appropriate.) # # 1. Specify a single maintenance package full filename to be installed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak" # # 2. Specify a multiple maintenance package full filename to be installed. # - Use a semicolon to separate the full filename specifications. # - Update Installer will install the latest applicable maintenance in the order listed. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak;/ # QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20030.pak";" # # 3. Specify a full folder name that contains the maintenance packages. # Update Installer will install the latest applicable maintenance in the order listed in the folder. # # For example: # -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance" # # Notes: If no package is specified, maintenance packages from the default folder (such as, # UpdateInstaller_HOME\maintenance ) # will be installed. # #-W maintenance.package= ################################################################################ # # Prerequisite Checking # # The update installer checks the system for prerequisites by default. # # Uncomment the following option to notify the installer to continue with # the update and log the warnings even though prerequisite checking # failed. # #-OPT disableNonBlockingPrereqChecking="true" ################################################################################ # # Used to input the product install location that will be updated. # # ie. -W product.location="/QIBM/ProdData/WebSphere/AppServer/V61/Express" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="" ################################################################################ # # Do not edit these values. # -W update.type="install"
This topic describes how to use the Update Installer for WebSphere Software to install multiple maintenance packages using the silent install option. This feature can install maintenance for WebSphere Application Server and all stack products installed in the same WebSphere Application Server home directory.
Ensure that the most recent version of the Update Installer is installed on a target system locally.
The Update Installer is capable of automatically selecting the recommended maintenance for a product stack and determining the appropriate installation sort order of the maintenance packages. For example, if multiple feature packs are both installed and there is a recommended fix pack and interim fix for each product, the Update Installer can determine if this maintenance is applicable and install them in the correct order. The following steps lead you through the process of installing multiple maintenance packages using the silent mode.
There are two options for installing the fix pack:
For example:
update.bat -silent -options "responsefiles\file_name"
update.exe -silent -options "responsefiles\file_name"
./update.sh -silent -options "responsefiles/file_name"
One of the following results will appear in the log.
The following is a sample response file used by the Update Installer to install multiple maintenance packages using the silent installer.
################################################################################ # # 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 # # Please enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # This section describes how to apply a maintenance package using the full # filename specifications to be installed. # There are three ways you can specify installing a maintenance package. # They are the following: # (Use the examples below and edit where appropriate.) # # 1. Specify a single maintenance package full filename to be installed. # # For example: # -W maintenance.package="C:\Program Files\IBM\WebSphere\AppServer\UpdateInstaller\ # maintenance\PQ20029.pak" # # 2. Specify a multiple maintenance package full filename to be installed. # - Use a semicolon to separate the full filename specifications. # - Update Installer will install the latest applicable maintenance in the order listed. # # For example: # -W maintenance.package="C:\maintenance\PQ20029.pak;C:\maintenance\PK31008.pak;D:\ # 6.1.0-WS-WAS-WinX32-FP0000001.pak" # # 3. Specify a full folder name that contains the maintenance packages. # Update Installer will install the latest applicable maintenance in the order listed in the folder. # # For example: # -W maintenance.package="D:\UpdateInstaller\maintenance" # # Notes: If no package is specified, maintenance packages from the default folder (such as, # UpdateInstaller_HOME/maintenance ) # will be installed. # -W maintenance.package="D:\UpdateInstaller\maintenance\6.1.0-WS-WAS-WinX32-FP0000001.pak" ################################################################################ # # Prerequisite Checking # # The update installer checks the system for prerequisites by default. # # Uncomment the following option to notify the installer to continue with # the update and log the warnings even though prerequisite checking # failed. # #-OPT disableNonBlockingPrereqChecking="true" ################################################################################ # # Used to input the product install location that will be updated. # # ie. -W product.location="C:\Program Files\IBM\WebSphere\AppServer" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="D:\Program Files\IBM\WebSphere\AppServer" ################################################################################ # # Do not edit these values. # # -W update.type="install"
This topic describes how to install a fix pack using the Update Installer. WebSphere Application Server fix packs contain enabling code to ensure feature packs continue to function when maintenance is applied.
Ensure you have the most recent version of the Update Installer installed locally on a target system.
Follow these steps to install a maintenance fix pack:
For example:
update.bat
update.exe
./update.sh
For a list of the recommended fixes for WebSphere Application Server, refer to the support Web site located at the following location: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980#ver61
When you install a fix pack, certain logic is used to determine which packages are selected for the install. To find out more, refer to Logic that the Update Installer uses for system recommended installations.
You can choose from the following options when installing a fix pack:
If a maintenance package is grayed out with the designation Not applicable on the selection panel, you can review the logs in the updi_root/logs/latest_temp_folder to find out why the maintenance package is not appropriate for installation.
You can find the following results in the log:
When you select the Recommended update option, the following logic is used by the Update Installer for WebSphere Software to install an update.
If you are using the Update Installer with the graphical user interface, after you select the Recommended update option on the maintenance panel of the wizard, certain packages may be grayed out for certain reasons. The following describes some of the reasons this occurs.
The package will not be shown or will be grayed out if:
As further maintenance packages are selected, the installer will evaluate prerequisites and dependencies to determine the installation sort order based on the following rules:
You can use the Update Installer to install maintenance packages to a location where a feature pack is installed.
To install a fix pack on a location with a feature pack, follow these steps:
You can use the Update Installer to install maintenance packages without a feature pack installed.
To install a fix pack on a location without a feature pack, follow these steps:
This topic describes how to install an interim fix, interim feature, or test fix using the Update Installer for WebSphere Software.
Ensure that you have installed the most recent version of the Update Installer on a target system locally.
The following steps outline the process of installing an interim fix, interim feature, or test fix pack.
For example:
update.bat
update.exe
./update.sh
The system will automatically determine the appropriate maintenance packages based on the version of the product that is installed.
When you select the interim fix, interim feature, or test fix, certain logic is used to determine which packages are installed. To find out more, refer to Logic that the Update Installer uses for system recommended installations.
If a maintenance package is grayed out with the designation Not applicable on the selection panel, you can review the logs in the updi_root/logs/latest_temp_folder to find out why the maintenance package is not currently appropriate for installation.
One of the following results will appear in the log.
You can install maintenance for WebSphere Application Server and all stack products installed in the same WebSphere Application Server home directory.
Ensure that the most recent version of the Update Installer is installed on a target system locally.
The Update Installer is capable of automatically selecting the recommended maintenance for stack products and determining the appropriate installation sort order of the maintenance packages. For example, if multiple feature packs are installed and there is a recommended fix pack and interim fix for each product, the Update Installer will determine if this maintenance is applicable and install them in the correct order. The following steps lead you through the process of installing multiple maintenance packages.
For example:
update.bat
update.exe
./update.sh
If a maintenance package is grayed out with the designation Not applicable on the selection panel, you can review the logs in updi_root/logs/latest_temp_folder to find out why the maintenance package is not currently appropriate for installation.
After all maintenance packages have been selected and verified to be installable as a group, the installer installs the packages in the following sequence:
Prerequisite checking continues to apply as each maintenance package is installed. Any failure that is detected stops the install flow. The message is displayed and you can find details in the installation logs covering the failure.
One of the following results will appear in the log.
You can use the Update Installer for WebSphere Software to uninstall interim fixes, fix packs, and refresh packs or you can uninstall maintenance in silent mode.
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.
Use the proper authorizations to successfully uninstall product updates. Use the update installer program as the root user on a Linux or UNIX(R) platform, or as the administrator on a Windows platform.
The following descriptions contain reference information about uninstalling interim fixes, fix packs, and refresh packs on WebSphere Application Server products:
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:
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:
|
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. |
The following procedure describes how to uninstall a maintenance package using the graphical user interface and silent mode.
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
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:
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.
Uninstall the interim fix on each application server node in a cell before uninstalling the maintenance package from the deployment manager node.
Issue one of the following commands to uninstall 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. |
Issue the following command to use the silent interface:
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. |
For example:
This procedure results in uninstalling maintenance packages to update WebSphere software.
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 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 levelsDeleting profiles created by a service level that is now rolled back: Profiles should be at a service level that is less than or equal to the service level of the WebSphere Application Server product. For example, if you install a fix pack, create a profile, and then uninstall the fix pack, then you must also delete the profile.
The Update Installer for WebSphere Software can use a response file to uninstall maintenance packages from a command line interface.
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 your uninstallation choices. The Update Installer uninstalls the maintenance package in silent mode, instead of displaying a graphical user interface.
The sample options response file is named uninstall.txt. The file is located in the updi_root/responsefiles directory after you unzip the Update Installer for WebSphere Software into the installation root directory of the WebSphere software product.
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 to provide uninstall option responses during a silent uninstall:
./update.sh -options "responsefiles/myresponsefile.txt" -silent
If you do not use the -silent option, the wizard uses the response file to provide initial values for the graphical interface:
./update.sh -options "responsefiles/myresponsefile.txt"
For example:
In a silent uninstall, response file validation has been coded into the uninstall process. If the validation does not pass, the failure is recorded in the log files in the app_server_root/logs/update/tmp directory.
/opt/properties/version/nif/backup/maintenance_package_to_uninstall
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 if possible. Problems can occur when a mismatch between product SDKs occurs, for example.
Do not use this directive unless absolutely necessary.
/opt/IBM/WebSphere/AppServer2
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 # # Please enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # 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\IBM\WebSphere\AppServer" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="<SPECIFY_PRODUCT_INSTALL_LOCATION_HERE>" ################################################################################ # # Do not edit these values. # -W update.type="uninstall"
Use a response file to uninstall maintenance silently.
Refer to the example response file, located at the bottom of this topic, for more details.
Follow these steps to uninstall maintenance silently:
This is the same filename as the package that was originally installed. A maintenance package can only be uninstalled if a backup package exists, such as, -W backup.package="PQ20029.pak"
For example:
If no package is specified, a default of the last installed maintenance (#) package is used.
To uninstall a maintenance pack using the silent mode, the order of uninstalling needs to be in the reverse order of installing. For example, if you installed maintenance packs A, B, and C in that order, you should uninstall C, B, and then A.
One of the following results will appear in the log.
The following response file demonstrates how to uninstall a fix pack silently.
################################################################################ # # 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 # # Enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # 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. # # For example: -W backup.package="PQ20029.pak" # # Note: If you do not specify a package, then a default of the last installed maintenance # package is used, as the following example demonstrate: # -W backup.package="6.1.0.1-WEBSV-FEP-WinX32-FP000001.pak" ################################################################################ # # 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, as the following example demonstrates: # # For example: -W product.location="C:\Program Files\IBM\WebSphere\AppServer" # # Note: The product install location needs to be specified, and it needs to # be the full path. # -W product.location="D:\IBM\WebSphere\AppServerNonroot3" ################################################################################ # # AIX Non-root user limitation # # The AIX user account running the Update Installer program also must be able to # run the slibclean command; otherwise, a root user must run the slibclean command # before the Update Installer program runs. # # Uncomment the following option to notify the installer that a root user has run # the slibclean command before the Update Installer program runs. # #-OPT rootUserHasRunSlibcleanCommandSuccessfully="true" ################################################################################ # # Do not edit these values. # -W update.type="uninstall"
This topic describes how to use the Update Installer for WebSphere Software to uninstall a fix pack, interim fix, or test fix.
The following steps are required to uninstall maintenance using the graphical user interface.
Select the maintenance package, click Next.
When you uninstall the pack, certain logic is used to determine which maintenance package to uninstall. To find out more, refer to Logic used by the Update Installer for uninstalling.
One of the following results appears in the log:
The Update Installer uses logical procedures when it uninstalls maintenance. The uninstall command works similar to the stack logic in computer science.
Uninstall fix packs in the reverse order that they were installed. The last fix pack installed should be the first one uninstalled.
For example, if maintenance packages A,B,C,D have been installed in that sequence, then the packages should be uninstalled in reverse order: D, C, B, A. This is true if these applications are made up of fix packs, interim fixes or feature packs.
The update command starts the Update Installer for WebSphere Software.
The Update Installer installs and uninstalls interim fixes, fix packs, and refresh packs to update WebSphere software.
The update command calls the update installer program to install and uninstall service 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 Installing maintenance packages and Uninstalling maintenance packages for information about using the command.
The following tables list commands for installing and uninstalling interim fixes.
Issue one of the following commands to use the graphical interface:
Command example | Type of installation | Description |
---|---|---|
![]() update.bat ![]() ![]() ![]() ![]() ./update.sh |
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.bat -options "responsefiles\file_name" ![]() ![]() ![]() ![]() ./update.sh -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.bat -W maintenance.package="e:\IBM\WebSphere \AppServer\updateinstaller\maintenance\PQ20029.pak" ![]() ![]() ![]() ![]() ./update.sh -W maintenance.package="/opt/IBM/WebSphere /AppServer/updateinstaller/maintenance/PQ20029.pak" |
Graphical interface mode | Overrides the name of the maintenance package to apply. |
![]() update.bat -W product.location="e:\IBM\WebSphere \AppServer" ![]() ![]() ![]() ![]() ./update.sh -W product.location="/opt/IBM/WebSphere /AppServer" |
Graphical interface mode | Overrides the location of the WebSphere software to update. |
![]() update.bat -W product.location="e:\IBM\WebSphere \AppServer" -W maintenance.package="e:\IBM\WebSphere \AppServer\updateinstaller\maintenance\PQ20029.pak" ![]() ![]() ![]() ![]() ./update.sh -W product.location="/opt/IBM/WebSphere" -W maintenance.package="/opt/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. |
![]() update.bat -OPT disableDiskSpaceCheck=true ![]() ![]() ![]() ![]() ./update.sh -OPT disableDiskSpaceCheck=true |
Graphical interface mode | Overrides the prerequisite check for disk space. |
Issue the following command to use the silent interface:
Command example | Type of installation | Description |
---|---|---|
![]() update.bat -silent -options "responsefiles\file_name" ![]() ![]() ![]() ![]() ./update.sh -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.
Always use a response file that is based on the response file under updi_root/responsefiles. |
Issue one of the following commands to uninstall with the graphical interface:
Command example | Description |
---|---|
![]() update.bat -W update.type="uninstall" ![]() ![]() ![]() ![]() ./update.sh -W update.type="uninstall" |
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.bat -W product.location="e:\IBM\WebSphere\AppServer" -W update.type="uninstall" ![]() ![]() ![]() ![]() ./update.sh -W product.location="/opt/IBM/WebSphere/AppServer" -W update.type="uninstall" |
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.bat -W backup.package="PQ20029.pak" -W update.type="uninstall" ![]() ![]() ![]() ![]() ./update.sh -W backup.package="PQ20029.pak" -W update.type="uninstall" |
Overrides the interim fix 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" ![]() ![]() ![]() ![]() ./update.sh -W product.location="/opt/IBM/WebSphere/AppServer" -W backup.package="PQ20029.pak" -W update.type="uninstall" |
Overrides the location of the WebSphere software to update and the name of the maintenance package to uninstall. |
![]() update.bat -options "responsefiles\file_name" ![]() ![]() ![]() ![]() ./update.sh -options "responsefiles/file_name" |
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 the following command to use the silent interface:
Command example | Type of installation | Description |
---|---|---|
![]() update.bat -silent -options "responsefiles\file_name" ![]() ![]() ![]() ![]() ./update.sh -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.
Always use a response file that is based on the response file under updi_root/responsefiles. |
Use a script to issue more than one command. Each command identifies one maintenance package to install.
... ./update.sh -W maintenance.package=/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PK20028.pak -silent ./update.sh -W maintenance.package=/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PK20029.pak -silent
If any maintenance package contains service for the IBM Software Developer Kit (SDK), the resulting asynchronous return to the script causes multiple instances of the Update Installer to run, which is not allowed. Use the following procedure to avoid the problem:
For example:
mkdir /opt/IBM/WebSphere/AppServer/updateinstaller/java
The command creates the same directory for the SDK that the Update Installer creates when it clones the SDK automatically.
Copy the contents of the app_server_root/java/jre directory to the updi_root/java directory.
For example, the command for a Linux system might resemble the following example:
cp -rf /opt/IBM/WebSphere/AppServer/java/jre/* --target-directory='/opt/IBM/WebSphere/AppServer/updateinstaller/java'
... ./update.sh -is:javahome /opt/IBM/WebSphere/AppServer/updateinstaller/java -W maintenance.package=/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PK20028.pak -silent ./update.sh -is:javahome /opt/IBM/WebSphere/AppServer/updateinstaller/java -W maintenance.package=/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PK20029.pak -silent
See the UPDI: Control returns prematurely to the command line when the Update Installer rolls back an updated IBM Software Development Kit (SDK) technote for more information about asynchronous operations when the Update Installer is cloning the SDK.
The InstallShield for Multiplatforms (ISMP) launcher program returns control to the command line or calling BAT script right away on Windows systems.
If a BAT script has the following two lines, the second line runs before the Update Installer has completed the first line.
"C:\IBM\WebSphere\AppServer60\updateinstaller\update" -W maintenance.package="C:\IBM\WebSphere\AppServer\updateinstaller\maintenance\PK20028.pak" -silent "C:\IBM\WebSphere\AppServer60\updateinstaller\update" -W maintenance.package="C:\IBM\WebSphere\AppServer\updateinstaller\maintenance\PK20029.pak" -silent
The resulting asynchronous return to the script causes multiple instances of the Update Installer to run, which is not allowed. Use the following procedure to avoid the problem:
Copy the contents of the app_server_root\java\jre directory to the updi_root\java directory, which is the default location when the Update Installer clones the SDK automatically.
For example, use the following command when the installation root directory is the C:\IBM\WebSphere\AppServer60\ directory.
xcopy C:\IBM\WebSphere\AppServer60\java\jre\*.* C:\IBM\WebSphere\AppServer60\updateinstaller\java\*.* /S
"C:\IBM\WebSphere\AppServer60\updateinstaller\java\bin\java.exe" -cp update.jar -Xms48m -Xmx384m run -W maintenance.package="C:\IBM\WebSphere\AppServer60\updateinstaller\maintenance\PK20028.pak" -silent "C:\IBM\WebSphere\AppServer60\updateinstaller\java\bin\java.exe" -cp update.jar -Xms48m -Xmx384m run -W maintenance.package="C:\IBM\WebSphere\AppServer60\updateinstaller\maintenance\PK20029.pak" -silent
The -Xms48m parameter and the -Xmx384m parameter are the minimum heap size and the maximum heap size, respectively.
The reworked batch file avoids the ISMP asynchronous behavior by invoking the native Java process directly. Additional parameters are allowed at the end of each line, such as the -options parameter.
Most fix packs and refresh packs include some maintenance for the IBM SDK, Java technology edition in the app_server_root/java/jre directory. When a refresh pack, fix pack, or interim fix updates the SDK, the Update Installer for WebSphere Software program clones the SDK in the product by starting an ISMP process to copy the SDK to the updi_root/java directory:
updi_root /java
To use a script to perform a silent maintenance installation, you must launch the update installer program twice. The first command clones the SDK only and does not automatically relaunch the update installer program. The second command uses the cloned SDK to update the product and the SDK in the product.
The Update Installer for WebSphere always uses the SDK in the updi_root/java directory if the SDK is present.
Issue the following commands from the script:
The update installer program uses the cloned copy of the SDK in the updi_root directory at the next invocation of the command. For example, use the following command to install the update using the cloned SDK:
/opt/WebSphere/AppServer/updateinstaller/update.sh \ -silent -W maintenance.package=\ "/opt/WebSphere/AppServer/updateinstaller/maintenance/\ 6.0.1.0-WS-WAS-LinuxIA32-RP0000002.pak" \ -W update.type="install" \ -W product.location="/opt/WebSphere/AppServer"
{Omit the Linux and UNIX line-continuation characters (\) when issuing the command on one line.}
The following sections describe logging that occurs when installing and uninstalling service.
If no installation log file exists, refer to the temporary log file in the updi_root/logs/update/tmp directory. If all validations pass, the installation occurs.
Then the update installer program creates the app_server_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.
If no log file exists after uninstalling an interim fix, refer to the temporary log file in the updi_root/logs/update/tmp directory. If all validations pass, the uninstall procedure occurs.
Then the update installer program creates the app_server_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.
The log file includes an indicator of success:
This topic describes known problems and issues associated with the Update Installer for WebSphere Software program.
The update installer program displays its version information in the title bar of the graphical interface. 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 download and use the latest version of the Update installer wizard when installing an interim fix.
The Update Installer can not automatically detect locks on files by remote processes. So you must ensure that all AppServers processes have been stopped for all your profiles, including any remote profiles.
You can use the IBM Update Installer for WebSphere Software to install interim fixes, fix packs, and refresh packs. Learn about important prerequisites, permissions, and precautions before installing a maintenance package.
In order to avoid problems, always use the same user ID for applying maintenance that you used to install WebSphere Application Server, the Update Installer, and any fix packs. If you choose to use a different user, then the maintenance action might not be successful, depending on the ownership and permissions of the files to be updated. If the update action is successful, the file ownerships of the updated files belong to the last user to perform the update and will prevent the original user from performing further updates.
The technote Servers fail to start after applying fixes in version 6.1 describes how to restore file ownership to the original user and allow users to apply future updates.
If WebSphere Application Server is installed by root, and if you try to use a non-root user ID to update WebSphere Application Server, the install will fail because it does not have authority to update the files owned by root. Similarly, if WebSphere Application Server is installed by a non-root user and a different non-root user applies maintenance, the install could fail if the second non-root user ID does not have write authority to those files owned by the first non-root user. In these cases, the user will get a warning message similar to the following:
The current operation must be performed by the same user who owns the existing files. Typically, the file owner is the user who performed the original installation. Switch to the right user, and then run the installer again.
To avoid these potential problems, always use the same user ID for applying maintenance that you used to install the product.
References in product information to app_server_root, profile_root, and other directories infer specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.
The following file paths are default locations. You can install the product and other components or create profiles in any directory where you have write access. Multiple installations of WebSphere Application Server Network Deployment products or components require multiple locations. Default values for installation actions by root and non-root users are given. If no non-root values are specified, then the default directory values are applicable to both root and non-root users.
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
The following list shows the default installation root directories for a CIP where cip_uid is the CIP unique ID generated during creation of the build definition file.
User | Directory |
---|---|
Root |
|
Non-root |
|
Directory |
---|
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
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 the following address:
For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/).