This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

Installing Liberty fix packs on distributed operating systems using the command line

You can use the IBM® Installation Manager command line to update the product with the fix packs that are available for WebSphere® Application Server Liberty Core.

Before you begin

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

Liberty Repository[8.5.5.6 or later]If you want to install Liberty assets from local directory-based repositories or an instance of the Liberty Asset Repository Service, configure the repositories. For more information about the Liberty asset repositories, see Installing assets using Installation Manager.

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. You can create and point to a set of custom repositories that include only the specific fixes that you want to install. 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 installFixes attribute in a response file.

About this task

[8.5.5.4 or later]To install Version 8.5.5.4 and later of Liberty, you must have IBM Installation Manager Version 1.6.2 or later.

Procedure

  1. For a list of interim fixes and fix packs that are available for WebSphere Application Server Liberty Core 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 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 note of the name of the fix pack that you would like to install.
  2. Update WebSphere Application Server LibertyCore 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 Core 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 pack from a service repository, perform the following actions:
      1. Log on to your system.
      2. Create Installation Manager credential-storage and master-password files that contain your IBM software user ID and password. These files enable you to access the repository and protected IBM software websites.

        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: For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In previous versions, the -keyring and -password options are used to access credentials in a keyring file. These options are 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.
      3. Stop all servers and applications on the WebSphere Application Server Liberty Core installation that is being updated.
      4. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.
      5. Install the fix pack.
        For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platforms
        ./imcl install offering_ID_offering_version,optional_feature_ID
          -repositories source_repository 
          -installationDirectory offering_installation_location
          -secureStorageFile storage_file -masterPasswordFile master_password_file
          -acceptLicense
        For Windows platforms
        imcl.exe install offering_ID_offering_version,optional_feature_ID
          -repositories source_repository 
          -installationDirectory offering_installation_location
          -secureStorageFile storage_file -masterPasswordFile master_password_file
          -acceptLicense
        where offering_ID is the offering ID that is listed in WebSphere Application Server product offerings for supported operating systems.
        Tips:
        • 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.
        • Liberty Repository[8.5.5.2 or later]You can specify additional features to install from the Liberty Repository. For a list of Liberty Repository assets, see the downloads page on WASdev.net.
          Note: To install Liberty Repository assets, you must have access to the internet, and you must have IBM Installation Manager Version 1.6.2 or later.
          If you want to install additional features, specify the following properties in the command line. Note that the feature short names, such as FeatureA, are separated by double commas:
          -properties user.feature=FeatureA,,FeatureB,,FeatureC,user.accept.license=true
          For Version 8.5.5.5 and later, user.accept.license=true is not required.
          Liberty Repository[8.5.5.4 or later]Beginning with Version 8.5.5.4, the Extended Programming Models are available to download from the Liberty Repository as the extendedPackage-1.0 addon. This addon provides a rich set of programming models such as Web Services, JMS (including Message-Driven Beans), and MongoDB 2.0. To install the addon, specify the extendedPackage-1.0 addon on the user.addon option of the -properties parameter:
          imcl install com.ibm.websphere.liberty.ND.v85
          -properties user.accept.license=true,user.addon=extendedPackage-1.0
          -installationDirectory D:\IBM\Liberty -acceptLicense
          -repositories D:\IBM\LibertyRepo
          -sharedResourcesDirectory D:\IBM\IMShared
          -showProgress
          Liberty Repository[8.5.5.6 or later]You can also install assets from instances of the Liberty Asset Repository Service or local directory-based repositories. For more information about these asset repositories, see Installing assets using Installation Manager. Add the repository on the -repositories parameter. The repositories are accessed in the order that they are specified. By default, the Liberty Repository is the last of the repositories that are accessed during installation. To disable access to the Liberty Repository, on the -properties parameter, set the user.useLibertyRepository option to false.[8.5.5.8 or later]
          imcl install com.ibm.websphere.liberty.v85
          -properties user.useLibertyRepository=false,user.addon=extendedPackage-1.0,user.feature=portlet-2.0
          -installationDirectory D:\IBM\Liberty -acceptLicense
          -repositories D:\IBM\LibertyProductRepo,https://your_onprem_asset_repo_url,D:\IBM\LocalAssetRepo,D:\IBM\LocalAssetRepo2.zip
          -sharedResourcesDirectory D:\IBM\IMShared
          -showProgress

          To learn more about the Liberty Repository and the assets it contains, see Liberty Repository.

        [8.5.5.4 or later]Note: If you do not have the Extended Programming Model installed prior to updating to Version 8.5.5.4, you might encounter the following error during the update:
        java.io.IOException: Too many open files
                at java.io.File.createNewFile(File.java:894)
        To resolve this problem, increase the number of files using the ulimit command; for example:
        ulimit -n 8192
      6. List all installed packages to verify the installation:
        For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platforms
        ./imcl listInstalledPackages -long
        For Windows platforms
        imcl.exe listInstalledPackages -long
    • Download the 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-pack file contains an Installation Manager repository for the fix pack and usually has a .zip extension. After downloading and extracting the fix-pack file, use Installation Manager to update WebSphere Application Server Liberty Core 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 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 file in binary format to the system on which it is installed.
        12. Extract the compressed repository files to a directory on your system.
      2. To install a fix pack from a downloaded file, perform the following actions:
        1. Log on to your system.
        2. Stop all servers and applications on the WebSphere Application Server Liberty Core installation that is being updated.
        3. Change to the Installation_Manager_binaries/eclipse/tools directory, where Installation_Manager_binaries is the installation root directory for the Installation Manager.
        4. Install the fix pack.
          For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platforms
          ./imcl install offering_ID_offering_version,optional_feature_ID
            -installationDirectory offering_installation_location
            -repositories location_of_expanded_files
            -acceptLicense
          For Windows platforms
          imcl.exe install offering_ID_offering_version,optional_feature_ID
            -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.
          • You can add a list of features that are separated by commas.
        5. Optional: List all installed packages to verify the installation:
          For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platforms
          ./imcl listInstalledPackages -long
          For Windows platforms
          imcl.exe listInstalledPackages -long

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=twlp_ins_upgrade_cl
File name: twlp_ins_upgrade_cl.html