Installing IBM SDK, Java Technology Edition on z/OS

The product code for IBM® SDK, Java™ Technology Edition is installed using IBM Installation Manager Version 1.8.5 or later. Liberty can run with any compliant Java runtime environment (JRE) or Java software development kit (SDK).

Important:

Java SE 8 is the recommended Java SDK because it provides the latest features and security updates.

Before you begin

Create an Installation Manager on your z/OS® system.
You will need to know the location of the binaries directory for the Installation Manager and have access to a user ID that can invoke the Installation Manager.
Install a copy of WebSphere® Application Server for z/OS Liberty.
Obtain the product repository for a version of IBM SDK, Java Technology Edition. The repository can be mounted read-only.

About this task

New: Installation Manager now supports two types of Java SDK offerings:

Common IBM Java SDKs: These offerings, which are denoted by com.ibm.java.jdk IDs, are available for the latest Java versions. Because these offerings do not follow the WebSphere fix pack schedule, you can receive Java security updates faster, as they become available. These offerings are also used by WebSphere Application Server traditional V9.0.
WebSphere Java SDKs: These offerings, which are denoted by com.ibm.websphere.liberty.IBMJAVA IDs, are available for older Java versions. Updates to these offerings are delivered according to the WebSphere fix pack schedule.

The following table lists the Java SDK offering names and IDs.

Table 1. IBM Java SDK offerings
Java SDK offering name	Offering ID
IBM SDK, Java Technology Edition, Version 8	`com.ibm.java.jdk.v8`
IBM SDK, Java Technology Edition, Version 7 Release 1	`com.ibm.java.jdk.v71`
IBM WebSphere SDK, Java Technology Edition, Version 7	`com.ibm.websphere.liberty.IBMJAVA.v70`
IBM WebSphere SDK, Java Technology Edition, Version 6	`com.ibm.websphere.liberty.IBMJAVA.v60`

Note: Liberty

Version 8.5.5 supported the com.ibm.websphere.liberty.IBMJAVA.v80 and com.ibm.websphere.liberty.IBMJAVA.v71 offerings. Although you can continue to install these offerings, consider installing the common Java SDK instead for both new and existing installations. Note that these WebSphere Java SDK offerings cannot be used with the versionless Liberty offering, com.ibm.websphere.liberty.zOS, which was introduced in Version 9.0. For this Liberty offering, you must install the IBM Java SDKs.

The com.ibm.websphere.liberty.IBMJAVA.v80 offering is deprecated and no fix packs or interim fixes will be provided for this offering after March 2020. If this offering is installed with Liberty Version 8.5.5 after March 2020, you must uninstall it and install com.ibm.java.jdk.v8 to continue to receive security updates and fixes.

Important: The type of Java SDK that you choose impacts how updates are delivered.

For both the IBM Java SDKs and the WebSphere Java SDKs, fix packs contain bundled service that brings the Java SDK installation up to a new level, such as 8.0.3.10. However, the packaging and installation of individual fixes differs:

Common IBM Java SDKs: Individual fixes are packaged as fix packs that have an updated time stamp. Content in the individual fixes for IBM SDK, Java Technology Edition is cumulative, so the fixes contain the fix pack content for the specified level plus any maintenance prior to the fix. Because individual fixes are packaged as fix packs, no interim fixes are provided, and all updates for the IBM Java SDKs are installed by following the method for installing and uninstalling fix packs.
WebSphere Java SDKs: Similar to Liberty and other WebSphere product offerings, individual fixes are packaged as interim fixes, which are applied differently from fix packs.

Procedure

Choose the installed copy of WebSphere Application Server for z/OS Liberty onto which you will install IBM SDK Java Technology Edition.
Mount the product file system for this copy of WebSphere Application Server for z/OS Liberty at the same location at which it was originally installed with IBM Installation Manager.
The file system will require a minimum of 7,500 tracks (3390) or 350 megabytes of available disk space to install IBM SDK Java Technology Edition.
You can use the zMountFileSystem.sh script in the eclipse/tools subdirectory of the Installation Manager binaries location to mount this file system. For example:
```
cd /InstallationManager/bin/eclipse/tools

zMountFileSystem.sh -name WAS.SBBOHFS -type ZFS
  -mountpoint /usr/lpp/WebSphere/Liberty/V9R0
```
You can add the -owner, -group, and -perm options to this command to set the ownership and permissions for all files in the file system.
Log in to the Unix System Services shell under the Installation Manager user ID, and change the directory to the eclipse/tools subdirectory of the Installation Manager binaries location.
For example:
```
cd /InstallationManager/bin/eclipse/tools
```

If you plan to use the web-based service repository, create a credential storage file on z/OS to access this repository by running the imutilsc command.

installation_manager_binaries_directory/eclipse/tools/imutilsc saveCredential 
  -secureStorageFile storage_file
  -userName user_ID -userPassword user_password
  -url http://www.ibm.com/software/repositorymanager/com.ibm.java.jdk.v8/repository.xml

where storage_file is the path and file name of the storage file to be created, and user_ID and user_password are the universal IBM user ID and password that you use to access protected IBM software websites.

For example:

/opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential 
  -secureStorageFile /u/jane/IBM.software.store
  -userName jsmith01 -userPassword 732Ukelele
  -url http://www.ibm.com/software/repositorymanager/com.ibm.java.jdk.v8/repository.xml

Make sure that the credential storage file is readable by the Installation Manager user ID.

Verify that the product repository is available.
You do this by issuing the following Installation Manager command-line command.
```
imcl listAvailablePackages -repositories list_of_repository_locations
```
You should see one or more levels of the IBM SDK Java Technology Edition offering.
The list_of_repository_locations should include the path to the initial product repository and the paths to any additional service repositories. Separate URLs in the list_of_repository_locations with commas.
To use the web-based service repository, add the -useServiceRepository parameter and use the -secureStorageFile parameter to specify a credential storage file containing your IBM Software ID and password. For example:
```
imcl listAvailablePackages 
  -repositories /usr/lpp/InstallationManagerRepository/HBBO900
  -useServiceRepository  
  -secureStorageFile  /u/jane/IBM.software.store
```
Run the Installation Manager command-line tool to install IBM SDK, Java Technology Edition.
```
imcl install com.ibm.java.jdk.v8
  -installationDirectory installation_location
  -repositories list_of_repository_locations 
  -sharedResourcesDirectory shared_data_location
  -acceptLicense
  [-useServiceRepository -secureStorageFile storage_file]
  [-installFixes <all | recommended | none> ]
```
The -sharedResourcesDirectory parameter points to a directory in which Installation Manager will store artifacts from the repository during installation processing. This value is set the first time a product is installed with a particular Installation Manager. You can omit this parameter after the shared resources directory has been set.

If you do not specify the product version to be installed, Installation Manager will install the latest version of the product. For the WebSphere Java SDKs, you can prevent the installation of fixes by specifying -installFixes none, or you can install only recommended fixes by specifying -installFixes recommended. If you specify the product version to be installed, any fixes in the repository locations will only be installed if you specify -installFixes recommended or -installFixes all.

The -installFixes parameter does not apply to the IBM Java SDKs because individual fixes are packaged as updated fix packs rather than as interim fixes.
Product installation is complete when the Installation Manager completes without error messages.

Logs for the installation can be found in the logs subdirectory of the Installation Manager runtime data location.
When product installation is complete, unmount the product file system and remount it read-only for use by Liberty servers.