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 IBM i operating systems using response files

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

Before you begin

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. 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 installFixes attribute in a response file.

About this task

New: [Updated in June 2016] Fix pack 16.0.0.2 is the next fix pack after 8.5.5.9. You can continue to use the same Version 8.5 Installation Manager repositories and offering IDs to install or update to 16.0.0.2, or you can use the new versionless repositories and offerings. For more information about fix pack 16.0.0.2, see What is new in Liberty in the new location of the latest Liberty documentation.[Updated in June 2016]

[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. Optional: If the repository requires a username and password, create a credential-storage file to access this repository.
    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 documentation. For more information on using the -keyring and -password options to store credentials in a keyring file, see the Installation Manager Version 1.5 documentation.
  2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  3. On a CL command line, run the STRQSH command to start the Qshell command shell.
  4. Use a response file to update the product.
    Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and update the product. For example:
    ./imcl -acceptLicense
      input $HOME/WASFiles/temp/update_response_file.xml 
      -log $HOME/WASFiles/temp/update_log.xml 
      -secureStorageFile $HOME/WASFiles/temp/credential.store -masterPasswordFile $HOME/WASFiles/master_password_file.txt
    Note: The program might write important post-installation instructions to standard output.

    For more information on using Installation Manager, read the IBM Installation Manager Information Center.

Example

The following is an example of a response file for updating WebSphere Application Server Liberty Core 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='/QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore'>
  <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/LibertyCore'/>
</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='/QIBM/UserData/InstallationManager/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 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.
  • 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/ReadmeV8.html or /QIBM/WAS/WASFixpacks/ReadmeV8.txt.

  • 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.
    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'/>
    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="/QIBM/LocalAssetRepo" />
    [8.5.5.8 or later]<repository location="/QIBM/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.

  • [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.

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_is
File name: twlp_ins_upgrade_is.html