Install interim fixes and fix packs

 

The update installer application installs and uninstalls interim fixes, cumulative fixes, and fix packs (also known as fixpacks, FixPaks and program temporary fixes, or PTFs).

The update installer application can also uninstall interim fixes and fix packs.

Installing a fix pack uninstalls all interim fixes.

1. Verify there is enough disk space. Fix packs typically require 50 MB and 250 MB in...

   $WAS_HOME/properties/version/backup directory.

   ...and approximately 400 MB of free space in the /tmp directory and another 400 MB in the file system that hosts the WAS image (typically /usr) on a UNIX-based platform.

2. Use the versionInfo command in the $WAS_HOME/bin directory to display the exact fix and version level of the product. Do not use the versionInfo command while installing an interim fix or fix pack.

3. Download the interim fix and the update installer, or download the fix pack (which includes the update installer)

4. Unpack the interim fix or fix pack. Unpacking the fix pack automatically creates the fixpacks directory.

5. Stop each server process on the base WAS node with the stopServer command.

   Stop all WAS-related Java processes. On a Windows platform, you can use the task manager to stop Java processes. On a UNIX-based platform, use the kill command to stop Java processes.

6. Create an /update directory, if it does not already exist.

7. Download the update installer application ZIP file to the /update directory, if you are installing an interim fix.

   Download the current version of the file even though you might have an update installer from a previous interim fix installation. The Support page links to the current installer.

8. Extract the contents of the ZIP file to the /update directory.

9. Create the /update/fixes repository if you are installing an interim fix.

   It is not necessary to create the /fixpacks repository directory. Unpacking the fix pack creates the /fixpacks directory, if it does not already exist.

10. Download the interim fix or download and unpack the fix pack.

    Download an interim fix from the Support page to the /update/fixes directory. Download a fix pack ZIP file to the /update directory. Unpack the fix pack to automatically create the /fixpacks directory.

11. Set up the Java environment for the update installer.

    If the update installer can set the Java environment, this step is not necessary. Otherwise, this is a required step.

    The location of the update, fixes, and fixpacks directories is arbitrary. You can create the directories anywhere so long as you do not use a directory name with one or more spaces.

12. Stop all Java processes on the machine

    It is possible that the update installer cannot set the JAVA_HOME environment variable. If you receive a message that the update installer cannot set JAVA_HOME, set the environment variable yourself, or issue the appropriate command script from the bin directory of the product installation root:

    1. Open a command-line window.

    2. Change directory to the bin directory of the installation root.

    3. Issue the appropriate command to set JAVA_HOME...
       • . $WAS_HOME/bin/setupCmdLine.sh
       • . $WAS_HOME/bin/setupClient.sh

13. Use one of the two interfaces to the update installer to apply the interim fix or fix pack to the base node...

    • Refer to the updateWizard command topic for usage information.

    • Refer to the updateSilent command description of the proper syntax for installing the interim fix or fix pack...

      • Install interim fixes

      • Install fix packs

    For example, to install the was50_fp2_win fix pack, use this updateSilent command

    updateSilent -fixpack \ 
                 -installDir "/opt/WebSphere/AppServer"  \
                 -skipIHS  \
                 -fixpackDir "/opt/WebSphere/AppServer/update/fixpacks" \
                 -install  \
                 -fixpackID was50_fp2_win
    

    The command is shown here on more than one line, for clarity.

14. Restart each server on the node with the startServer command.

15. Restart the node agent for the base node with the startNode command.

16. Verify that the node is online and functioning correctly.

    There are several ways to verify the successful application of an interim fix or fix pack:

    • Does the interim fix or fix pack appear in the wizard panel that lists applied interim fixes, or the panel that lists applied fix packs? If so, the interim fix or fix pack is installed.

    • Does the interim fix or fix pack appear in the wizard panel that lists installable interim fixes, or the panel that lists installable fix packs? If so, the interim fix or fix pack is uninstalled.

    • Is there a [interim fixID].efix or [fix packID].ptf file in the $WAS_HOME/properties/version/version directory, or a [interim fixID].efixApplied, [interim fixID].efixDriver, [fix packID].ptfApplied, or [fix packID].ptfDriver file in the $WAS_HOME/properties/version/history directory?

    • Do the product version and history reports show the interim fix or fix pack as installed or removed?

    • Does collecting interim fix information and update state show that the interim fix is installed or removed?

    • Does collecting fix pack information and update state show that the fix pack is installed or removed?

    You can also run the installation verification tool on the node to verify that the node is operational.

 

---