Install Liberty fix packs on distributed operating systems using the command line

Install Liberty fix packs on distributed operating systems using the command line

We can use the IBM Installation Manager command line to update the product with the fix packs available for Liberty Core.

Contact the IBM Software Support Center for information about updates for Liberty Core. The most current information is available from the IBM Software Support Center and Fix Central.
IBM Installation Manager is used to apply product maintenance to WebSphere Application Server Liberty Core.
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 we have full control over which fixes are contained in the targeted repositories. We can create and point to a set of custom repositories that include only the specific fixes to install. If we enable searching service repositories or install fixes directly from other live web-based repositories, then we might not want to select this option so that we can select only the fixes to install using the -installFixes option with the install command on the command line or the installFixes attribute in a response file.

To install v8.5.5.4 and later of the Liberty profile requires IBM Installation Manager v1.6.2 or later.

For a list of interim fixes and fix packs available for Liberty Core 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 the 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 we 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 containing the fix pack, and use web-based updating.
Use Installation Manager on the 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 Server product offerings for supported operating systems.

These locations do not contain web pages that we can access using a web browser. They are remote web-based repository locations that we specify for Installation Manager so that it can maintain the product.

To install a fix pack from a service repository, perform the following actions:

Log on to the system.

Create Installation Manager credential-storage and master-password files containing the IBM software user ID and password. These files enable you to access the repository and 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 specified.
For Installation Manager v1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In previous versions, the -keyring and -password options are used to access credentials in a keyring file. These options are deprecated in v1.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 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 source_repository -installationDirectory offering_installation_location -secureStorageFile storage_file -masterPasswordFile master_password_file -acceptLicense

imcl.exe install offering_ID_offering_version,optional_feature_ID -repositories source_repository -installationDirectory offering_installation_location -secureStorageFile storage_file -masterPasswordFile master_password_file -acceptLicense
where offering_ID is the offering Server product offerings for supported operating systems.
Tips:

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 running the following command against the repository:
imcl listAvailablePackages -repositories source_repository

We can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes we 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.

We can add a list of features that are separated by commas.

We can specify additional features to install from the Liberty Repository.
To install Liberty Repository assets, have access to the internet, and have IBM Installation Manager v1.6.2 or later. To install additional features, specify the following properties in the command line. Note that the feature short names, such as FeatureA, are separated by double commas:
-properties user.feature=FeatureA,,FeatureB,,FeatureC,user.accept.license=true

For a list of Liberty features, see Liberty features. We can also install the following additional features:

Liberty Repository features that we can install using IBM Installation
Feature Symbolic name and short name Description
Portlet Container com.ibm.websphere.appserver.portlet-2.0
portlet-2.0
This feature provides a runtime environment for portlets that comply with JSR 168 and JSR 286 and a development environment for testing portlets deployed into WebSphere Portal Server.
Portlet Serving com.ibm.websphere.appserver.portletserving-2.0
portletserving-2.0
This feature provides the portlet serving or URL addressability functionality for portlets that are compliant with JSR 168 and JSR 286. This feature enables us to invoke a portlet under a defined URL from a browser.
Web Cache Monitor com.ibm.websphere.appserver.webCacheMonitor-1.0
webCacheMonitor-1.0
This feature provides monitoring of the distributed map cache and provides simple cache statistics, cache entries, and cache policy information for Servlet cache instances.

Beginning with v8.5.5.4, the Extended Programming Models are available to download from the Liberty Repository. This feature provides a rich set of programming models such as Web Services, JMS (including Message-Driven Beans), and MongoDB 2.0. The following example installs the Extended Programming Model.
imcl install com.ibm.websphere.liberty.ND.v85 -properties user.accept.license=true,user.addon=extendedPackage-1.0 -installationDirectory D:\IBM\Liberty -acceptLicense -repositories D:\IBM\LibertyRepo -sharedResourcesDirectory D:\IBM\IMShared -showProgress

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

Note: If we do not have the Extended Programming Model installed prior to updating to v8.5.5.4, we might encounter the following error during the update:
java.io.IOException: Too many open files at java.io.File.createNewFile(File.java:894)
To resolve this problem, increase the number of files using the ulimit command; for example:
ulimit -n 8192

List all installed packages to verify the installation:

./imcl listInstalledPackages -long

imcl.exe listInstalledPackages -long

Download the file containing the fix pack from Fix Central, and use local updating.
We can download a compressed file containing 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 WebSphere Application Server as the product.

Select the installed version.

Select the operating system as the platform, and click Continue.

Select Browse for fixes, and click Continue.

Select the fix pack to download, and click Continue.

Select the 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 is installed.

Extract the compressed repository files to a directory on the system.

To install a fix pack from a downloaded file, perform the following actions:

Log on to the 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:

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 running the following command against the repository:
imcl listAvailablePackages -repositories source_repository

We can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes we 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.

We can add a list of features that are separated by commas.

Optional. List all installed packages to verify the installation:

./imcl listInstalledPackages -long

imcl.exe listInstalledPackages -long

Parent topic: Install Liberty interim fixes and fix packs on distributed operating systems
Tasks:
Install Liberty interim fixes on distributed operating systems using the GUI
Install Liberty interim fixes on distributed operating systems using the command line
Uninstall Liberty interim fixes from distributed operating systems using the GUI
Uninstall Liberty interim fixes from distributed operating systems using the command line
Uninstall Liberty fix packs from distributed operating systems using the GUI
Install Liberty fix packs on distributed operating systems using the GUI
Install Liberty fix packs on distributed operating systems using response files
Uninstall Liberty fix packs from distributed operating systems using the command line
Uninstall Liberty fix packs from distributed operating systems using response files

Terms and conditions for information centers

Feature	Symbolic name and short name	Description
Portlet Container	com.ibm.websphere.appserver.portlet-2.0 portlet-2.0	This feature provides a runtime environment for portlets that comply with JSR 168 and JSR 286 and a development environment for testing portlets deployed into WebSphere Portal Server.
Portlet Serving	com.ibm.websphere.appserver.portletserving-2.0 portletserving-2.0	This feature provides the portlet serving or URL addressability functionality for portlets that are compliant with JSR 168 and JSR 286. This feature enables us to invoke a portlet under a defined URL from a browser.
Web Cache Monitor	com.ibm.websphere.appserver.webCacheMonitor-1.0 webCacheMonitor-1.0	This feature provides monitoring of the distributed map cache and provides simple cache statistics, cache entries, and cache policy information for Servlet cache instances.