Fix Pack 8550

Installing WebSphere Application Server Liberty for z/OS

The product code for WebSphere® Application Server Liberty for z/OS® is installed using IBM® Installation Manager.

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.

Obtain the product repository for WebSphere Application Server Liberty for z/OS. The repository can be mounted read-only.

Procedure

  1. Choose an installation location for this copy of WebSphere Application Server Liberty for z/OS.

    This copy of the product must be mounted at this location every time Installation Manager accesses it to install, uninstall, or modify it. This does not have to be the same location at which the product will be mounted when used in production.

    Installation Manager requires that every installed product or group of products have its own installation location.

  2. Mount an empty file system read/write at this location.
    It will require a minimum of:
    • 72 megabytes (2000 tracks (3390)) for WebSphere Application Server Liberty for z/OS with no optional features
    • 132 megabytes (4000 tracks (390)) for WebSphere Application Server Liberty for z/OS with all optional features
    • 426 megabytes (9000 tracks (3390)) for WebSphere Application Server Liberty for z/OS with all optional features and WebSphere SDK Java™ Technology Edition Version 7.0 for Liberty
    Set the ownership for the file system to that of the Installation Manager user ID, and set the permissions to allow group-write if it will be access by a group-mode Installation Manager. For example:
    chown IMADMIN:IMGROUP /usr/lpp/zWebSphere/V8R5
    
    chmod 775 /usr/lpp/zWebSphere/V8R5
    You can use the zCreateFileSystem.sh script in the eclipse/tools subdirectory of the Installation Manager binaries location to create this file system. For example:
    cd /InstallationManager/bin/eclipse/tools
    
    zCreateFileSystem.sh -name WAS.v85.SBBOHFS -type ZFS 
      -megabytes 1800 200 -volume PRV005
      -mountpoint /usr/lpp/zWebSphere/V8R5
      -owner IMADMIN -group IMGROUP
    If you installed the initial product repository with SMP/E, you can use sample job BBO1CFS in the SBBOJCL dataset to allocate and mount this 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.
    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.liberty.zOS.v85/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:
    /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.liberty.zOS.v85/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. For more information on using the -keyring and -password options to store credentials in a keyring file, see the Installation Manager Version 1.5 Information Center.
  5. Verify that the product repositories are 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 WebSphere Application Server Liberty for z/OS offering, com.ibm.websphere.liberty.zOS.v85.

    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. For more information on using the -keyring and -password options to store credentials in a keyring file, see the Installation Manager Version 1.5 Information Center.
  6. Read the product license, which can be found in the lafiles subdirectory of the product repository.
  7. Run the Installation Manager command-line tool to install the WebSphere Application Server Liberty for z/OS product.
    imcl install com.ibm.websphere.liberty.zOS.v85
      -installationDirectory installation_location
      -repositories list_of_repository_locations 
      -sharedResourcesDirectory shared_data_location 
      -acceptLicense
      [-useServiceRepository -keyring  keyring_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. This directory should have at least 30,000 tracks of free space. You can omit this parameter after the shared resources directory has been set.

    By specifying -acceptLicense, you accept the terms of the product license. 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 offering.

    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.

    You can also follow the package name (and version) with a comma and a list of optional features separated by commas. The following features are available for WebSphere Application Server Liberty for z/OS. The keyword name for each feature is provided in parentheses.
    • Embeddable EJB container and JPA client (embeddablecontainer)

      This option installs the embeddable EJB container and JPA client.

      The embeddable EJB container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition (SE) environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

      The JPA client can be used with the embeddable EJB container to provide Java Persistence API capability in a Java SE environment.

    • Extended Programming Models (extprogmodels)

      The Extended Programming Models feature provides a rich set of programming models such as Web Services, JMS (including Message-Driven Beans), and Mongo 2.0.

    Notes:
    • When you install a new copy of the WebSphere Application Server Liberty for z/OS and do not specify the features to be installed, the following features are installed by default:
      • embeddablecontainer
      • extprogmodels
    • If any features are listed, the normal list of default features is ignored and only the listed features are installed.

    If you installed the initial product repository with SMP/E, you can use sample job BBO1INST in the SBBOJCL dataset to perform the product installation.

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

  9. When product installation is complete, unmount the product filesystem and remount it read-only for use by Liberty servers.

Icon that indicates the type of topic Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_ins_installation_zos_installing
File name: twlp_ins_installation_zos_installing.html