Maintaining the feature pack prerequisites

You can use the IBM® Update Installer for WebSphere® Software to install interim fixes and fix packs, collectively known as maintenance packages. On all platforms except i5/OS®, the Update Installer runs with a graphical user interface.

About this task
Before installing maintenance on the feature pack, you must ensure that the following prerequisites have been met.
  1. On Windows®, stop all Windows services.
  2. Stop all Java™ processes related to the WebSphere Business Process Management product installation containing the feature pack on the system where you are using the Update Installer program. For example, Java processes can include:
    • All Java Virtual Machines (JVMs)
    • WebSphere Business Process Management product 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 A WebSphere Process Server or WebSphere Enterprise Service Bus process running on an i5/OS subsystem. A process can be stopped by ending the subsystem where it is running. This subsystem is either QWAS61 (default) or QWBI61 (custom) and can be ended with the ENDSBS command.
    • IBM HTTP Server processes
    • Web services processes that use a plug-in you are installing.
    • First steps consoles.
    • Installation verification test (IVT) processes.
    • The Profile Management Tool.
    • Installation programs.
    • Uninstallation programs.
    • IBM WebSphere Integration Developer Java processes.
    • The IBM Agent Controller.
    • The Derby Network Server database server.
  3. Use the same user account that originally installed the feature pack to install the Update Installer. That same user account must be used to start the Update Installer program to update the feature pack.
  4. For AIX® operating system. 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.
  5. Ensure that no processes from any users are locking any files in the target location where the maintenance package is to be installed.
  6. Windows Vista and Windows 2008 platforms. 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 the WebSphere Business Process Management product and feature pack were originally installed.
    • If UAC was enabled during installation, apply maintenance with UAC enabled.
    • If UAC was disabled during installation, apply maintenance with UAC disabled.

    If a non-administrator applies maintenance with a UAC setting that is different from the one used in the initial installation, the registry is adversely affected. This can result in unreliable listings of the installation locations in the destination panels of the Update Installer, or in an existing installation location not showing 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 the publisher of the program is recognized. For certain WebSphere Business Process Management product programs, for example, an operating-system dialog might appear that states "An unidentified program wants access to your computer." Examine the program details. If it is the WebSphere Business Process Management product program that you intend to run, click Allow to proceed.