[z/OS]

Installing the Web 2.0 and Mobile Toolkit on z/OS

The product code for the Web 2.0 and Mobile Toolkit 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. Obtain the product repository for the Web 2.0 and Mobile Toolkit. The repository can be mounted read-only.

Procedure

  1. Choose an installation location for the Web 2.0 and Mobile Toolkit.

    This copy of the offering 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 offering 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 3200 tracks (3390) or 150 megabytes of free disk space. 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 accessed by a group-mode Installation Manager. For example:
    chown IMADMIN:IMGROUP /usr/lpp/Web2Mobile/V11
    
    chmod 775 /usr/lpp/Web2Mobile/V11
    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.SWEBHFS -type ZFS 
      -megabytes 150 30 -volume PRV005
      -mountpoint /usr/lpp/Web2Mobile/V11
      -owner IMADMIN -group IMGROUP
  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.W2MTK.v11/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:
    /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.W2MTK.v11/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 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 Installation Manager Version 1.6 documentation.

  5. Verify that the 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 Web 2.0 and Mobile Toolkit offering, com.ibm.websphere.W2MTK.v11.

    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 /opt/repository/W2MTK
      -useServiceRepository  
      -keyring  /u/jane/IBM.software.keyring
    Note:

    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 Installation Manager Version 1.6 documentation.

  6. Read the product license, which can be found in the lafiles subdirectory of the repository.
  7. Run the Installation Manager command-line tool to install the Web 2.0 and Mobile Toolkit.
    imcl install com.ibm.websphere.W2MTK.v11
      -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. 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.

    By specifying -acceptLicense, you accept the terms of the product license contained in the repository.

  8. 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 installation is complete, unmount the product file system and remount it read-only for use by WebSphere® Application Server nodes and servers.
Task topic    

Terms and conditions for product documentation | Feedback

Last updated: January 29, 2018 10:59 AM GMT-06:00
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v850webmob&product=was-nd-mp&topic=tweb_ins_installation_zos_installing
File name: tweb_ins_installation_zos_installing.html