Installing maintenance packages

Use the IBM® Update Installer for the product to install interim fixes, fix packs, and refresh packs. The Update Installer is also known as the Update Installer program, the Update Installer program, and the Update Installation wizard.

Before you begin

Use the correct authorizations to successfully install product updates.

[AIX HP-UX Linux Solaris Windows] Use the Update Installer program as the root user on a platform such as AIX® or Linux® or as the administrator on a Windows® platform.

Important:
  • [AIX HP-UX Linux Solaris Windows] The user account that originally installed the WebSphere® Application Server product to be updated should be used to launch the Installation Wizard to install the Update Installer, and the same user account should be used to launch the Update Installer program to update a product.
    • When a different user account uses the updi_root location, that user account must have reading and running access to that location. It must also have writing access to the updi_root/logs directory and its subdirectory.
    • When a different user account is used to update the target WebSphere Application Server product location, that user account must have full access (reading, writing, and running) to the target location where a maintenance package is to be applied.
  • [AIX] 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.
  • Make sure that no processes from any users are locking any files in the target location where a maintenance package is to be installed.
Attention: 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.

[AIX HP-UX Linux Solaris Windows] 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.

The following descriptions contain reference information about installing interim fixes, fix packs, and refresh packs on WebSphere Application Server products and components:
Overview of the installation procedure
[AIX HP-UX Linux Solaris Windows]
  1. To update an existing copy of the Update Installer, back up and delete the updateinstaller directory of the existing Update Installer before downloading the new ZIP or TAR file into the installation root directory.
  2. Download the most current version of the Update Installer, fix pack, or refresh pack ZIP or TAR file from the Support site into the installation root directory.
  3. Unpack the downloaded file to create the updateinstaller directory and several subdirectories, including the updi_root/maintenance directory.
  4. Interim fix only: Download the interim fix from the Support Web site into the updi_root/maintenance directory.
  5. Use the Update Installer to install the interim fix, fix pack, or refresh pack. The Update Installer creates a backup file in the app_server_root/properties/version/update/backup directory. IBM does not support user modifications to backup files.
Updating existing profiles in WebSphere Application Server products
The Update Installer updates the core product files in a WebSphere Application Server product. Service in a maintenance package might update the following files in the installation root directory:
  • [AIX HP-UX Linux Solaris Windows] The SDK, Java™ technology edition, in the java/jre directory
  • JAR files in the app_server_root/lib directory
  • Scripts in the app_server_root/bin directory
  • Profile templates

[AIX HP-UX Linux Solaris Windows] 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.

[AIX HP-UX Linux Solaris Windows] 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.

[AIX HP-UX Linux Solaris Windows] 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.

[AIX HP-UX Linux Solaris Windows] 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.

Viewing the fix level of the product
Use the versionInfo command and the historyInfo command in the app_server_root/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.
Updating cluster members [AIX HP-UX Linux Solaris Windows]
Apply the same maintenance packages to all of the WebSphere Application Server installations in a cluster. If your applications installed on clusters use DRS Caching, make sure you have the same patches on each cluster member that is at the same WebSphere Application level, for example all v6.x members are at the same level. If these 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.

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.

[AIX HP-UX Linux Solaris Windows] Required information. The graphical interface requires you to supply the following information:
[AIX HP-UX Linux Solaris Windows]
Table 1. Information required when installing a maintenance package
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 WebSphere Application Server
  • IBM WebSphere Application Server - Express™
  • Embedded version of the IBM WebSphere Application Server - Express
  • IBM WebSphere Application Server Network Deployment
  • IBM WebSphere Extended Deployment
  • IBM Application Client for WebSphere Application Server
  • IBM WebSphere Business Integration Server Foundation
  • Web server plug-ins for WebSphere Application Server

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 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 updi_root/maintenance directory. The default maintenance package is the package with the latest date stamp and time stamp.
[AIX HP-UX Linux Solaris Windows] Important: See Update command - known problems and workarounds and the release notes for your product for the latest information about the Update Installer.

About this task

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

