WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Installing fix packs and refresh packs with the Update Installer

You can use the IBM® Update Installer for WebSphere® Software to install interim fixes, fix packs, and refresh packs collectively known as maintenance packages. 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 correct authorizations to successfully install product updates.

When administrative security is enabled on WebSphere Application Server Network Deployment or WebSphere ESB, you must supply the administrative user ID and password before you can update the files.

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

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.

For i5/OS operating system On i5/OS® platforms: Use the Update Installer program from a user profile with *ALLOBJ special authority.

Important:
  • The user account that originally installed the product you want to update should be used to install the Update Installer, and the same user account should be used to start the Update Installer program to update the product.
    • When a different user account uses the location where the Update Installer files are located, that user account must have reading and running access to that location. It must also have writing access to the logs directory and its subdirectory. For information about the location of the Update Installer files, see Installing the Update Installer for WebSphere Software.
    • 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.
  • For AIX operating system On AIX® platforms: If a non-root user starts 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.
The Update Installer is an InstallShield MultiPlatform 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 last maintenance package that you downloaded to the default maintenance directory. For more information about the example response file that is installed with the Update Installer, see the install.txt topic in the WebSphere Application Server Network Deployment documentation.
For i5/OS operating system Restriction: On i5/OS platforms: The Update Installer on i5/OS runs only with the install.txt response file.
Important: The maintenance package updates the profiles. Before updating an existing installation, back up your configuration files. Use the backupConfig command to back up the configuration of each profile that the maintenance package can update. See Backing up and restoring administrative configurations for more information about running this command.

For refresh packs you might also need to update the various WebSphere ESB database schemas. If you want to uninstall your refresh pack, then you need to restore your database to the previous level, so you need to backup your database as well. For detailed installing or uninstalling instructions, please refer to the instructions provided with your fix pack or refresh pack.

About this task

Updating is modifying a file or data set with current information. When WebSphere ESB is updated with a refresh pack, interim fix, or a fix pack, its out-of-date files are replaced with newer versions. Updating is different from migrating, which is installing a completely new version of the product to replace an earlier version of the product. For more information about migrating, see Migrating.

Important: Instructions you receive with your interim fix, fix pack or refresh pack override the instructions in this topic, which are provided for your general reference only. Always follow the specific installation instructions you receive with your interim fix, fix pack or refresh pack.
Check the list of WebSphere ESB recommended fixes to confirm that your software is at the latest maintenance level. From the Recommended Fixes web page, make sure to read the readme file, also called the installation instructions, for the fix pack or refresh pack that you are installing.
Important: Do not start multiple copies of the update installer at one time. Concurrent instances 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.
Note: Throughout this topic, certain directory paths are shown only in Linux® and UNIX® format for simplicity. The equivalent Windows® paths are identical except for the direction of the slashes.

The following procedure describes how to install a maintenance package. For a description of how to roll back a maintenance package, see Uninstalling maintenance packages.

To install an interim fix, a fix pack, or a refresh pack, perform the following steps.

