Product fix packs contain bundled service to bring WebSphere® Application Server Liberty Core 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 Core 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.

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:
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]](../deltaend.gif)
Procedure
- For a list of fixes that are available for WebSphere Application Server Liberty Core 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 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 list of the names of the fixes that you would like to
install.
- Update WebSphere Application Server LibertyCore 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
Core with the interim fixes from the live
web-based service repositories.
To install a fix from a service repository, perform the following actions:
- 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.
- Sign on to the IBM i system with a user profile that has
*ALLOBJ and *SECADM special authorities.
- Stop all servers and applications on the WebSphere
Application Server Liberty Core installation that is being
updated.
- On a CL command line, run the STRQSH command to start the Qshell command shell.
- 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
- 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.
- 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 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.
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.

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 assets from the IBM
WebSphere Liberty Repository, 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 Liberty Repository
features, specify the short names or symbolic names on the user.feature option
of the -properties parameter. Multiple feature names are separated with double
commas. The following example installs the Portlet Container and Portlet Serving
features:
-properties user.feature=portlet-2.0,,portletserving-2.0,user.accept.license=true
For Version 8.5.5.5 and later, user.accept.license=true is not required.

![[8.5.5.4 or later]](../ng_v8554.gif)
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:
You
can install the complete set of Extended Programming Model features by specifying the
user.addon
option:
-properties user.addon=extendedPackage-1.0,user.accept.license=true
If
you upgrade WebSphere Application Server Liberty Version
8.5.5.3 or previous versions that contain the
extprogmodels feature, Installation
Manager automatically installs the
extendedPackage-1.0 add-on. You must specify the
user.accept.license
option:
-properties user.accept.license=true

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]](../ng_v8558.gif)
./imcl install com.ibm.websphere.liberty.v85
-properties user.useLibertyRepository=false,user.addon=extendedPackage-1.0,user.feature=portlet-2.0
-installationDirectory /QIBM/ProdData/Liberty -acceptLicense
-repositories /QIBM/LibertyProductRepo,https://your_onprem_asset_repo_url,/QIBM/LocalAssetRepo,/QIBM/LocalAssetRepo2.zip
-sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared
-showProgress
To learn more about the Liberty Repository and the
assets it contains, see Liberty Repository.
- 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.
- 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
Core 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 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 fix file in binary format to the IBM i systems on which it will be installed.
- Extract the compressed repository file to a directory on your system.
- To install a fix pack from a downloaded file, perform the following actions:
- Sign on to the IBM i system with a user profile that has
*ALLOBJ and *SECADM special authorities.
- Stop all servers and applications on the WebSphere
Application Server Liberty Core installation that is being
updated.
- On a CL command line, run the STRQSH command to start the Qshell command shell.
- 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
- 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.
- 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.
- 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 assets from the IBM
WebSphere Liberty Repository, 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 Liberty Repository features, specify the short names or symbolic names on the
user.feature option of the -properties parameter. Multiple
feature names are separated with double commas. The following example installs the Portlet
Container and Portlet Serving
features:
-properties user.feature=portlet-2.0,,portletserving-2.0,user.accept.license=true
For Version 8.5.5.5 and later, user.accept.license=true is not required.

![[8.5.5.4 or later]](../ng_v8554.gif)
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:
You
can install the complete set of Extended Programming Model features by specifying the
user.addon
option:
-properties user.addon=extendedPackage-1.0,user.accept.license=true
For Version 8.5.5.5 and later, user.accept.license=true is not required.
If you upgrade WebSphere Application Server Liberty Version 8.5.5.3 or
previous versions that contain the
extprogmodels feature, Installation Manager
automatically installs the
extendedPackage-1.0 add-on. You must specify the
user.accept.license
option:
-properties user.accept.license=true

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]](../ng_v8558.gif)
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.
- 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.
- Optional: List all installed packages to verify the
installation:
./imcl listInstalledPackages -long