IBM® WebSphere® SDK Java™ Technology Edition Version 6.0 is no longer in service. Using IBM Installation Manager, you can optionally install IBM WebSphere SDK Java Technology Edition Version 8.0. For new installations of WebSphere Application Server 8.5.5.11 or later, Java SE 8 is installed by default.

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.

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.

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.

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.

Note: WebSphere Application Server Version 8.5.5.9 and later support IBM WebSphere SDK Java Technology Edition Version 8.0. This package is not available on the product media or on IBM Passport Advantage®.

1. Optional: If the repository requires a user name and password, create a key ring file to access this repository.

   For more information on creating a key ring file for Installation Manager, read the IBM Installation Manager documentation.

   Tip: When you create a key ring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.

   Supported configurations:

   Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

   In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

   There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the IBM Installation Manager documentation.

2. Log on to your system.
3. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
4. Verify that the repository is available.
   

   imcl.exe listAvailablePackages -repositories path_to_repository

   

   ./imcl listAvailablePackages -repositories path_to_repository

   You see one or more levels of the offering.
5. Use the imcl command to install the offering.
   

   imcl.exe install com.ibm.websphere.IBMJAVA.v80_offering_version
     -repositories source_repository 
     -installationDirectory installation_directory
     -keyring keyring_file -password password

   

   ./imcl install com.ibm.websphere.IBMJAVA.v80_offering_version
     -repositories source_repository 
     -installationDirectory installation_directory
     -keyring keyring_file -password password

   Tips:

   • The offering_version, which can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.0.20110503_0200 for example).
     • If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
     • If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.
     The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:

     imcl listAvailablePackages -repositories source_repository

   • You can also specify none, recommended, or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.
     • If the offering version is not specified, the -installFixes option defaults to all.
     • If the offering version is specified, the -installFixes option defaults to none.
   • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation image or repository for this product.
   • The program might write important postinstallation instructions to standard output.
   • For installation_directory, specify the appropriate WebSphere Application Server installation path on which to install IBM WebSphere SDK Java Technology Edition Version 8.0.

   For more information about using the imcl command, see the IBM Installation Manager documentation.