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

You can use a single instance of the IBM® Update Installer for WebSphere® Software to install interim fixes, fix packs, and refresh packs for Version 6.0.2 Fix Pack 21, Version 6.1, and Version 7.0.

Before you begin

Note: If you previously imported WebSphere Application Server Version 7.0 into Installation Manager, you cannot use Installation Manager to update it. You must use the instructions given in this section and use the Update Installer to install any fixes. After you use the Update Installer to apply maintenance to the base WebSphere Application Server product or the IBM SDK, you must reimport the WebSphere Application Server Version 7.0 installation into Installation Manager.
Learn about important prerequisites, permissions, and precautions before installing a maintenance package by reviewing the topic Installing maintenance packages overview.
New feature New feature: The Update Installer offers several features:
  • The Version 7.0 Update Installer supports multiple releases. The Version 7.0 Update Installer is also compatible with earlier releases; it works with Version 6.0.2 Fix Pack 21 and newer maintenance and any maintenance for Version 6.1.0.x and Version 7.0 releases. This allows a single instance of the Update Installer to apply maintenance to more than one version of the application server. For Version 6.0.2 Fix Pack 19 and previous releases, apply maintenance with the Version 6.0.2.x Update Installer.
  • It 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.
  • It can update language packs to add new languages.
  • It supports updates for DMZ Secure Proxy Server.
  • It is available in .tar format on Unix operating systems.
  • When installing it, you can choose to create Start menu shortcuts.
newfeat
Avoid trouble Avoid trouble: Fix packs that include updates to the Software Development Kit (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.gotcha

About this task

See Uninstalling maintenance packages, interim fixes, fix packs, and refresh packs for a description of how to roll back a maintenance package.

Avoid trouble Avoid trouble: You cannot use the update commands from the same Update Installer to update multiple installations or products at the same time.gotcha

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.
    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 the product that you intend to update.

    If you already have the product 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 unpack the *.pak file. If your 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. Stop application servers.

    Run the stopServer command on all WebSphere Application Server profiles.

  5. Stop all Java processes that use the IBM Software Developer Kit (SDK) that the WebSphere Application Server 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 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:
    • All Java Virtual Machines (JVMs)
    • WebSphere Application Server processes:
      WebSphere Application Server processes include:
      • Application server processes
      • The nodeagent process on an application server 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 WebSphere Application Server-related Java process runs, the product might not continue to run successfully.

  6. 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.
  7. Change directories to the updi_root directory.
  8. 8. Choose to install the product in silent or graphical user interface mode.

    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.

    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 following tables show options that are available when using the update command.

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

    This table contains commands for the graphical user 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 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.

    Table 2. Update Installer command for installing in silent mode.

    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.

  9. Optional: Re-apply any ownership and permissions changes that were made after the product was originally installed.

    You must complete this step if the user owner, group owner, or permissions of any product files has changed prior to the installation or removal of a fix pack.

    In some situations, the user ownership, group ownership, and permissions of the product files, including files that are associated with profiles, might have been changed after the product was installed. For example, you might have installed the product as the root user, and then afterward changed the file ownership to a non-root user. Typically, the a command, such as chown or chmod is used to change the ownership of these files.

    When a fix pack is either installed or uninstalled, the UpdateInstaller might change the ownership and permissions of the product files, including the files that are associated with profiles. The changed ownership and permissions might interfere with starting application servers or using certain features.

    To prevent this interference, you must re-apply any ownership and permissions changes that were made after the product was originally installed. For example, if the ownership was changed from root user to non-root user, and then the UpdateInstaller is run as root user to install a fix pack, the file ownership needs to be changed back to non-root user after the fix pack is installed or removed.

    Avoid trouble Avoid trouble: When using the chown or chmod commands, you must apply the changes to * instead of *.*. Using *.*does not sufficiently update all product files.gotcha

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.

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 Uninstalling fix packs, interim fixes, interim features, test fixes, or fix packs delivered as a CIP slip install for more information.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 2:29:34 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=tins_ptfLevels
File name: tins_ptfLevels.html