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 response files

You can update WebSphere® Application Server Liberty Core to a later version using Installation Manager response files.

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.

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 topic, use the Installation Manager 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. 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 if you 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.

Procedure

  1. To obtain a list of interim fixes and fix packs that are available for WebSphere Application Server Liberty Core 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 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. 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.
      Perform the following actions:
      1. Log on to your system.
      2. Create files that enable you to access the repository. Installation Manager credential-storage and master-password files contain your IBM software user ID and password and enable you to access 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, you should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In previous versions of Installation Manager, 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 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 using a response file.
        For example:
        • For Windows platforms Administrator or non-administrator:
          imcl.exe -acceptLicense 
            input C:\temp\update_response_file.xml 
            -log C:\temp\update_log.xml 
            -secureStorageFile C:\IM\credential.store -masterPasswordFile C:\IM\master_password_file.txt
        • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsAdministrator:
          ./imcl -acceptLicense 
            input /var/temp/update_response_file.xml 
            -log /var/temp/update_log.xml 
            -secureStorageFile /var/IM/credential.store -masterPasswordFile /var/IM/master_password_file.txt
        • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsNon-administrator:
          ./imcl -acceptLicense 
            input user_home/var/temp/update_response_file.xml 
            -log user_home/var/temp/update_log.xml 
            -secureStorageFile user_home/var/IM/credential.store -masterPasswordFile user_home/var/IM/master_password_file.txt
    • 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 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 will be installed.
        12. Extract the compressed repository files to a directory on your system.
      2. Perform the following actions:
        1. Log on to your system.
        2. If the repository requires a username and password, create a credential-storage file to access this repository.

          For more information on creating a credential-storage file 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.
        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 using a response file.
          For example:
          • For Windows platformsAdministrator or non-administrator:
            imcl.exe -acceptLicense 
              input C:\temp\update_response_file.xml 
              -log C:\temp\update_log.xml 
              -secureStorageFile C:\IM\credential.store -masterPasswordFile C:\IM\master_password_file.txt
          • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsAdministrator:
            ./imcl -acceptLicense 
              input /var/temp/update_response_file.xml 
              -log /var/temp/update_log.xml 
              -secureStorageFile /var/IM/credential.store -masterPasswordFile /var/IM/master_password_file.txt
          • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsNon-administrator:
            ./imcl -acceptLicense 
              input user_home/var/temp/update_response_file.xml 
              -log user_home/var/temp/update_log.xml 
              -secureStorageFile user_home/var/IM/credential.store -masterPasswordFile user_home/var/IM/master_password_file.txt

Example

For Windows platformsThe following is an example of a response file for updating the product to a later version.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input>
<server>
  <repository location='https://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85'/>
</server>
<profile id='WebSphere Liberty V8.5' 
  installLocation='C:\Program Files\IBM\WebSphere\Liberty'>
</profile>
<install modify='false'>
  <offering profile='WebSphere Liberty V8.5' id='com.ibm.websphere.liberty.v85' 
    version='8.5.5.20101025_2108'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='C:\Program Files\IBM\IMShared'/>
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
</agent-input>
Tips:
  • The profile ID (<profile . . . id='profile_ID' . . . .> and <offering . . . profile='profile_ID' . . . .>) can be found when you run the imcl listInstallationDirectories -verbose command from the eclipse/tools subdirectory in the directory where you installed Installation Manager. It is the same as the package group's name.
  • The offering ID (<offering . . . id='offering_ID' . . . .>) can be found in WebSphere Application Server product offerings for supported operating systems.
  • The version is a specific version of the offering to install (8.5.5.20101025_2108 for example). This specification is optional.
    • If version is not specified, the latest version of the offering and all interim fixes for that version are installed.
    • If 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.
  • Liberty Repository[8.5.5.2 or later]You can specify additional assets to install from the Liberty Repository. For a list of Liberty Repository assets, see the downloads page on WASdev.net.

    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. Previous versions of Installation Manager do not have the option to install Liberty Repository assets. If you use a response file and did not update Installation Manager to Version 1.6.2 or later, the assets that you specify in the response file are ignored during installation.

    If you want to install additional features, specify two extra data key elements in your response file. You can use either the symbolic name or the short name.

    The following example installs the Portlet Container and Portlet Serving features using the symbolic name.
    <data key='user.feature' value='com.ibm.websphere.appserver.portlet-2.0,,com.ibm.websphere.appserver.portletserving-2.0'/>
    <data key='user.accept.license' value='true'/>
    The following example installs the Portlet Container and Portlet Serving features using the short name:
    <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/>
    <data key='user.accept.license' value='true'/>
    [8.5.5.5 or later]For Version 8.5.5.5 and later, user.accept.license=true is not required.
    [8.5.5.3 or later]Note: If you are updating to Version 8.5.5.3 and previously installed Liberty Repository features but do not currently have a connection to the IBM WebSphere Liberty Repository, you cannot update using a response file. Instead, update the product by running the imcl command and specifying the user.feature="" parameter.
    Liberty Repository[8.5.5.4 or later]Beginning with Version 8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 addon, or install the individual features that you need from the Liberty Repository. See the following topics for more information:
    The following example installs the Extended Programming Models using the user.addon parameter and the Portlet Container and Portlet Serving features using the user.feature parameter with short names:
    <data key='user.addon' value='extendedPackage-1.0'/>
    <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/>
    <data key='user.accept.license' value='true'/>
    [8.5.5.5 or later]For Version 8.5.5.5 and later, user.accept.license=true is not required.
    Liberty Repository[8.5.5.6 or later]You can also install assets from an instance of the Liberty Asset Repository Service or local directory-based repositories. For more information, see Installing assets using Installation Manager. Add the repository on repository elements. If Installation Manager does not recognize the repository, point directly to the repository.config file. When you install assets, the repositories are accessed in the order that you specify them.
    <server>
    <repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85" />
    <repository location="https://your_onprem_asset_repo_url" />
    <repository location="D:\IBM\LocalAssetRepo" />
    [8.5.5.8 or later]<repository location="D:\IBM\LocalAssetRepo2.zip" />
    </server>
    By default, the Liberty Repository is the last of the repositories that are accessed during installation. To disable access to the Liberty Repository, set the user.useLibertyRepository parameter to false:
    <data key='user.addon' value='extendedPackage-1.0'/>
    <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/>
    <data key='user.useLibertyRepository' value='false'/>

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

  • When updating a product, your response file must contain the features that were used in the initial install of the product; otherwise, your update will not occur as intended. If you do not add these features to your response file, Installation Manager assumes you are removing them.

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_silent
File name: twlp_ins_upgrade_silent.html