This topic describes how to use the IBM Update Installer for WebSphere Software to install interim fixes, fix packs, and refresh packs. The Update Installer for WebSphere Software is also known as the update installer program, the UpdateInstaller program, and the Update installation wizard.
Before you begin
Use the proper authorizations to successfully 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 package that you downloaded to the default maintenance 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 install_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 profiles directory to replace the changed profile.
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
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:
|
Download and unpack the Update Installer for WebSphere Software within each set of core
product files that you intend to update. The Update Installer application selects 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. |
Why and when to perform this task
The following procedure describes how to install a maintenance package. See Uninstalling service for a description of how to remove a maintenance package.
Steps for this task
You have very likely already installed the software that you are now updating. But if not, install the software now.
Unpacking the file creates 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 download and use the latest version of the Update Installer wizard when installing an interim fix.
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, such as the process created when server1 is running.
WebSphere Application Server processes include application server processes, such as the process created when server1 is running.
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 Update Installer for WebSphere software requires a valid Java run time that is provided with WebSphere software. If the update installer program cannot locate a valid IBM or Sun SDK, such as the one shipped with WebSphere Application Server products, the update installer cannot install maintenance packages.
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 method of setting the JAVA_HOME environment variable is using the setupCmdLine script provided with the WebSphere Application Server product. In some cases, failure to run setupCmdLine can result in the update installer program matching an SDK in an order that is different than the order described.
./update -is:javahome install_root/java
To use the setupCmdLine script to set the JAVA_HOME variable, perform the following procedure that is appropriate for your operating system:
See the following technote for more information, Using the setupCmdLine script to set JAVA_HOME before running the Update Installer for WebSphere software.
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.
Use the following command syntax to install the last maintenance package that you downloaded. The Update Installer wizard runs as a background process and does not display the graphical user interface when running in silent mode:
update -silent
Or, issue the update command to start the graphical user interface:
update
Command example | Type of installation | Description |
---|---|---|
update | Graphical interface mode | 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 -W prereqsfailedpanelInstallWizardBean.active= "false" | Graphical interface mode that bypasses prerequisites checking | Initializes the maintenance package field with the name of the maintenance package 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. |
Command example | Type of installation | Description |
---|---|---|
update -silent | Silent mode | Installs the maintenance package 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 maintenance package 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 maintenance package
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. |
Result
This procedure results in installing maintenance packages to update WebSphere software.
What to do next
After installing an maintenance package, continue to use your WebSphere software.
Related reference
Product version information