You can update WebSphere® Application
Server Liberty Network
Deployment to
a later version using Installation Manager response files.
Before you begin
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.
Procedure
- For a list of interim fixes and fix packs that are available
for WebSphere Application
Server Liberty Network
Deployment installation
and specific information about each fix, perform the following actions.
- Go to Fix
Central.
- Select WebSphere as
the product group.
- Select WebSphere Application
Server Liberty Network
Deployment as
the product.
- Select the installed version.
- Select your operating system as the platform, and click Continue.
- Select Browse for fixes, and click Continue.
- Click More Information under each fix to view information
about the fix.
- Recommendation: Make a note of the name of the fix pack
that you would like to install.
- Update WebSphere Application
Server Liberty Network
Deployment 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
Network
Deployment with
the interim fixes from the live web-based service repositories.
Perform the following actions:
- Log on to your system.
- 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.
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.
- Stop all servers and applications on the WebSphere Application Server Liberty Network
Deployment installation
that is being updated.
- Change to the Installation_Manager_binaries/eclipse/tools directory,
where Installation_Manager_binaries is
the installation root directory for the Installation Manager.
- Install the fix pack using a response file.
- 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.
- To download the fix pack, perform the following actions:
- Go to Fix
Central.
- Select WebSphere as
the product group.
- Select WebSphere Application
Server Liberty Network
Deployment as
the product.
- Select the installed version.
- Select your operating system as the platform, and click Continue.
- Select Browse for fixes, and click Continue.
- Select the fix pack that you want to download, and click Continue.
- Select your download options, and click Continue.
- Click I agree to agree to the terms and conditions.
- Click Download now to download the fix pack.
- Transfer the compressed file in binary format to the system on
which it will be installed.
- Extract the compressed repository files to a directory on your
system.
- Perform the following actions:
- Log on to your system.
- 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.
- Stop all servers and applications on the WebSphere Application Server Liberty Network
Deployment installation
that is being updated.
- Change to the Installation_Manager_binaries/eclipse/tools directory,
where Installation_Manager_binaries is
the installation root directory for the Installation Manager.
- Install the fix pack using a response file.
Example

The 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.ND.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.ND.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.
- 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, the Installation Manager assumes you are removing
them.