update command

The update command is the Update Installer for WebSphere Software program. The Update installer wizard is also known as the Update installation wizard, the update installer program, and the updateInstaller program.

The update installer program installs and uninstalls interim fixes, fix packs, and refresh packs to update WebSphere software.

 

Overview

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 Applying service and Uninstalling service for information about using the command.

Important: See Known problems and workarounds for the update command for information about known problems and workarounds.

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:

Table 1. 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 1. 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.

Commands for uninstalling interim fixes

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

Table 1. 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 1. 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.

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

Automating maintenance operations

Most fix packs and refresh packs include some maintenance for the IBM SDK, Java technology edition in the install_root/java 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 install_root/updateinstaller/java directory

install_root
   /updateinstaller
      /java

To use a script to perform a silent maintenance installation, 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 install_root/updateinstaller directory if the SDK is present.

Issue the following commands from the script:

  1. update -silent [other_options] -W relaunchwizardexecInstallWizardBean.active=false

    For example, use the following command to clone the SDK

    /opt/WebSphere/AppServer/updateinstaller/update \
       -silent \
       -W relaunchwizardexecInstallWizardBean.active=false \
    
    

    Identify the interim fix in the first command if the interim fix is not the last maintenance package that you downloaded. {Omit the Linux and UNIX line-continuation characters (\) when issuing the command on one line.}

  2. update -silent

    The update installer program uses the cloned copy of the SDK in the install_root/updateinstaller 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 \
       -silent -W maintenance.package=\
       "/opt/WebSphere/AppServer/updateinstaller/maintenance/\
       6.0.1.0-WS-WAS-LinuxIA32-RP0000001.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.}

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.