Procedure

  1. [AIX HP-UX Linux Solaris Windows] 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

    [Linux] If Japanese locale is enabled, you need to use the silent installation to avoid problems.

  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. Back up and delete any older copy of the Update Installer before downloading the current Update Installer. To use a newer version of the Update Installer, you must first remove the older version.
    1. Back up any files and subdirectories in the app_server_root/updateinstaller/maintenance directory if necessary.
    2. Delete the app_server_root/updateinstaller/maintenance directory and all of its subdirectories.
  4. [AIX HP-UX Linux Solaris Windows] 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, you must first remove the older version.

    1. Back up any files and subdirectories in the updi_root/maintenance directory if necessary.
    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 WebSphere Application Server supplements disc.
  5. Download the maintenance package
    For the Refresh Pack 6.0.2.0, or Fix Pack 19 or earlier
    1. The maintenance package is bundled with a valid version of the Update Installer.
    2. Continue following the instructions below for version 6.0.
    For Fix Pack 21, or later
    1. Download the ".pak" file from the support site. Move the downloaded ".pak" file into the updi_root/maintenance subdirectory of the version 6.0 Update Installer directory.
    2. Install Fix Pack 21, or 6.0.2.21, or later releases by launching the Update Installer. For more information, refer to http://www.ibm.com/support/docview.wss?rs=180&uid=swg24012718.
  6. Interim fixes only: Download the Update Installer from the Support site into a temporary directory.
    [AIX HP-UX Linux Solaris Windows] Download the compressed file for the Update Installer for WebSphere Software from one of the following IBM Web sites:
  7. [Windows] Make sure that all application servers are stopped.

    Run the stopServer command on all WebSphere Application Server profiles.

  8. [AIX HP-UX Linux Solaris Windows] 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.

    [AIX HP-UX Linux Solaris Windows] 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 (JVM)
    • 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 Creation wizard
    • Other InstallShield for Multiplatforms (ISMP) installation programs
    • InstallShield for Multiplatforms uninstall programs
    • The IBM Rational® Application Developer Agent Controller

    [AIX HP-UX Linux Solaris Windows] 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.

    [AIX HP-UX Linux Solaris Windows] See the following technote for more information, Stop all WebSphere Application Server-related Java processes before using the Update Installer for WebSphere software.

  9. Locate a valid IBM SDK, Java Technology Edition for the Update Installer to use.

    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.

    The Update Installer for WebSphere Software searches known locations for a suitable IBM SDK to use. In order, the Update Installer wizard looks for a valid Java Virtual Machine (JVM) in the following locations:
    1. The app_server_root/updateinstaller/java/jre directory (when updating the product SDK)
    2. The ../java/jre directory, which is the app_server_root/java/jre directory if you unpacked the Update Installer in the installation root directory:
      app_server_root
         /updateinstaller

      This SDK is the preferred SDK. However, if you did not unpack the Update installer or the maintenance package that includes the Update Installer into the installation root directory, the default relative addressing scheme does not work. In such a case, source the setupCmdLine script or use the -is:javahome option on the update command to set the correct JAVA_HOME variable setting.

    3. [AIX] [HP-UX] [Linux] [Solaris] The directory identified by one of the following environment variables on a system such as AIX or Linux:
      1. JAVA_HOME
      2. JAVAHOME
      3. JRE_HOME
      4. JREHOME

      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, a failure in sourcing the setupCmdLine script can result in the Update Installer program matching an SDK in a different order than the order described.

    You can also force the installation to use the correct SDK with the following command:

    [Windows]
    update.bat -is:javahome app_server_root/java/jre
    [AIX] [HP-UX] [Linux] [Solaris]
    ./update.sh -is:javahome app_server_root/java/jre

    To use the setupCmdLine script to set the JAVA_HOME variable, perform the following procedure that is appropriate for your operating system:

    [Windows]
    1. Open a command prompt window.
    2. Change directories to the app_server_root\bin directory.
    3. Issue the setupCmdLine.bat command.
    4. Use the same command prompt window to start the Update Installer, as described in a later step.
    [AIX] [HP-UX] [Linux] [Solaris]
    1. Open a command shell window.

      Important tip for SuSe Linux Enterprise System (SLES) users: Use either Terminal Emulator Superuser Mode or mlterm as the command shell.

    2. Change directories to the app_server_root/bin directory.
    3. Issue the . ./setupCmdLine.sh command. Notice the space between the periods. The special format for this command sources the command to make the setting active for all processes started from the command shell.

      Important tip for SLES users: After the . ./setupCmdLine.sh command, issue the echo $JAVA_HOME command to verify that JAVA_HOME is set correctly.

    4. Use the same command shell window to start the Update Installer, as described in a later step.

    [AIX HP-UX Linux Solaris Windows] See the following technote for more information, Using the setupCmdLine script to set JAVA_HOME before running the Update Installer for WebSphere software.

  10. [AIX HP-UX Linux Solaris Windows] 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.
    • [AIX HP-UX Linux Solaris Windows] The WebSphere SDK, Java technology edition is not corrupt.
    • [AIX HP-UX Linux Solaris Windows] The user is root on a system such as AIX or Linux or a member of the administrator group on a Windows system. In certain cases the user can be non-root or non-administrator users.
  11. [AIX HP-UX Linux Solaris Windows] Change directories to the updateinstaller 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 application server 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 does not display the graphical user interface when running in silent mode.

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

    [AIX HP-UX Linux Solaris Windows] Or, issue the update command to start the graphical user interface:

    [Windows]
    update.bat
    [AIX] [HP-UX] [Linux] [Solaris]
    ./update.sh

    The following tables show options that are available when using the update command.

    [AIX HP-UX Linux Solaris Windows] The commands in the first table each start the Update Installer wizard with a graphical user interface. The commands in the second table each cause the Update Installer wizard to run in silent mode.
    [AIX HP-UX Linux Solaris Windows]
    Table 2. 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 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.

    The commands in the following table each start the Update Installer wizard in silent mode without the graphical user interface:
    Table 3. Update Installer commands for installing in silent mode
    Command example Type of installation Description
    update.bat -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.bat -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.bat -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.bat -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.

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

    update.bat -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.bat -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.
  12. [AIX HP-UX Linux Solaris Windows] Click Relaunch to start the Update Installer again if the maintenance package causes the Update Installer to copy the Java 2 SDK.

    If the maintenance package includes service to the SDK, the Update Installer copies the SDK and stops. Click Relaunch to start the Update Installer again. The Update Installer can then install the maintenance package.

Results

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

What to do next

[AIX HP-UX Linux Solaris Windows] 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.




In this information ...


Related reference

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    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tins_ptfLevels
File name: tins_ptfLevels.html