Install interim fixes, interim features, or test fixes using the GUI

This page describes how to install an interim fix, interim feature, or test fix using the Update Installer for WebSphere Software.

Ensure that we have installed the most recent version of the Update Installer on a target system locally.

Use the Update Installer program from the same userid ID that installed WAS that we are updating. Otherwise, the file ownership mismatches might require correction by the root user. See Use root or non-root when installing with the Update Installer for more information.

The following steps outline the process of installing an interim fix, interim feature, or test fix pack.

 

1. Download the required interim fix, interim feature, or test fix pack from the official IBM support Web site into the updi_root/maintenance directory.

2. Make the current working directory: updi_root.

3. Ensure that you stop all running processes.

4. Launch the Update Installer.

   For example:
   

   (Windows)

   update.bat
   

   
   

   

   

   update.exe
   

   
   [AIX] [HP-UX] [Linux] [Solaris]

   ./update.sh
   

5. The Welcome panel is displayed. Click Next.

6. Specify the location of WAS that you want updated.

7. Select either to Install or Uninstall maintenance, the default is the install option. Click Next.

8. The system will prompt for the maintenance location where packages can be found. Enter the directory name containing the packages. Click Next.

9. Select to install an interim fix, interim feature, or test fix.

   The system will automatically determine the appropriate maintenance packages based on the version of WAS that is installed.

   When you select the interim fix, interim feature, or test fix, certain logic is used to determine which packages are installed. To find out more, refer to Logic that the Update Installer uses for system recommended installations.

10. Before the installation, the Confirmation panel confirms which packages will be installed.

    If a maintenance package is grayed out with the designation Not applicable on the selection panel, we can review the logs in the updi_root/logs/latest_temp_folder to find out why the maintenance package is not currently appropriate for installation.

11. On the Confirmation panel, we can also ensure that you have the correct permissions to perform the installation of a maintenance package.

    1. To ensure we have the correct permissions to apply maintenance, select Verify My Permissions. After the permission checking finishes, the confirmation panel displays the permission checking results. If permission checking succeeds, then Verify My Permissions is deselected. You can then click Next to install maintenance. If permission checking fails, then Verify My Permissions remains selected. We can perform the necessary actions to resolve the permission problems and then verify the permissions again.

    2. If we deselect Verify My Permissions and click Next, then you skip permission checking and the Update Installer performs the installation. If we do not have all of the necessary permissions, then the installation fails.

12. After the installation, the Summary panel lists which packages have been installed.

13. After the interim fix, interim feature, or test fix has been installed, check the installation log to verify the install was successful. The log can be found at APP_ROOT/logs/update/maintenance_package.install.

 

Results

One of the following results will appear in the log.

INSTCONFSUCCESS

The operation was a success.

INSTCONFPARTIALSUCCESS

The operation was partially successful, refer to the log for more details.

INSTCONFFAILED

The operation failed, refer to the log for more details.

---

 

Related tasks

Install maintenance packages, interim fixes, fix packs, and refresh packs

 

Related

install.txt
Logic that the Update Installer uses for system recommended installations
Use root or non-root when installing with the Update Installer