Fix Pack 8550

Installing Liberty fix packs on IBM i operating systems using the command line

Product fix packs contain bundled service to bring WebSphere® Application Server Liberty - Express® up to a new product level. Interim fixes provide corrective service for specific known problems. You can use the IBM® Installation Manager command-line function to update the product with the fixes that are available for your service level of WebSphere Application Server Liberty - Express installation.

Before you begin

Contact the IBM Software Support Center for information about updates for WebSphere Application Server for IBM i. The most current information is available from the IBM Software Support Center and Fix Central.

IBM Installation Manager is used to apply product maintenance to WebSphere Application Server for IBM i.

Tip: As an alternative to the procedure that is described in this article, Installation Manager allows you to use the updateAll command in a response file or on the command line to search for and update all installed packages. Use this command only if you have full control over which fixes are contained in the targeted repositories. If you create and point to a set of custom repositories that include only the specific fixes that you want to install, you should be able to use this command confidently. If you enable searching service repositories or install fixes directly from other live web-based repositories, then you might not want to select this option so that you can select only the fixes that you want to install using the -installFixes option with the install command on the command line or the installFixesattribute in a response file.

About this task

Use this procedure whenever you want to apply a new fix pack to your system.
Tip: You can also install fix packs using response files with Installation Manager. For information on creating and using response files, read Installing Liberty fix packs on IBM i operating systems using response files and the IBM Installation Manager Information Center.
Fix Pack 8550 Restriction: You cannot use the iRemoteInstall command to install a fix pack.

Procedure

  1. For a list of fixes that are available for WebSphere Application Server Liberty - Express installation 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 - Express as the product.
    4. Select the installed version.
    5. Select your operating system 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 - Express installation with the fix pack using one of the following procedures.
    • Access the live service repository that contains the fix pack, and use web-based updating.
      Use Installation Manager on your local system to update WebSphere Application Server Liberty - Express 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 product.
      To install a fix from a service repository, perform the following actions:
      1. 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.
        For information on creating credential-storage and master-password files for Installation Manager, read the IBM Installation Manager Information Center.
        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.
      2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
      3. Stop all servers and applications on the WebSphere Application Server Liberty - Express installation that is being updated.
      4. On a CL command line, run the STRQSH command to start the Qshell command shell.
      5. Make sure that the umask is set to 022.
        To verify the umask setting, issue the following command:
        umask
        To set the umask setting to 022, issue the following command:
        umask 022
      6. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.

        On IBM i systems, the root directory for the Installation Manager is /QIBM/ProdData/InstallationManager.

      7. Install the fix pack.
        ./imcl install offering_ID_offering_version,optional_feature_ID
          -repositories source_repository 
          -installationDirectory offering_installation_location
          -secureStorageFile storage_file -masterPasswordFile master_password_file
          -acceptLicense
        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.
        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.
        • You can add a list of features that are separated by commas.
        • If you obtained the fix pack by installing the WebSphere Application Server group PTF, you can use the local fix-pack repositories to install the fix pack.

          For information about the local fix-pack repositories, see file /QIBM/WAS/WASFixpacks/ReadmeV85.html or /QIBM/WAS/WASFixpacks/ReadmeV85.txt.

      8. Optional: List all installed packages to verify the installation:
        ./imcl listInstalledPackages -long
    • Download a file that contains the fix pack from Fix Central, and use local updating.
      You can download a compressed file that contains the fix pack from Fix Central. Each compressed fix file contains an Installation Manager repository for the fix pack and usually has a .zip extension. After downloading the fix file, you can use Installation Manager to update WebSphere Application Server Liberty - Express with the fix pack.
      1. To download the fix pack, perform the following actions:
        1. Go to Fix Central.
        2. Select WebSphere as the product group.
        3. Select WebSphere Application Server Liberty - Express as the product.
        4. Select the installed version.
        5. Select your operating system as the platform, and click Continue.
        6. Select Browse for fixes, and click Continue.
        7. Select the fix pack 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 fix pack.
        11. Transfer the compressed fix file in binary format to the IBM i systems on which it will be installed.
        12. Extract the compressed repository file to a directory on your system.
      2. To install a fix pack from a downloaded file, perform the following actions:
        1. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
        2. Stop all servers and applications on the WebSphere Application Server Liberty - Express installation that is being updated.
        3. On a CL command line, run the STRQSH command to start the Qshell command shell.
        4. Make sure that the umask is set to 022.
          To verify the umask setting, issue the following command:
          umask
          To set the umask setting to 022, issue the following command:
          umask 022
        5. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.

          On IBM i systems, the root directory for the Installation Manager is /QIBM/ProdData/InstallationManager.

        6. Install the fix pack.
          ./imcl install offering_ID_offering_version,optional_feature_ID
            -repositories location_of_expanded_files
            -installationDirectory offering_installation_location
            -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.
          • You can add a list of features that are separated by commas.
          • If you obtained the fix pack by installing the WebSphere Application Server group PTF, you can use the local fix-pack repositories to install the fix pack.

            For information about the local fix-pack repositories, see file /QIBM/WAS/WASFixpacks/ReadmeV85.html or /QIBM/WAS/WASFixpacks/ReadmeV85.txt.

        7. Optional: List all installed packages to verify the installation:
          ./imcl listInstalledPackages -long

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-express-iseries&topic=twlp_ins_upgrade_is_cl
File name: twlp_ins_upgrade_is_cl.html