Install maintenance packages, interim fixes, fix packs, and refresh packs


 

+

Search Tips   |   Advanced Search

 

The WAS v7 Update Installer works with...

For V6.0.2.19 and previous releases, apply maintenance with the V6.0.2.x Update Installer.

The Update Installer...

Fix packs that include updates to the SDK might overwrite unrestricted policy files. Back up unrestricted policy files before you apply a fix pack and reapply these files after the fix pack is applied.

The following procedure describes how to install a maintenance package. package.

  1. Log on as root on an operating system such as AIX or Linux, or log on as a member of the administrator group on a Windows system.

    [AIX] [HP-UX] [Linux] [Solaris]

    In addition, verify that the umask setting is 022. To verify the umask setting, issue the following command:

    umask
    To set the umask setting to 022, issue the following command:

    umask 022

  2. Install WAS that you intend to update.

    If we already have WAS installed, proceed to the next step.

  3. Download the maintenance package *.pak file from the Support Web site into the maintenance directory.

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

    Tip: Do not attempt to unzip or unpack the *.pak file. If the browser changes the download package from *.pak file to *.zip, do not attempt to unzip the package. Instead, rename the file to *.pak and proceed to the next step without unzipping the renamed *.pak file.

  4. (Windows) Make sure that all appservers are stopped.

    Run the stopServer command on all WAS profiles.

  5. Stop all Java processes that use the IBM Software Developer Kit (SDK) that WAS v7 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 WAS provides. Stop all WAS-related Java processes that are running on the system where we are using the Update Installer program. For example, Java processes can include:

    • All JVMs

    • WAS processes:

      • Application Server processes
      • The nodeagent process on an appserver node when the node is federated into a dmgr cell
      • The dmgr process for the dmgr server

    • IBM HTTP Server processes

    • Web server processes that use a plug-in that we are updating

    • First steps consoles

    • Installation verification test (IVT) processes

    • The Profile Management Tool

    • Other InstallShield for Multiplatforms (ISMP) installation programs

    • InstallShield for Multiplatforms uninstall programs

    • The IBM Rational Application Developer Agent Controller

    Stop all Java processes if necessary. If we install an interim fix while a WAS-related Java process runs, IBM does not guarantee that WAS can continue to run successfully, or without error.

    See the following technote for more information, Stop all WAS-related Java processes before using the Update Installer for WebSphere software.

  6. Verify that the following prerequisite conditions are met:

    • All of WAS hardware and software prerequisites exist.

      The official statement of supported hardware and software is on the Supported hardware and software Web site.

    • The WebSphere software that we are updating is correctly installed and is not corrupt.

    • The WebSphere SDK, Java technology edition is not corrupt.

    • The user is root on a system such as AIX or Linux or a member of the administrator group on a Windows system.

  7. Change directories to the updi_root directory and use the update command to install the maintenance package.

    Install the maintenance package on the dmgr node before installing the maintenance package on each appserver node that you intend to update.

    See on root versus non-root for installing maintenance with the Update Installer, refer to Use root or non-root when installing with the Update Installer.

    The Update Installer wizard runs in two modes: the silent mode, as a background process, and the regular mode, using the GUI.

     Silent mode

    The Update Installer wizard does not display the graphical user interface when running in silent mode.

    The following commands initiate a silent installation:

    (Windows)

    update.bat -silent -options responsefile

    update.exe -silent -options responsefile

    [AIX] [HP-UX] [Linux] [Solaris]

    ./update.sh -silent -options responsefile
    There are three types of silent installation procedures:

    1. Install a fix pack or refresh pack. Refer to Installing fix packs silently for more information.

    2. Install an interim fix or interim feature or test fix. Refer to Install an interim fix, interim feature, or test fix with silent install for more information.

    3. Install multiple maintenance packs. Refer to Installing multiple maintenance packs silently for more information.

     Graphical user interface mode

    Issue the update command to start the GUI:

    (Windows)

    update.bat

    update.exe

    [AIX] [HP-UX] [Linux] [Solaris]

    ./update.sh
    There are three types of installation procedures that use the graphical user interface:

    1. Install a fix pack or refresh pack. Refer to Installing fix packs using the GUI for more information.

    2. Install an interim fix, interim feature, or test fix. Refer to Install interim fixes, interim features, or test fixes using the GUI for more information.

    3. Install multiple maintenance packs. Refer to Installing multiple maintenance packs using the GUI for more information.

    The procedure for uninstalling fix packs, interim fixes, and interim features is similar. 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 Uninstall fix packs, interim fixes, interim features or test fixes using the GUI for more information.

    The following tables show options that are available when using the update command. The first table contains commands for the GUI and the second table contains commands for silent mode.


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

    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 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 GUI:

    Command example Description
    update.bat -silent -options "responsefiles/file_name" Overrides all default values with values specified in the options response file.

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

 

Results

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

 

What to do next

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 the WebSphere software.


Subtopics

install.txt
Install the Update Installer for WebSphere Software
Uninstall the Update Installer for WebSphere Software
Updating the Update Installer for WebSphere Software
Uninstall maintenance packages, interim fixes, fix packs, and refresh packs
Install fix packs silently
Install an interim fix, interim feature, or test fix with silent install
Install multiple maintenance packs silently
Install fix packs using the GUI
Install interim fixes, interim features, or test fixes using the GUI
Install multiple maintenance packs using the GUI
Silently uninstalling fix packs, interim fixes, or test fixes
Uninstall fix packs, interim fixes, interim features or test fixes using the GUI
update
Update command - known problems and workarounds
Use root or non-root when installing with the Update Installer

 

Related

Verifying and setting file permissions
Product version information