[z/OS]

Installing IBM WebSphere SDK Java Technology Edition Version 7.x

The product code for IBM® WebSphere® SDK Java Technology Edition Version 7.x is installed using IBM Installation Manager Version 1.5.2 or later.

Before you begin

  1. 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.

  2. Install a copy of WebSphere Application Server for z/OS Version 8.5.
  3. Obtain the product repository for IBM WebSphere SDK Java Technology Edition Version 7.x. The repository can be mounted read-only.

About this task

This article provides information on installing IBM WebSphere SDK Java Technology Edition Version 7.x with IBM WebSphere Application Server for z/OS.

[8.5.5.0 or later] If you have IBM WebSphere Application Server Liberty for z/OS and you want to add IBM WebSphere SDK Java Technology Edition Version 7.x for Liberty, see Installing IBM WebSphere SDK Java Technology Edition Version 7.0 for Liberty.

[8.5.5.2 or later] You can download and install IBM WebSphere SDK Java Technology Edition Version 7.1. This version and higher versions are only available from the web. You have the following installation options:
  • Download the installation files from the IBM Fix Central website and use a local installation.
  • Access the live repositories and use your IBM Software ID for a web-based installation.

Procedure

  1. Choose the installed copy of WebSphere Application Server for z/OS Version 8.5 onto which you will install IBM WebSphere SDK Java Technology Edition Version 7.x.
  2. Mount the product file system for this copy of WebSphere Application Server for z/OS Version 8.5 at the same location at which it was originally installed with IBM Installation Manager.

    The file system will require a minimum of 20,000 tracks (3390) or 1,100 megabytes of free disk space to install IBM WebSphere SDK Java Technology Edition Version 7.x.

    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.v85.SBBOHFS -type ZFS
      -mountpoint /usr/lpp/zWebSphere/V8R5

    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.

  3. 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
  4. If you plan to use the web-based service repository, create a keyring file on z/OS to access this repository by running the imutilsc command. [8.5.5.1 or later]
    installation_manager_binaries_directory/eclipse/tools/imutilsc saveCredential 
      -keyring keyring_file
      -userName user_ID -userPassword user_password
      -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v70/repository.xml 
    [8.5.5.2 or later]
    installation_manager_binaries_directory/eclipse/tools/imutilsc saveCredential 
      -keyring keyring_file
      -userName user_ID -userPassword user_password
      -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v71/repository.xml 
    where keyring_file is the path and file name of the keyring 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:
    [8.5.5.1 or later]
    /opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential 
      -keyring /u/jane/IBM.software.keyring
      -userName jsmith01 -userPassword 732Ukelele
      -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v70/repository.xml 

    [8.5.5.2 or later]
    /opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential 
      -keyring /u/jane/IBM.software.keyring
      -userName jsmith01 -userPassword 732Ukelele
      -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v70/repository.xml 

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

    Note: Starting in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. When you use Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

    There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.

    For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.

  5. 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 WebSphere SDK Java Technology Edition Version 7.x offering:
    • [8.5.5.1 or later] com.ibm.websphere.IBMJAVA.v70
    • [8.5.5.2 or later] com.ibm.websphere.IBMJAVA.v71

    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 -keyring parameter to specify a keyring file containing your IBM Software ID and password. For example:
    imcl listAvailablePackages 
      -repositories /usr/lpp/InstallationManagerRepository/HBBO850
      -useServiceRepository  
      -keyring  /u/jane/IBM.software.keyring
    Note: Starting in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. When you use Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

    There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.

    For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.

  6. Run the Installation Manager command-line tool to install IBM WebSphere SDK Java Technology Edition Version 7.x. [8.5.5.1 or later]
    imcl install com.ibm.websphere.IBMJAVA.v70
      -installationDirectory installation_location
      -repositories list_of_repository_locations 
      -sharedResourcesDirectory shared_data_location
      -acceptLicense
      [-useServiceRepository -keyring keyring_file]
      [-installFixes <all | recommended | none> ]
    [8.5.5.2 or later]
    imcl install com.ibm.websphere.IBMJAVA.v71
      -installationDirectory installation_location
      -repositories list_of_repository_locations 
      -sharedResourcesDirectory shared_data_location
      -acceptLicense
      [-useServiceRepository -keyring keyring_file]
      [-installFixes <all | recommended | none> ]

    The -installationDirectory needs to point to a WebSphere Application Server Version 8.5 install directory where WebSphere Application Server Version 8.5 has already been installed.

    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 along with any fixes in the repository locations. You can prevent the installation of fixes by specifying -installFixes none or 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.

  7. 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.

  8. When product installation is complete, unmount the product file system and remount it read-only for use by WebSphere Application Server nodes and servers.

What to do next

You can now install other WebSphere Application Server components or configure an application-serving environment.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-zos&topic=tins_installation_zos_installing_jdk7
File name: tins_installation_zos_installing_jdk7.html