Install maintenance packages

 

+

Search Tips   |   Advanced Search

 

 

Overview

This topic describes how to use the IBM Update Installer for WebSphere Software to install...

The Update Installer is also known as...

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.

 

User Accounts

When administrative security is enabled, supply the administrative user ID and password before running the Update Installer.

Use the Update Installer program from the same installer ID that installed the product being updated. Otherwise, file ownership mismatches might require correction by the root user.

Alternate user accounts must have read/write access to...

updi_root/logs

...and have read/write/execute access to the WAS product target location where the maintenance package is to be applied.

For AIX systems, if a non-root user launches the Update Installer program, that user account must be able to run the slibclean command; otherwise, a root user must run the slibclean command whenever the Update Installer program is used.

Verify no processes from any users are locking any files in the target location where a maintenance package is to be installed. On *nix boxes you can use the lsof command

 

Installation Procedure

  1. Install the Update Installer for WebSphere Software

  2. Download the...

    ...from the Support Web site...

    www-1.ibm.com/support/docview.wss?uid=swg27004980

    ...into...

    updi_root/maintenance

  3. Use the Update Installer to install the maintenance files.

    The Update Installer creates a backup file in...

    app_server_root/properties/version/nif/backup

    IBM does not support restoring a backup file that you have modified.

 

Update existing profiles in WAS products

The Update Installer updates the core product files in a WAS 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 the 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.

 

View the fix level of the product

Use the versionInfo command and the historyInfo command in the bin directory of the installation root directory to display the exact fix and version level of the product. However, do not use either command while installing or uninstalling a maintenance package.

 

Update cluster members

Apply the same maintenance packages to all of the WAS 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 not function properly.

Information required when installing a maintenance package.

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.

Identify the installation root directory for one of the following products:

  • IBM WAS
  • IBM WAS - Express
  • Embedded version of the IBM WAS - Express
  • IBM WAS ND
  • IBM WebSphere Extended Deployment
  • IBM Application Client for WAS
  • IBM WebSphere Business Integration Server Foundation
  • Web server plug-ins for WAS

Download, unpack, and install the Update Installer for WebSphere Software. Or install the Update Installer that is on the 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.

See Update command - known problems and workarounds and the release notes for your product for the latest information about the Update Installer.

 

Overview

The following procedure describes how to install a maintenance package. See Uninstall maintenance packages for a description of how to roll back a maintenance package.

 

Procedure

  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,...

    umask 022

  2. Install the product that you intend to update.

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

     

  3. Optional: Install a new version of the Update Installer.

    Back up and uninstall any older copy of the Update Installer before downloading and installing the current Update Installer. To use a newer version of the Update Installer, first remove the older version.

    1. Back up any files and subdirectories in...

      updi_root/maintenance

    2. Uninstall the older version of the Update Installer using the program under...

      updi_root/uninstall

    3. Download, unpack, and install the Update Installer for WebSphere Software; or install the Update Installer that is on the supplements disc.

  4. 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:

    Do not attempt to unzip or unpack the *.pak file.

  5. [Windows] Verify all appservers are stopped.

    Run the stopServer command on all WebSphere Application Server profiles.

  6. Stop all Java processes that use the IBM Software Developer Kit (SDK) that the WAS product provides.

    Before installing or uninstalling interim fixes, fix packs, and refresh packs on a machine, stop all Java processes on the machine that use the IBM SDK, Java Technology Edition that WAS provides. Stop all WAS-related Java processes running on the system where you are using the Update Installer program. For example, Java processes can include:

    • All JVMs

    • WAS processes:WAS processes include:

      • Application server processes

      • The nodeagent process on an appserver node when the node is federated into a deployment manager cell

      • The dmgr process for the deployment manager server

    • IBM HTTP Server processes

    • Web server processes that use a plug-in that you 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 you install an interim fix while a WAS-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 WAS-related Java processes before using the Update Installer for WebSphere software.

  7. Verify that the following prerequisite conditions are met:

    • All of the product hardware and software prerequisites exist.

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

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

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

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

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

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

    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 runs as a background process and does not display the graphical user interface when running in silent mode:

    [Windows]

    update.sh -silent -options responsefile
    
    [AIX] [HP-UX] [Linux] [Solaris]

    ./update.sh -silent -options responsefile
    

    Or, issue the update command to start the graphical user interface:

    [Windows]

    update.sh
    
    [AIX] [HP-UX] [Linux] [Solaris]

    ./update.sh
    

    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.

    Update installer commands for installing with the graphical interface:

    • update.sh

      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.sh -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.sh -W maintenance.package="/AppServer/updateinstaller/maintenance\PQ20029.pak"

      Overrides the name of the maintenance package to apply.

    • update.sh -W product.location="/AppServer"

      Overrides the location of the WebSphere software to update.

    • update.sh -W product.location="/AppServer" -W maintenance.package="/AppServer/updateinstaller/maintenance/PQ20029.pak"

      Overrides the location of the WebSphere software to update and the name of the maintenance package to apply.

    • update.sh -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:

Update Installer command for installing in silent mode

Command example Type of installation Description
update.sh -silent -options "responsefiles/file_name" Silent mode with an options file 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 your WebSphere software.



install.txt
Installing the Update Installer for WebSphere Software
Uninstall the Update Installer for WebSphere Software
Updating the Update Installer for WebSphere Software
Uninstall maintenance packages
update command
Update command - known problems and workarounds

 

Related Reference

Product version information

 

Related information