Procedure
  1. Make sure that the most recent version of the Update Installer for WebSphere Software is installed on your system. In order to install an interim fix, a fix pack, or a refresh pack, you must have the Update Installer for WebSphere Software installed. You can download it from the WebSphere ESB product support Web site or from the product DVD using the launchpad. For more information about installing for the first time, see Installing the Update Installer for WebSphere Software. For more information about installing a newer version of the update installer, see Updating the Update Installer for WebSphere Software in the WebSphere Application Server Network Deployment documentation.
    For Vista operating system Note: Using the Update Installer for WebSphere Software on the Microsoft® Windows Vista operating system: To use the Update Installer for WebSphere Software on the Microsoft Windows Vista operating system, you must have Version 6.1.0.9 or later of the Update Installer installed on your system. Earlier versions of the Update Installer are not supported on the Windows Vista operating system.
  2. Download the most current version of the interim fix, fix pack, or refresh pack from the WebSphere ESB recommended fixes Web site into the update installer maintenance directory. The maintenance directory is located in one of the following locations, depending on the operating system that you are using:
    • For AIX operating system On AIX platforms: /usr/IBM/WebSphere/UpdateInstaller
    • For i5/OS operating system On i5/OS platforms: /QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI
    • For HP-UX operating systemFor Linux operating systemFor Solaris operating system On HP-UX, Linux and Solaris platforms: /opt/IBM/WebSphere/UpdateInstaller
    • For Windows operating system On Windows platforms: C:\Program Files\IBM\WebSphere\UpdateInstaller
  3. For Windows operating system On Windows platforms: Use the Windows Services panel to stop all services for WebSphere ESB processes.
  4. Stop all WebSphere ESB-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 ESB processes, including:
      • Server processes
      • The node agent process on a node when the node is federated into a deployment manager cell
      • The dmgr process for the deployment manager server
      • For i5/OS operating system On i5/OS platforms: The above processes can be stopped by ending the subsystem where the WebSphere ESB is running. This subsystem will either be QWAS61 (default) or QWBI61 (custom) and can be ended with the ENDSBS command.
    • IBM HTTP Server processes
    • Web services processes that use a plugin you are installing
    • First steps consoles
    • Installation verification test (IVT) processes
    • The Profile Management Tool
    • Other InstallShield MultiPlatform (ISMP) installation programs
    • InstallShield MultiPlatform uninstallation programs
    • IBM WebSphere Integration Developer Java processes
    • The IBM Agent Controller
    • The Derby Network Server database server (if you are updating a deployment manager profile that is configured to use Derby Network Server).
  5. Change directories to the update installer directory. The update installer directory is located in one of the following locations, depending on the operating system that you are using:
    • For AIX operating system On AIX platforms: /usr/IBM/WebSphere/UpdateInstaller
    • For i5/OS operating system On i5/OS platforms:/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI
    • For HP-UX operating systemFor Linux operating systemFor Solaris operating system On HP-UX, Linux and Solaris platforms: /opt/IBM/WebSphere/UpdateInstaller
    • For Windows operating system On Windows platforms: C:\Program Files\IBM\WebSphere\UpdateInstaller
  6. Use the update command to install the interim fix, fix pack, or refresh pack. Install the maintenance package on the deployment manager node before installing the maintenance package on each server node that you intend to update.
    • To install the maintenance package using the graphical user interface, type one of the following commands:
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: ./update.sh to initialize the maintenance package field with the name of the package that has the most recent date stamp and time stamp.
      • For Windows operating system On Windows platforms: update.bat to initialize the maintenance package field with the name of the package that has the most recent date stamp and time stamp.
      • For Vista operating system On Vista and Windows 2008 platforms: update.exe to initialize the maintenance package field with the name of the package that has the most recent date stamp and time stamp.
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: ./update.sh -options "responsefiles/file_name" to override all graphical interface values with values that you specified in the options response file. For more information about the example response file that is installed with the update installer, see the install.txt topic in the WebSphere Application Server Network Deployment documentation.
      • For Windows operating system On Windows platforms: update.bat -options "responsefiles/file_name" to override all graphical interface values with values that you specified in the options response file. For more information about the example response file that is installed with the update installer, see the install.txt topic in the WebSphere Application Server Network Deployment documentation.
      • For Vista operating system On Vista and Windows 2008 platforms: update.exe -options "responsefiles/file_name" to override all graphical interface values with values that you specified in the options response file. For more information about the example response file that is installed with the update installer, see the install.txt topic in the WebSphere Application Server Network Deployment documentation.
      For more information about options to use with the update command, see the update command topic in the WebSphere Application Server Network Deployment documentation.
      For Vista operating system Note: Running the Update Installer for WebSphere Software on Microsoft Windows Vista and Windows 2008 operating systems: If a non-Administrator applies maintenance using the Update Installer, that user must do so with Windows User Account Control (UAC) in the same state that it was in when WebSphere ESB was originally installed.
      1. If UAC was enabled during installation of WebSphere ESB, apply maintenance with UAC enabled.
      2. If UAC was disabled during installation of WebSphere ESB, apply maintenance with UAC disabled.

      If a non-Administrator applies maintenance to WebSphere ESB with a UAC setting that is different from that used in the initial installation, then the registry is adversely affected. This might result in unreliable listings of the installation locations in the destination panels of the Update Installer, or an existing installation location might not show up in the dropdown menu.

      When the Windows Vista or Windows 2008 operating system is asked to run a program that requires elevated (Administrator) privileges, it first tells the user whether or not the publisher of the program is recognized. For certain WebSphere ESB programs, for example, an operating-system dialog might appear that states "An unidentified program wants access to your computer." Examine the program details; and if it is the WebSphere ESB program that you intend to run, click Allow to proceed.

    • To install the maintenance package as a background process, using the silent mode, type one of the following commands:
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: ./update.sh -silent -options "responsefiles/file_name" to install without a graphical user interface, using the values that you specified in the options response file. For more information, see install.txt topic in the WebSphere Application Server Network Deployment documentation.
      • For Windows operating system On Windows platforms: update.bat -silent -options "responsefiles/file_name" to install without a graphical user interface, using the values that you specified in the options response file. For more information, see install.txt topic in the WebSphere Application Server Network Deployment documentation.
      • For Vista operating system On Vista and Windows 2008 platforms: update.exe -silent -options "responsefiles/file_name" to install without a graphical user interface, using the values that you specified in the options response file. For more information, see install.txt topic in the WebSphere Application Server Network Deployment documentation.
      • For i5/OS operating system On i5/OS platforms: update -options responsefiles/file_name
        Important: When using the update command on the i5/OS platform, do not include the -silent option in the command line. The option is included in the response file itself.

    For more information about the update command, see the update command topic in the WebSphere Application Server Network Deployment documentation.

    The Update installer creates a backup files in the install_root/properties/version/nif/backup directory.
    Note: When you install a maintenance package that contains service for a profile that a non-root user owns, you own any new files that the maintenance package creates. You can change the ownership of the new files so that a non-root user can successfully start the product. For more information, see Installing maintenance packages as an installer and changing the ownership of profile-related files in the WebSphere Application Server Network Deployment documentation.

What to do next

After installing an maintenance package, continue to use your WebSphere software.

Important: For information about known problems, see Update command - known problems and workarounds in the WebSphere Application Server Network Deployment documentation.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_apply_service.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).