Install multiple maintenance packs using the GUI

We can install maintenance for WAS and all stack products installed in the same WAS home directory.

Verify the most recent version of the Update Installer is installed on a target system locally.

Use the Update Installer program from the same user 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 Update Installer is capable of automatically selecting the recommended maintenance for stack products and determining the appropriate installation sort order of the maintenance packages. For example, if multiple feature packs are installed and there is a recommended fix pack and interim fix for each product, the Update Installer will determine if this maintenance is applicable and install them in the correct order.

The following steps lead you through the process of installing multiple maintenance packages.

 

1. Download the required packages from the official IBM support Web site into the updi_root/maintenance directory. It is also recommended you download the maintenance for any stack products in this same 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 system displays the Welcome panel. Click Next.

6. The system prompts for the location of WAS that needs to be updated.

7. Select Install. Click Next.

8. The system prompts for the maintenance location where packages can be found.

   Before entering the directory name of the location that contains the maintenance packages, notice there are links to obtain recommended maintenance for WAS. We recommend to click the link to Recommended fixes for Websphere application Server to verify the latest maintenance available for WAS has been downloaded. Also download maintenance for any stack products installed under the same location as you selected in step 6. Enter the directory name containing the packages. Click Next.

9. The system displays a list of maintenance packages available for installation. Select Recommended updates or select the packages we need installed. The Recommended updates selects the most recent applicable pack. Click Next.

   To find out more about how the multiple installation works, refer to Logic that the Update Installer uses for system recommended installations. If we choose to make our own selection, the system logically changes the remaining packages available for selection based on product, prerequisite and containment relationships.

10. Confirm the information from the pre-installation confirmation Summary panel. This panel highlights the maintenance packages to be installed and products to be updated.

    If a maintenance package is grayed out with the designation Not applicable on the selection panel, we can review the logs in 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 we 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. We 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. The Update Installer shows progress as backup and installation of maintenance packages are completed. After all maintenance packages have been selected and verified to be installable as a group, the installer installs the packages in the following sequence:

    1. Refresh packs

    2. Fix packs

    3. Enable interim fixes (automatically installed)

    4. Interim fixes

    5. Interim features.
    Prerequisite checking continues to apply as each maintenance package is installed. Any failure that is detected stops the install flow. The message is displayed and we can find details in the installation logs covering the failure.

13. A final panel displays the Summary panel. This panel reports information about the completed install action taken. The user is prompted to click Finish to exit the wizard.

14. Review the log to verify maintenance was installed successfully. 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