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.
Tip: As an alterative 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 you have full control over which fixes are
contained in the targeted repositories. If you create and point to
a set of custom repositories that include only the specific fixes
that you want to install, you should be able to use this command confidently.
If you enable searching service repositories or install fixes directly
from other live web-based repositories, then you might not want to
select this option so that you can select only the fixes that you
want to install using the -installFixes option with the install command
on the command line or the installFixes attribute in a response file.
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.
Procedure
- For a list of interim fixes and fix packs that are available
for the Web 2.0 and Mobile Toolkit and specific information about
each fix, perform the following actions.
- Go to Fix
Central.
- Select WebSphere as
the product group.
- Select WebSphere Application
Server Web 2.0 and Mobile Toolkit as the product.
- Select the version of the product to be updated.
- Select your 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
you would like to install.
- Update the Web 2.0 and Mobile Toolkit with the fix pack
using one of the following procedures.
- Access the live service repository that contains the fix pack,
and use web-based updating.
Use Installation Manager on your local
system to update the Web 2.0 and Mobile Toolkit with the fix pack
from the live web-based repository at the following location:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.W2MTK.v11
Perform the following actions:
- Log on to your system.
- If you do not already have an Installation Manager credentials file containing your IBM software
user ID and password, create one that will allow you to access the
repository.
Note: These are the credentials that you use to access protected
IBM software websites.
For 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.
- 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 using a response file.
- Download the file that contains the fix pack from Fix Central,
and use local updating.
You can download a compressed file that
contains 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 the Web 2.0 and Mobile Toolkit
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 Web 2.0 and Mobile Toolkit as the product.
- Select the version of the product to be updated.
- Select your operating system as the platform, and click Continue.
- Select Browse for fixes, and click Continue.
- Select the fix pack that you want to download, and click Continue.
- Select your 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 will be installed.
- Extract the compressed repository files to a directory on your
system.
- Perform the following actions:
- Log on to your system.
- 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.
- 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 using a response file.
Example
![[Windows]](../images/windows.gif)
The following is an example of a response
file for updating the product 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.W2MTK.v11'/>
</server>
<profile id='Web 2.0 and Mobile Toolkit V1.1'
installLocation='C:\Program Files\IBM\WebSphere\AppServer\Web20Mobile'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer\Web20Mobile'/>
<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 2.0 and Mobile Toolkit V1.1' id='com.ibm.websphere.W2MTK.v11'
version='1.1.0.20110427_2247'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='C:\Program Files\IBM\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 (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.