Install Liberty fix packs on IBM i operating systems using the command line
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. We can use the IBM Installation Manager command-line function to update the product with the fixes available for the service level of WAS Liberty Core installation.
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.
IBM Installation Manager is used to apply product maintenance to WebSphere Application Server for IBM i.
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. If we create and point to a set of custom repositories that include only the specific fixes to install, we should be able to use this command confidently. 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.
- We can also install fix packs using response files with Installation Manager. For information on creating and using response files, read Install Liberty fix packs on IBM i operating systems using response files and the IBM Installation Manager Information Center.
- We cannot use the iRemoteInstall command to install a fix pack.
-
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 fixes available for 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 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 list of the names of the fixes that we would like to install.
- Go to Fix
Central.
- Update WebSphere Application Server Liberty Core installation 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 from a service repository, perform the following actions:
- If we do not already have Installation Manager credential-storage
and master-password files containing the IBM software user ID and password, create files
that will allow you to access the repository.
These are the credentials that we 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.
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.
- 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
When we use Installation Manager v1.6.2 and later, we should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In versions of Installation Manager earlier than v1.6.2, the -keyring and -password options were used to access credentials in a keyring file. These options were 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.
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
- If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
- 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.
- If the offering version is not specified, the -installFixes option defaults to all.
- We can add a list of features that are separated by commas.
- We can specify additional assets to install from the Liberty Repository.
To install Liberty Repository assets, have access to the internet, and we must have IBM Installation Manager v1.6.2 or later.
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. To install additional features, specify the -properties parameter in the command line using either short names or symbolic names. 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
Beginning with v8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 add-on, or install the individual features needed from the Liberty Repository. See the following topics for more information:
We can install the complete set of Extended Programming Model features by specifying user.addon:
- -properties user.addon=extendedPackage-1.0,user.accept.license=true
If we upgrade WebSphere Application Server Liberty profile v8.5.5.3 or previous versions containing the extprogmodels install feature, Installation Manager automatically installs the extendedPackage-1.0 add-on. We must specify the user.accept.license feature:
- -properties user.accept.license=true
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, we 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.
- 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).
- Optional: List all installed packages to verify the installation:
- ./imcl listInstalledPackages -long
- 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:
- Download a 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 file contains an Installation Manager repository for the fix pack and usually has a .zip extension. After downloading the fix file, we 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 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 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 the system.
- Go to Fix
Central.
- 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:
-
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
- If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
- 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.
- If the offering version is not specified, the -installFixes option defaults to all.
- We can add a list of features that are separated by commas.
- We can specify additional assets to install from the Liberty Repository.
To install Liberty Repository assets, have access to the internet, and we must have IBM Installation Manager v1.6.2 or later.
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. To install additional features, specify the -properties parameter in the command line using either short names or symbolic names. 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
Beginning with v8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 add-on, or install the individual features needed from the Liberty Repository. See the following topics for more information:
We can install the complete set of Extended Programming Model features by specifying user.addon:
- -properties user.addon=extendedPackage-1.0,user.accept.license=true
If we upgrade WebSphere Application Server Liberty profile v8.5.5.3 or previous versions containing the extprogmodels install feature, Installation Manager automatically installs the extendedPackage-1.0 add-on. We must specify the user.accept.license feature:
- -properties user.accept.license=true
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, we 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.
- 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).
- Optional: List all installed packages to verify the installation:
- ./imcl listInstalledPackages -long
- Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
- To download the fix pack, perform the following actions:
- Access the live service repository containing the fix pack, and use web-based updating.
Parent topic:
Install Liberty on IBM i operating systems
Tasks:
Install Liberty on IBM i operating systems using the command line
Install Liberty on IBM i operating systems using response files
Install Liberty remotely on IBM i operating systems using the iRemoteInstall command
Add and remove features from Liberty on IBM i operating systems using response files
Uninstall Liberty from IBM i operating systems using the command line
Uninstall Liberty from IBM i operating systems using response files
Install Liberty interim fixes on IBM i operating systems using the command line
Install Liberty fix packs on IBM i operating systems using response files
Uninstall Liberty interim fixes from IBM i operating systems using the command line
Uninstall Liberty fix packs from IBM i operating systems using the command line
Uninstall Liberty fix packs from IBM i operating systems using response files
Terms and conditions for information centers