IBM Support

WebSphere Application Server for z/OS: Your first cup of Java is included!

Technical Blog Post


Abstract

WebSphere Application Server for z/OS: Your first cup of Java is included!

Body

 

Co-authored by: Shawfu Chen and  Steve Dittmar

As of IBM WebSphere Application Server V8.5, users on most platforms can choose to run on Java SDK 6.1 or 7.0, with support for 7.1 having been added more recently. Java SDK 6.1 continues to be shipped with, and updated automatically by,  the WebSphere Application Server fix packs. However, some users do not realize that Java SDK 7.x fix packs are not included in the WebSphere Application Server fix packs and thus is not automatically installed or kept up-to-date by the WebSphere Application Server fix packs. Instead, users must manually install and update Java SDK 7.x.


Acquiring and Installing Java SDK 7.x Fix Packs
There are three ways to install Java SDK 7.0 fix packs, but only two ways to install Java SDK 7.1 fix packs

 

SMP/E PTFs

Fix Central

IBM Live Repository

Java SDK 7.0

image

image

image

Java SDK 7.1

image

image

image


Note: If you are installing a Java SDK 7.0 fix pack with SMP/E, you must already have installed the initial repository that was included in your WebSphere Application Server 8.5.0.0 order or product media as optional material FMID HBJA700.  To read more about installing the initial levels, see the Obtaining product repositories for installing the product on z/OS topic in the IBM Knowledge Center.

Using Installation Manager, you can install fix packs for both Java SDK 7.0 and 7.1 either from a local repository or from the remote IBM live repository.  If you do not have a direct internet connection or have issues getting through a firewall to the IBM live repository, you must install using the local repository method.

 

Using a local repository:

Download the repositories for the new Java SDK level that you want.

  1. Go to Fix Central.
     
  2. Select WebSphere Application Server.
     
  3. Select your installed WebSphere Application Server version.
     
  4. Select z/OS.
     
  5. Filter the results to show only Fix Packs.
     
  6. Look for files with “IBMWASJAVA” in the name to identify available Java SDK fix packs.
     
  7. Download the fix pack files. Keep in mind that if there are multiple parts you must download them all. For example, if you are looking for SDK 7.1.1.0 you must download:
    • 7.1.1.0-WS-IBMWASJAVA-part1
    • 7.1.1.0-WS-IBMWASJAVA-part2

 

Fix Central should allow you to install any Java SDK level that was released with your WebSphere Application Server fix pack level or newer.  The following table lists which Java SDK fix packs were released with each WebSphere Application Server fix pack level for all WebSphere Application Server platforms:
http://www.ibm.com/support/docview.wss?uid=swg27005002

For example, Java SDK 7.1 fix pack 1 (a.k.a. 7.1.1), will be found in the SDK 7.1 table with a level name starting with SR1. From the table, we can see that it was released with WebSphere Application Server 8.5.5.3.

Need help “translating” the Java SDK level names?  Click here!

 

Perform the installation:

  1. Always start by updating IBM Installation Manager to the latest version. See the Installation Manager and Packaging Utility download links document
     
  2. Decompress the two parts into one single empty directory.  The resulting directory will be the repository from which you upgrade or install the Java SDK.  You can download an unzip utility from the z/OS ported tools web page.

    Important: Do not decompress the files into the WebSphere Application Server product installation file system!
     
  3. Run the IM command to install the Java SDK with the repository argument pointing to the new directory with the combined decompressed Java SDK contents. For example, to install a fix pack for Java SDK 7.1, the command would look like this example:
    imcl install com.ibm.websphere.IBMJAVA.v71
      -installationDirectory product_installation_location
      -repositories repository_dir_where_JavaSDK_jars_were_unzipped
      -acceptLicense

     
  4. (Optional) Switch the Java SDK run time that you want WebSphere Application Server to use (read below)

 

Using a remote repository:

Follow the instructions in the Installing IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1 topic within the IBM Knowledge Center.

 

Switching your Java SDK runtime

After installing a new Java SDK run time you must tell WebSphere Application Server to use it.  This setting can be made at the node or server level.  You can switch the active Java SDK in three ways:

  • Using the managesdk.sh script
    See the WebSphere Application Server documentation in the IBM Knowledge Center for more information about managesdk.sh
     
  • Using the WebSphere Application Server Administrative Console
    Server scope: Servers > Server Types > Application Server > ServerName > Java SDKs
    Node scope: System Administration > Nodes > NodeName > Java SDKs
     
  • Using the AdminTask SDK with wsadmin
    Server scope: AdminTask.setServerSDK()
    Node scope: AdminTask.setNodeDefaultSDK()
    See the WebSphere Application Server documentation in the IBM Knowledge Center for more information about the AdminSDKCmds command group

 

 

Java SDK Level Names

It is useful to understand some of the nomenclature that can be used to represent the level of a Java SDK so that you can recognize what you are installing or find what you want to install. Generally speaking, there is the short name, like v7.1.1, and there is the longer more detailed name, which often exists among a host of other information like build date, platform, bit level, interim fix list, and so on. The output of the java -version command, for example, displays the long hand form of the level information and much more.

The short hand of a level is written as vA.B.C.D, where

A= version (v)

B= release (r)

C= service refresh (SR)

D= fix pack (FP)

So v7.1.1 is equivalent to saying version 7 release 1 service refresh 1 (with no fix packs).


Among the longer more detailed level information, you will generally find the SR and FP represented in the build name as well as in the fix string that is often printed after the build name, such as in the Java 7.0.6.1 level that was delivered with WebSphere Application Server 8.5.5.2:

pmz3170sr6fp1ifix-20140220_01(SR6 FP1+IX90136+IX90137)
 

At the following URL you will find that v7.1.1 is found in the Java 7.1 table as:

pmz3170_27sr1ifix-20140713_01(SR1+IX90150+IX90144+IV60711+IV60971+IV61564+IV62037+IV62044)

Note: In some cases, you might also see v7.0 and v7.1 used interchangeably with 1.7.0 and 1.7.1, respectively.

 

*** Wondering how to do all of this in regards to the Liberty Profile?  Watch for another blog entry about that, coming soon!

 

Thanks for reading!

Shawfu Chen & Steve Dittmar
WebSphere Application Server for z/OS L2 Support

 

Coffee Beans (modified) credit: (cc) Some rights reserved by Pen Waggener

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}}]

UID

ibm11080627