[AIX Solaris HP-UX Linux Windows]

Installing fix packs on distributed operating systems using the GUI

You can update this product to a later version using the Installation Manager GUI.

Before you begin

Attention: Starting in version 8.5.5.11, the default versions of Java are Java SE 6 or Java SE 8. As such, you can accept the default and install either Java SE 6 or Java SE 8 as the version of Java SE contained in the /java and /java64 directories in WebSphere Application Server and used by default during server and node configuration. Java 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 6, but no service can be provided after the end of support in April 2018, which might expose your environment to security risks.
Java SE 7 and Java SE 7.1 (not available for Solaris and HP) are also viable options for installing on WebSphere Application Server version 8.5.5.11.
  • The bit level of Java SE 7.0 is based on the bit level selected during the initial installation of WebSphere Application Server. If a 32-bit WebSphere Application Server is installed, then only the 32-bit Java SE 7.0 can be installed. If a 64-bit WebSphere Application Server is installed, then only the 64-bit Java SE 7.0 can be installed.
  • Installing the optional Java SE 7.0 or Java SE 7.1 does not imply that profiles can take advantage of this new version of Java. The managesdk command can be used to switch Java or the WebSphere Application Server administrative console (wsadmin) can be used to make the switch.

[8.5.5.14 or later]Starting in version 8.5.5.14, Java SE 8 is the default Java. When updating to 8.5.5.14, any existing profile that uses Java SDK 6 is replaced by Java SDK 8. You can continue to use Java SDK Java Technology Edition Version 7.0 and Version 7.1, but no service can be provided after the end of support in July 2022, which could expose your environment to security risks.

For more information on Java SE 6, 7, and 7.1 end of service, see Java SE 6, 7, and 7.1 end of service in WebSphere Application Server V8.5.

The com.ibm.websphere.IBMJAVA.v80 offering will be deprecated, and no fix packs or interim fixes will be provided for this offering after March 2020. If this offering is installed with WebSphere Application Server Version 8.5.5 after March 2020, uninstall it and switch to the default Java SE 8 SDK provided by the WebSphere Application Server package in the same package group. With the default Java SE 8 SDK, you continue receiving Java SE 8 SDK support, including security updates.

[8.5.5.18 or later]Starting in version 8.5.5.18 for Linux on POWER8 Little Endian (LE), the default versions of Java are Java SE 7.1 or Java SE 8. As such, you can accept the default and install either Java SE 7.1 or Java SE 8 as the version of Java SE contained in the /java directory in WebSphere Application Server and used by default during server and node configuration. Java 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 7.1, but no service can be provided after the end of support in July 2022, which might expose your environment to security risks.

You can use the user.wasjava=java8 property only with new installations of the product for Linux on POWER8 LE. The user.wasjava=java8 property does not work for product upgrades through fix packs for Linux on POWER8 LE.

[8.5.5.19 or later]Starting in version 8.5.5.19 for Linux on POWER8 Little Endian (LE), the default version of Java is Java SE 8. As such, you can accept the default and install Java SE 8 as the version of Java SE contained in the /java directory in WebSphere Application Server and used by default during server and node configuration. You can continue to use Java SE 7.1 by installing IBM WebSphere Java SDK Version 7.1, but no service can be provided after the end of support in July 2022, which might expose your environment to security risks.

The user.wasjava=java8 property is not required for installing and updating to version 8.5.5.19 for Linux on POWER8 LE.

Contact the IBM® Software Support Center for information about upgrades for WebSphere® Application Server. The most current information is available from the IBM Software Support Center and Fix Central.

IBM Installation Manager is used to apply product maintenance to WebSphere Application Server.

Make sure that the web-based or local service repository location is listed and checked or that the Search service repositories during installation and updates option is selected on the Repositories panel in your Installation Manager preferences. For more information on using service repositories with Installation Manager, read the IBM Installation Manager documentation.

About this task

Restriction: You cannot use the Installation Manager to upgrade an installation and add or remove the full WebSphere Application Server profile feature or the Liberty profile feature.
Note: In WebSphere Application Server Version 8.5.5.0, the Liberty profile was promoted from a feature to an independently installable offering. You cannot make an inplace update of the Version 8.5.0.x Liberty profile feature. The wlp folder includes the Liberty runtime and any user data or server configurations that you have saved in the wlp/usr folder. If you have a combined full-profile and Liberty-profile Version 8.5.0.x installation, the update program will back up the wlp folder for the existing Version 8.5.0.x Liberty profile feature into the wlp.bak_<timestamp> folder and uninstall the feature during an update to Version 8.5.5.0 or higher. You can continue using Liberty from the backed-up location or copy it elsewhere. To update the Liberty profile to Version 8.5.5.0 or higher, you then must install WebSphere Application Server Liberty Network Deployment with the com.ibm.websphere.liberty.ND.v85 offering ID. After installing the WebSphere Application Server Liberty product, you can move any user data and server configurations from the wlp.bak_<timestamp> folder to the new Liberty installation.

Procedure

  1. Log on to your system.
  2. Stop all servers and applications on the WebSphere Application Server installation that is being updated.
  3. Start Installation Manager.
  4. Click Update.
    Note: If you are prompted to authenticate, use the IBM ID and password that you use to access protected IBM software websites.
  5. Select the package group to update.
    Tip: If you select Update all, Installation Manager will search all of the added and predefined repositories for recommended updates to all of the package groups that it has installed.
    • Use this feature only if you have full control over which fixes are contained in the targeted repositories.
      • If you create and point to a set of custom repositories that include only the specific recommended fixes that you want to install, you should be able to use this feature confidently.
      • If you enable searching service repositories or install fixes directly from other live web-based repositories, you might not want to select this option so that you can select only the fixes that you want to install for each offering on subsequent panels.
    • If you select Update all, Installation Manager will install only the recommended updates to all of the package groups; it will not allow you to select non-recommended fixes for installation. If you want to install non-recommended fixes, perform the following actions:
      1. On this panel, clear the Update all check box and select an offering to update.
      2. On the next panel, clear the option to show only recommended fixes and then select the fixes that you want to install.
  6. Click Next.
  7. Select the version to which you want to update under IBM WebSphere Application Server Network Deployment.
  8. Select any fixes that you want to install.

    Any recommended fixes are selected by default.

    If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

  9. Click Next.
  10. Accept the terms in the license agreements, and click Next.
  11. Select the optional features that you want in your updated installation.
  12. Review the summary information, and click Update.
    • If the installation is successful, the program displays a message indicating that installation is successful.
    • If the installation is not successful, click View Log File to troubleshoot the problem.
  13. Click Finish.
  14. Click File > Exit to close Installation Manager.