You can use the IBM® Installation Manager command
line to update the product with the fix packs that are available for WebSphere® Application Server LibertyCore.
Before you begin
Important: Support for using Java™
SE 6 with WebSphere Liberty ended in September 2017. The
Liberty kernel was recompiled for 17.0.0.3. Beginning with 17.0.0.3, the Liberty kernel no longer
runs with Java SE 6. If you continue to use Java SE 6 on earlier releases after the end of support date, you
might expose your environment to security risks.
Java SE 8
is the recommended Java SDK because it provides the latest
features and security updates. As an alternative to installing Java SE 8, you can install another supported Java SDK
version.
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.
IBM Installation Manager Version 1.8.5 or later is required to update to Liberty fix pack 16.0.0.2 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.
Procedure
- For a list of fix packs that are available for WebSphere Application Server Liberty Core
and specific information about each fix, perform the following actions.
- Go to Fix
Central.
- Click Find product.
- Select WebSphere Liberty as the product group.
- Select the version of the product to be updated.
- Select your operating system as the platform, and click Continue.
- Select Browse for fixes, and click Continue.
- Select Fix pack as the fix type, and click
Submit.
- 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 Core 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 pack from a service repository, 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.
- Stop all servers and applications on the WebSphere Application Server Liberty Core
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.




./imcl install offering_ID_offering_version,optional_feature_ID
-repositories repository_URL_or_path
-installationDirectory offering_installation_location
-secureStorageFile storage_file -masterPasswordFile master_password_file
-acceptLicense

imcl.exe install offering_ID_offering_version,optional_feature_ID
-repositories repository_URL_or_path
-installationDirectory offering_installation_location
-secureStorageFile storage_file -masterPasswordFile master_password_file
-acceptLicense
where offering_ID is the offering ID that is listed in Liberty product offerings for supported operating systems.Tips: New: When you update Liberty, all installed Liberty addons and features are also
updated.
You can install additional addons and features by specifying them on the
user.addon and user.feature properties, as shown in the
following example. Note that the feature short names or symbolic names are separated by double
commas:imcl install com.ibm.websphere.liberty.CORE.ND,embeddablecontainer
-properties user.addon=extendedPackage-1.0,user.feature=portlet-2.0,,portletserving-2.0
-installationDirectory "C:\Program Files\IBM\WebSphere\Liberty" -acceptLicense
-repositories D:\IBM\LibertyRepo,https://your_onprem_asset_repo_url,D:\IBM\LocalAssetRepo,D:\IBM\LocalAssetRepo2.zip
-sharedResourcesDirectory D:\IBM\IMShared
-showProgress
You can install assets from instances of the Liberty Asset
Repository Service or local directory-based repositories with or without internet access. Add the
repository URL, directory path, or archive file path on the -repositories
parameter. These repositories are accessed in the order that they are specified. For more
information about these asset repositories, see Installing assets using Installation Manager. To install assets from the IBM
WebSphere Liberty Repository, you must have access to
the internet. To enable access to the Liberty Repository, on the -properties
parameter, set the user.useLibertyRepository option to true.
The Liberty Repository is the last of the repositories that are accessed during
installation.
- The offering_version, which optionally can be attached to the offering ID
with an underscore, is a specific version of the offering to install
(16.0.2.20160503_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 repository_URL_or_path
- 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.
- To install the embeddable EJB container and JPA client, specify the optional
embeddablecontainer feature after the offering ID, separated by a comma.
Note: A removal notice was issued for the embeddable EJB container and JPA
client feature as of the 16.0.0.2 fix pack, so the feature is eligible for future removal. For more
information, see Removal notices.
The embeddable EJB container is a
Java archive (JAR) file that you can use to run enterprise
beans in a standalone Java Platform, Standard Edition (SE)
environment. You can run enterprise beans by using this embeddable container outside the application
server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used
for unit testing enterprise beans business logic.
The JPA client can be used with the
embeddable EJB container to provide Java Persistence API
capability in a Java SE environment.
- Optional: List all installed packages to verify the installation:




./imcl listInstalledPackages -long

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.
- To download the fix pack, perform the following actions:
- Go to Fix
Central.
- Select WebSphere as the product group.
- Select 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.
- To install a fix pack from a downloaded file, perform the following actions:
- Log on to your system.
- Stop all servers and applications on the WebSphere Application Server Liberty Core
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.




./imcl install offering_ID_offering_version,optional_feature_ID
-installationDirectory offering_installation_location
-repositories location_of_expanded_files
-acceptLicense

imcl.exe install offering_ID_offering_version,optional_feature_ID
-installationDirectory offering_installation_location
-repositories location_of_expanded_files
-acceptLicense
Tips: New: When you update Liberty, all installed Liberty addons and features are also
updated.
You can install additional addons and features by specifying them on the
user.addon and user.feature properties, as shown in the
following example. Note that the feature short names or symbolic names are separated by double
commas:imcl install com.ibm.websphere.liberty.CORE.ND,embeddablecontainer
-properties user.addon=extendedPackage-1.0,user.feature=portlet-2.0,,portletserving-2.0
-installationDirectory "C:\Program Files\IBM\WebSphere\Liberty" -acceptLicense
-repositories D:\IBM\LibertyRepo,https://your_onprem_asset_repo_url,D:\IBM\LocalAssetRepo,D:\IBM\LocalAssetRepo2.zip
-sharedResourcesDirectory D:\IBM\IMShared
-showProgress
You can install assets from instances of the Liberty Asset
Repository Service or local directory-based repositories with or without internet access. Add the
repository URL, directory path, or archive file path on the -repositories
parameter. These repositories are accessed in the order that they are specified. For more
information about these asset repositories, see Installing assets using Installation Manager. To install assets from the IBM
WebSphere Liberty Repository, you must have access to
the internet. To enable access to the Liberty Repository, on the -properties
parameter, set the user.useLibertyRepository option to true.
The Liberty Repository is the last of the repositories that are accessed during
installation.
- The offering_ID is the offering ID that is listed in Liberty 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
(16.0.2.20160503_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 repository_URL_or_path
- 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.
- To install the embeddable EJB container and JPA client, specify the optional
embeddablecontainer feature after the offering ID, separated by a comma.
Note: A removal notice was issued for the embeddable EJB container and JPA
client feature as of the 16.0.0.2 fix pack, so the feature is eligible for future removal. For more
information, see Removal notices.
The embeddable EJB container is a
Java archive (JAR) file that you can use to run enterprise
beans in a standalone Java Platform, Standard Edition (SE)
environment. You can run enterprise beans by using this embeddable container outside the application
server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used
for unit testing enterprise beans business logic.
The JPA client can be used with the
embeddable EJB container to provide Java Persistence API
capability in a Java SE environment.
- Optional: List all installed packages to verify the installation:




./imcl listInstalledPackages -long

imcl.exe listInstalledPackages -long