[IBM i]

Installing fix packs for the Web 2.0 and Mobile Toolkit on IBM i operating systems using response files

You can use Installation Manager response files to update the Web 2.0 and Mobile Toolkit to a later version.

Before you begin

Contact the IBM® Software Support Center for information about upgrades for WebSphere® Application Server. The most current information is available from the IBM Software Support Center and Fix Central.

Minimum repositories requirement to apply Web 2.0 and Mobile Toolkit updates: Installation Manager must have access to the following repositories:
  • Repository for the current level of the Web 2.0 and Mobile Toolkit that is installed on the system
  • Update repositories—that is, the repositories containing the updates for the Web 2.0 and Mobile Toolkit

See the readme documentation that is included with the fix pack for more information on installing the update.

About this task

Perform this procedure to use Installation Manager response files to update the Web 2.0 and Mobile Toolkit.

Procedure

  1. 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

    Tip: 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 that is specified.
    Note:

    Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring 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 before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

    There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 documentation.

  2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  3. On a CL command line, run the STRQSH command to start the Qshell command shell.
  4. Use a response file to update the Web 2.0 and Mobile Toolkit.
    Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and update the Web 2.0 and Mobile Toolkit. 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
    Note: 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 the Web 2.0 and Mobile Toolkit to a later version.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' temporary='true'>
<server>
  <repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.W2MTK.v11'/>
</server>
<profile id='Web 2.0 and Mobile Toolkit V1.1' 
  installLocation='/QIBM/ProdData/WebSphere/AppServer/Web20Mobile/V11'>
  <data key='eclipseLocation' value='/QIBM/ProdData/WebSphere/AppServer/Web20Mobile/V11' />
  <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/Web20Mobile/V11'/>
  <data key='user.import.profile' value='false'/>
  <data key='cic.selector.nl' value='en'/>
</profile>
<install modify='false'>
  <offering profile='Web 2.0 and Mobile Toolkit V1.1' features='main' id='com.ibm.websphere.W2MTK.v11' 
    version='1.1.0.20110427_2247' installFixes='none'/>
</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'/>
<preference name='com.ibm.cic.common.core.preferences.import.enabled' value='true'/>
<preference name='com.ibm.cic.agent.ui.displayInternalVersion' 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 (1.1.0.20110427_2247 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
  • 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.
  • If you obtained the fix pack by installing the WebSphere Application Server group PTF, you 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.

Task topic    

Terms and conditions for product documentation | Feedback

Last updated: January 29, 2018 10:59 AM GMT-06:00
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v850webmob&product=was-nd-mp&topic=tweb_ins_upgrade_is
File name: tweb_ins_upgrade_is.html