WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Installing maintenance packages

This topic describes how to use the IBM Update Installer for WebSphere Software to install interim fixes, fix packs, and refresh packs. The Update Installer for WebSphere Software is also known as the Update Installer program, the UpdateInstaller program, and the Update installation wizard.

Before you begin

Use the proper authorizations to successfully install product updates.

Use the Update Installer program as the root user on a Linux or UNIX platform, or as the administrator on a Windows platform.

The Update Installer wizard is an InstallShield for Multiplatforms wizard that runs with either a graphical user interface or in silent mode with or without a response file.

When you omit the response file in silent mode, the wizard installs the maintenance package that you last downloaded to the default maintenance directory.

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
  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 maintenance directory.
  4. Interim fix only: Download the interim fix from the Support Web site into the 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:
  • The SDK, Java technology edition, in the java/jre directory
  • JAR files in the lib directory
  • Scripts in the bin directory
  • Profile templates

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.

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.

Viewing 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.
Updating cluster members
Apply the same maintenance packages to all of the WebSphere Application Server 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.

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.

Required information

The graphical interface requires you to supply the following information:
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 maintenance directory. The default maintenance package is the package with the latest date stamp and time stamp.
Important: See Known problems and workarounds for the update command and the release notes for your product for the latest information about the Update Installer.

Why and when to perform 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.

Steps for this task

  1. Log on as a user profile with *ALLOBJ special authority.
  2. Log on as root on a Linux or UNIX operating system, or as a member of the administrator group on a Windows system.
    [Linux][UNIX]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
  3. 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.

  4. 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.
  5. Refresh packs and fix packs only: Download the fix pack or refresh pack file from the Support site into a temporary directory.

    The compressed file for a refresh pack or a fix pack contains the Update Installer and the maintenance package.

    You can check for a newer version of the Update Installer code. Download the compressed file that contains the latest version of the Update Installer for WebSphere Software from one of the following IBM Web sites:
  6. Interim fixes only: Download the Update Installer from the Support site into a temporary directory.
    Download the compressed file for the Update Installer for WebSphere Software from one of the following IBM Web sites:
  7. Unpack the compressed file.

    Unpack the compressed file into the app_server_root directory:

    Or unpack the compressed file into one of the following directories in a Version 5.1.1.1 Extended Deployment environment:
    • [AIX]/usr/WebSphere/DeploymentManager
    • [HP-UX]/opt/WebSphere/DeploymentManager
    • [Linux]/opt/WebSphere/DeploymentManager
    • [Solaris]/opt/WebSphere/DeploymentManager
    • [Windows]C:\Program Files\WebSphere\DeploymentManager

    Unpacking the file creates the following directory structure:

    app_server_root
       /updateinstaller
          /framework
          /lib
          /maintenance
          /responsefiles

    Version information is stored in the version.txt file in the updateinstaller directory.

    A new version might ship to correspond to any new fix. Information in the version.txt file is displayed prominently in the title bar of the wizard and is also recorded in the updatelog.txt file.

    Always download and use the latest version of the Update Installer wizard when installing an interim fix.

  8. Interim fixes only: 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.
  9. [Windows]Use the Windows Services panel to stop all services for WebSphere Application Server processes.
  10. 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 Creation wizard
    • 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, IBM does not guarantee that the product can continue to run successfully, or without error.

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

  11. 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. [Linux][UNIX]The directory identified by one of the following environment variables on a Linux or UNIX system:
      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:
    ./update -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.
    [Linux][UNIX]
    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.

    See the following technote for more information, Using the setupCmdLine script to set JAVA_HOME before running the Update Installer for WebSphere software.

  12. 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 Linux or UNIX system or a member of the administrator group on a Windows system.
  13. 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 as a background process and does not display the graphical user interface when running in silent mode:

    update -silent

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

    update

    The following tables show all of the 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. Commands in the second table cause the Update Installer wizard to run in silent mode.
    Table 2. Update installer commands for installing with the graphical interface
    Command example Type of installation Description
    update Graphical interface mode 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 -W prereqsfailedpanelInstallWizardBean.active= "false" Graphical interface mode that bypasses prerequisites checking Initializes the maintenance package field with the name of the maintenance package 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.

    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.

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

Result

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.




Sub-topics
install.txt
Uninstalling maintenance packages
update command
Known problems and workarounds for the update command

Related reference
Product version information

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_ptfLevels.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)