Product fix packs contain bundled service to bring WebSphere® Application Server
up to a new product level. Interim fixes provide corrective service
for specific known problems. You can use IBM Installation Manager
to update the product with the fixes that are available for the Web
2.0 and Mobile Toolkit.
Before you begin
Contact the IBM® Software Support Center for
information about upgrades for WebSphere Application
Server for z/OS®. 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 for more information on installing the update.
About this task
Use this procedure whenever you want to apply a new fix
pack or interim fix to your system.
Procedure
- Use Installation Manager to apply the required maintenance
to your product dataset and file-system structure.
- 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 interim
fixes using one of the following procedures.
- To update the Web 2.0 and Mobile Toolkit with interim fixes or
fix packs, access the live service repository that contains the fixes
and use web-based updating.
Use Installation Manager on your local
system to update the Web 2.0 and Mobile Toolkit with the interim fixes
from the live web-based repository at the following location:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.W2MTK.v11
To install a fix from a service repository, perform
the following actions:
- Mount the product file system, read and write, at the path at
which it was originally mounted with Installation Manager.
- 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.
Use the
imutilsc
saveCredential command to create a keyring or add additional
credentials to
it:
imutilsc saveCredential
-keyring keyring_file
-userName IBM_software_ID
-userPassword IBM_software_password
-url repository_URL
For
information on the imutilsc saveCredential command,
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.
- From the Installation Manager user ID, perform the following actions:
- 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.
To install an interim fix, use this command:imcl install fix_name
-installationDirectory product_installation_location
-repositories repository_URL
-keyring keyring_file
To
install a fix pack, use this command:imcl install com.ibm.websphere.W2MTK.v11_version
-installationDirectory product_installation_location
-repositories repository_URL
-keyring keyring_file
-acceptLicense
Tips: - The version, which optionally can be attached
to the offering ID with an underscore, is a specific version of the
offering to install (1.1.0.20110427_2247 for example).
- 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.
- Optional: List all installed packages to verify the installation:
imcl listInstalledPackages -long
- To update the product with interim fixes or fix packs, download
the files that contain the fixes from Fix Central and use local updating.
You
can download compressed files that contain the fixes from Fix Central.
Each compressed fix file contains an Installation Manager repository
for the fix and usually has a .zip extension. After downloading the
fix files, you can use Installation Manager to update the Web 2.0
and Mobile Toolkit with the fixes.
- To download the fixes, 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 fixes 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 fixes.
- Transfer the compressed fix files in binary format to the z/OS
system on which they will be installed.
- If you are installing a fix pack, extract the compressed repository
files to a directory on your system.
- To install a fix from a downloaded file, perform the following
actions:
- Mount the product file system, read and write, at the path at
which it was originally mounted with Installation Manager.
- From the Installation Manager user ID, perform the following actions:
- 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.
To install an interim fix, use this command:imcl install fix_name
-installationDirectory product_installation_location
-repositories compressed_file
To
install a fix pack, use this command:imcl install com.ibm.websphere.W2MTK.v11_version
-installationDirectory product_installation_location
-repositories location_of_expanded_files
-acceptLicense
Tips: - The version, which optionally can be attached
to the offering ID with an underscore, is a specific version of the
offering to install (1.1.0.20110427_2247 for example).
- 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.
- Optional: List all installed packages to verify the installation:
imcl listInstalledPackages -long
- Remount the product file system at its production location.
The file system should normally be mounted read-only.
- Perform any other migration actions as instructed in fix
or APAR cover letters.