Install Liberty fix packs on IBM i operating systems using response files

Install Liberty fix packs on IBM i operating systems using response files

We can update WebSphere Application Server Liberty Core to a later version using Installation Manager response files.

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.

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

Optional: If the repository requires a username and password, create a credential-storage file to access this repository.
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.
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.

Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.

On a CL command line, run the STRQSH command to start the Qshell command shell.
Use a response file to update the product.
Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and update the product. For example:
./imcl -acceptLicense input $HOME/WASFiles/temp/update_response_file.xml -log $HOME/WASFiles/temp/update_log.xml -secureStorageFile $HOME/WASFiles/temp/credential.store -masterPasswordFile $HOME/WASFiles/master_password_file.txt

The program might write important post-installation instructions to standard output.
For more information on using Installation Manager, read the IBM Installation Manager Information Center.

Example

The following is an example of a response file for updating WebSphere Application Server Liberty Core 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.v85'/> </server> <profile id='WebSphere Liberty V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore'> <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/LibertyCore'/> </profile> <install modify='false'> <offering profile='WebSphere Liberty V8.5' id='com.ibm.websphere.liberty.v85' version='8.5.5.20101025_2108'/> </install> <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/QIBM/UserData/InstallationManager/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 running 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 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 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.

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/ReadmeV8.html or /QIBM/WAS/WASFixpacks/ReadmeV8.txt.

We can specify additional assets 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. Previous versions of Installation Manager do not have the option to install Liberty Repository assets. If we are using a response file and have not updated Installation Manager to 1.6.2 or later, the assets that we specify in the response file are ignored during the installation.
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 two extra data key elements in the response file. We can use either the symbolic name or the short name.
The following example installs the Portlet Container and Portlet Serving features using the symbolic name.
<data key='user.feature' value='com.ibm.websphere.appserver.portlet-2.0,,com.ibm.websphere.appserver.portletserving-2.0'/> <data key='user.accept.license' value='true'/>
The following example installs the Portlet Container and Portlet Serving features using the short name:
<data key='user.feature' value='portlet-2.0,,portletserving-2.0'/> <data key='user.accept.license' value='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:

Install Liberty Repository assets

Liberty features

The following example installs the Extended Programming Models using the user.addon parameter and the Portlet Container and Portlet Serving features using the user.feature parameter with symbolic names:
<data key='user.addon' value='extendedPackage-1.0'/> <data key='user.feature' value='com.ibm.websphere.appserver.portlet-2.0,,com.ibm.websphere.appserver.portletserving-2.0'/> <data key='user.accept.license' value='true'/>
The following example installs the Extended Programming Models using the user.addon parameter and the Portlet Container and Portlet Serving features using the user.feature parameter with short names:
<data key='user.addon' value='extendedPackage-1.0'/> <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/> <data key='user.accept.license' value='true'/>

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

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

Verify the installation

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 the command line

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

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.