Install fix packs on the Web Server Plug-ins on IBM i operating systems using response files

(iseries)
Install fix packs on the Web Server Plug-ins on IBM i operating systems using response files

We can update the Web Server Plug-ins to a later version using Installation Manager response files.

As an alterative to the procedure described in this article, Installation Manager allows us 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, you should be able to use this command confidently. If we perform one of the following procedures, however, you might not want to use the updateAll command:

Enable Installation Manager to search service repositories

Install fixes directly from other live web-based repositories
If we do not use the updateAll command in a response file or on the command line, we can select only the fixes to install using one of the following options:

The installFixes attribute in a response file

The -installFixes option with the install command on the command line

Perform this procedure to use Installation Manager to update the Web Server Plug-ins using Installation Manager response files.
For information on installing and removing fix packs for WebSphere Application Server offerings on IBM i systems using the Installation Manager command line, read the following articles in this information center:

Install fix packs on IBM i operating systems using the command line

Uninstall fix packs from IBM i operating systems using the command line

Optional: If the repository requires a username and password, create a keyring file to access this repository.
For more information on creating a keyring file for Installation Manager, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.
When creating a keyring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL specified.

Start in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.
In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager prior to version 1.7. Update Installation Manager to version 1.7 or higher and then recreate and replace any secure storage files created with earlier versions.
There is no migration path from keyring files to storage files because of the differences in the file structures. Create a storage file to replace a keyring file. 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.

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 Web Server Plug-ins.
Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and update the Web Server Plug-ins. For example:

./imcl -acceptLicense input $HOME/WASFiles/temp/update_response_file.xml -log $HOME/WASFiles/temp/update_log.xml -keyring $HOME/WASFiles/temp/im.keyring

For more information on using Installation Manager, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

Example

The following is an example of a response file for updating the Web Server Plug-ins 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.PLG.v85'/>
</server>
<profile id='Web Server Plug-ins for IBM WebSphere Application Server V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/PLG'>
  <data key='eclipseLocation' value='/QIBM/ProdData/WebSphere/AppServer/V85/PLG'/>
  <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/PLG'/>
  <data key='user.import.profile' value='false'/>
  <data key='cic.selector.nl' value='en, fr, it, zh, ro, ru, zh_TW, de, ja, pl, es, cs, hu, ko, pt_BR'/>
</profile>
<install modify='false'>
  <offering profile='Web Server Plug-ins for IBM WebSphere Application Server V8.5' id='com.ibm.websphere.PLG.v85' version='8.5.0.20101025_2108'
   features='core.feature'/>
</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 you run 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 offering ID (<offering . . . id='offering_ID' . . . .>) can be found in the Install Manager Offering ID section of the report that is generated when you run the historyInfo or genHistoryReport command from the app_server_root/bin directory.

The version is a specific version of the offering to install (8.5.0.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 you run 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.

Related tasks

Install and uninstall the Web Server Plug-ins on IBM i operating systems
Install the Web Server Plug-ins on IBM i operating systems using response files
Install the Web Server Plug-ins on IBM i operating systems using the command line
Uninstall fix packs from the Web Server Plug-ins on IBM i operating systems using response files
Uninstall the Web Server Plug-ins from IBM i operating systems using response files
Uninstall the Web Server Plug-ins from IBM i operating systems using the command line