Maintaining the feature pack on Windows, Linux and UNIX

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.

Before you begin
Before installing feature pack maintenance perform the following tasks:
About this task
The maintenance packages do not update the profiles. Instructions that you receive with your interim fix or fix pack override the instructions in this topic, which are provided for your general reference only. Always follow the installation instructions you receive with your specific maintenance package.
  1. Change directories to the Update Installer directory. The Update Installer directory is located in one of the following default locations:
    • For AIX operating systems: /usr/IBM/WebSphere/UpdateInstaller
    • For HP-UX, Linux, and Solaris operating systems: /opt/IBM/WebSphere/UpdateInstaller
    • For Windows operating systems: C:\Program Files\IBM\WebSphere\UpdateInstaller

    Install the maintenance package on the deployment manager node before installing the maintenance package on each server node that you intend to update.

  2. Type the update command for your platform to start the Update Installer and click Next to exit the Welcome page.
    • For AIX, HP-UX, Linux, and Solaris operating systems: ./update.sh
    • For Windows operating systems: update.bat
    • For Windows Vista and Windows 2008 operating systems: update.exe
    Important: Do not start multiple copies of the Update Installer at one time. Running more than one instance of the Update Installer at a time is not supported and can produce unpredictable results, which might include a failed or faulty update.
    For more information about the update command, see the update command topic in the WebSphere Application Server Network Deployment documentation.
  3. On the Product Selection page, select the installation of the feature pack that you want to update and click Next.
  4. On the Maintenance Operation Selection page, select to install maintenance and click Next.
  5. On the Maintenance Package Directory Selection page, select the directory that contains the interim fix or fix pack you want to install and click Next.
  6. On the Available Maintenance Package to Install page, select the interim fix or fix pack you want to install and click Next.
  7. Review the Installation Summary panel and click Next to begin the update.
    Note: When installing a fix pack, you will receive a warning at this stage if interim fixes applied previously will be removed, and if so, whether they will be reapplied.
  8. On the Installation Complete page, click Finish to exit the Update Installer or Relaunch to add or remove additional maintenance packages.
Results
The Update Installer installs the maintenance package and the Installation Complete page indicates whether the completed update was successful. The Update Installer records installation events in a log file in the following directory:
  • For AIX, HP-UX, Linux, and Solaris operating systems: feature_pack_install_root/logs/update/interim_fix_name or fixpack_name.install/updatelog.txt
  • For Windows operating systems: feature_pack_install_root\logs\update\interim_fix_name or fixpack_name.install\updatelog.txt

If errors are detected during the update, other messages might be displayed in place of Success. A message of Partial success indicates that the update completed but errors were generated. A message of Failed indicates that the update failed completely. In either case, the log file provides information to troubleshoot the problems.

You can also verify that the maintenance is applied by running the command versionInfo -maintenancePackages from the following directory:
  • For AIX, HP-UX, Linux, and Solaris operating systems: feature_pack_install_root/bin
  • For Windows operating systems: feature_pack_install_root\bin
What to do next

If a maintenance package affects EAR files, those updated EAR files are not deployed automatically. Deployment requires an extra step, which is described in the maintenance package readme file.