Fix Pack 8550

Installing Liberty interim fixes and fix packs on z/OS operating systems

Fix packs contain bundled service to bring WebSphere® Application Server Liberty for z/OS® up to a new level. Interim fixes provide corrective service for specific known problems. You can use IBM® Installation Manager to update the offering with the fixes that are available for your service level of WebSphere Application Server Liberty for z/OS.

Before you begin

Contact the IBM Software Support Center for information about updates for WebSphere Application Server Liberty for z/OS. For more information about upgrades, see the WebSphere Application Server for z/OS: Program Directory. The most current information is available from the IBM Software Support Center and Fix Central.

IBM Installation Manager is used to apply maintenance to WebSphere Application Server Liberty for z/OS.

Tip: Although almost all of the instructions in this section of the information center will work with earlier versions of IBM Installation Manager, the information here is optimized for users who have installed or upgraded to Installation Manager Version 1.5.2 or later.

Procedure

  1. Use Installation Manager to apply the required maintenance to your dataset and file-system structure.
    1. For a list of fixes that are available for WebSphere Application Server Liberty for z/OS and specific information about each fix, perform the following actions.
      1. Go to Fix Central.
      2. Select WebSphere as the product group.
      3. Select WebSphere Application Server Liberty for z/OS as the product.
      4. Select the version of the offering to be updated.
      5. Select z/OS as the platform, and click Continue.
      6. Select Browse for fixes, and click Continue.
      7. Click More Information under each fix to view information about the fix.
      8. Recommendation: Make a list of the names of the fixes that you would like to install.
    2. Update WebSphere Application Server Liberty for z/OS with the fixes using one of the following procedures.
      • To update the offering with interim fixes or fix packs, access the live service repository that contains the fixes and use web-based updating.
        Use Installation Manager on your local system to update WebSphere Application Server Liberty for z/OS with the interim fixes from the live web-based service repositories.
        • For the live service repositories, use the same URLs as those used for the generally available product-offering repositories during installation. These URLs are based on the following pattern:
          http://www.ibm.com/software/repositorymanager/offering_ID
          where offering_ID is the offering ID that you can find in WebSphere Application Server product offerings for supported operating systems.
        • These locations do not contain web pages that you can access using a web browser. They are remote web-based repository locations that you specify for Installation Manager so that it can maintain the offering.
        To install a fix from a service repository, perform the following actions:
        1. Mount the product file system, read and write, at the path at which it was originally mounted with Installation Manager.
        2. If you do not already have Installation Manager credential-storage and master-password files containing your IBM software user ID and password, create files that will allow you to access the repository.
          Note: These are the credentials that you use to access protected IBM software websites.
          Create a credential-storage file and master-password file:
          imutilsc saveCredential 
            -secureStorageFile storage_file -masterPasswordFile master_password_file
            -userName IBM_software_ID
            -userPassword IBM_software_password
            -url repository_URL
          Tip: When creating a credential-storage file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.
          Note: When you use Installation Manager Version 1.6.2 and later, you should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In versions of Installation Manager earlier than Version 1.6.2, the -keyring and -password options were used to access credentials in a keyring file. These options were deprecated in Version 1.6.2. There is no migration path from keyring files to storage files because of the differences in the file structures. 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.
        3. From the Installation Manager user ID, perform the following actions:
          1. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.
          2. Install the fix.
            To install an interim fix, use this command:
            imcl install fix_name
              -installationDirectory offering_installation_location
              -repositories repository_URL
              -secureStorageFile storage_file -masterPasswordFile master_password_file
            To install a fix pack, use this command:
            imcl install offering_ID_offering_version
              -installationDirectory offering_installation_location
              -repositories repository_URL
              -secureStorageFile storage_file -masterPasswordFile master_password_file
              -acceptLicense
            Tips:
            • The offering_ID is the offering ID that is listed in WebSphere Application Server product offerings for supported operating systems.
            • The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.5.20110503_0200 for example).
              • If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
              • If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.
              The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:
              imcl listAvailablePackages -repositories source_repository
            • You can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.
              • If the offering version is not specified, the -installFixes option defaults to all.
              • If the offering version is specified, the -installFixes option defaults to none.
          3. Optional: List all installed packages to verify the installation:
            imcl listInstalledPackages -long
      • To update the offering with interim fixes or fix packs, download the files that contain the fixes from Fix Central and use local updating.
        You can download compressed files that contain the fixes from Fix Central. Each compressed fix file contains an Installation Manager repository for the fix and usually has a .zip extension. After downloading the fix files, you can use Installation Manager to update WebSphere Application Server Liberty for z/OS with the fixes.
        1. To download the fixes, perform the following actions:
          1. Go to Fix Central.
          2. Select WebSphere as the product group.
          3. Select WebSphere Application Server Liberty for z/OS as the product.
          4. Select the version of the offering to be updated.
          5. Select z/OS as the platform, and click Continue.
          6. Select Browse for fixes, and click Continue.
          7. Select the fixes that you want to download, and click Continue.
          8. Select your download options, and click Continue.
          9. Click I agree to agree to the terms and conditions.
          10. Click Download now to download the fixes.
          11. Transfer the compressed fix files in binary format to the z/OS system on which they will be installed.
          12. If you are installing a fix pack, extract the compressed repository files to a directory on your system.
        2. To install a fix from a downloaded file, perform the following actions:
          1. Mount the product file system, read and write, at the path at which it was originally mounted with Installation Manager.
          2. From the Installation Manager user ID, perform the following actions:
            1. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.
            2. Install the fix.
              To install an interim fix, use this command:
              imcl install fix_name 
                 -installationDirectory offering_installation_location
                 -repositories compressed_file
              To install a fix pack, use this command:
              imcl install offering_ID_offering_version
                -installationDirectory offering_installation_location
                -repositories location_of_expanded_files
                -acceptLicense
              Tips:
              • The offering_ID is the offering ID that is listed in WebSphere Application Server product offerings for supported operating systems.
              • The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.5.20110503_0200 for example).
                • If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
                • If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.
                The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:
                imcl listAvailablePackages -repositories source_repository
              • You can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.
                • If the offering version is not specified, the -installFixes option defaults to all.
                • If the offering version is specified, the -installFixes option defaults to none.
            3. Optional: List all installed packages to verify the installation:
              imcl listInstalledPackages -long
      • To update the offering with fix packs, apply fix-pack PTFs to the SMP/E-managed repository and use local updating.

        You can add a new fix-pack level of the offering to the SMP/E-managed repository that contains the base offering by applying PTFs for the fix pack to the repository. See the WebSphere Application Server Liberty for z/OS service page for a listing of available fix packs and PTFs. After installing the PTFs, you can use Installation Manager to update WebSphere Application Server Liberty for z/OS with the new fix pack.

        1. Apply the PTFs for the fix pack to the WebSphere Application Server Liberty for z/OS repository (FMID HBBO850).
        2. Perform the following actions:
          1. Mount the product file system, read and write, at the path at which it was originally mounted with Installation Manager.
          2. From the Installation Manager user ID, perform the following actions:
            1. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.
            2. Use the imcl install command to install the new fix-pack level. For example:
              imcl install com.ibm.websphere.liberty.zOS.v85_offering_version
                -installationDirectory offering_installation_location
                -repositories /usr/lpp/InstallationManagerRepository/HBBO850
                -acceptLicense
              Tips:
              • offering_version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository. For example:
                imcl listAvailablePackages 
                  -repositories /usr/lpp/InstallationManagerRepository/HBBO850
              • When the offering is installed for use with WebSphere Application Server Liberty for z/OS, it is installed into the WebSphere Application Server Liberty for z/OS product file system.
            3. Optional: List all installed packages to verify the installation:
              imcl listInstalledPackages -long

    For more information on updating WebSphere Application Server Liberty for z/OS, see Updating and uninstalling Liberty on z/OS.

  2. Remount the product file system at its production location.

    The file system should normally be mounted read-only.

  3. Perform any other migration actions as instructed in fix or APAR cover letters.
  4. Start your server(s) to complete any necessary post-installation tasks.

    At server startup, the post-installer will run automatically against each node in order to update the configuration file system to the new service level.

    Note: In Network Deployment cells, the deployment manager node must be at the same or a later service level than the cell's application server nodes. You must ensure that the deployment manager node is upgraded to the new service level.

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_install_fixes_z
File name: twlp_ins_install_fixes_z.html