You can use the IBM Update Installer for WebSphere Software to
install interim fixes, fix packs, and refresh packs. The Update Installer
for WebSphere Software is also known as the update installer program, the
UpdateInstaller program, and the Update Installation Wizard.
Use the proper authorizations to successfully install product updates.
Use the update installer program as the root user on a Linux or UNIX platform,
or as the Administrator on a Windows platform.
The Update Installer
Wizard is an InstallShield for Multiplatforms Wizard that runs with either
a graphical user interface or in silent mode with or without a response file.
When you omit the response file in silent mode, the wizard installs the last
maintenance package that you downloaded to the default maintenance directory.
Important: Throughout this topic, certain directory paths are shown
only in Linux and UNIX format for simplicity. The equivalent Windows paths
are identical except for the direction of the slashes.
The following
descriptions contain reference information about installing interim fixes,
fix packs, and refresh packs on
WebSphere ESB products:
- Overview of the installation procedure
- To install an interim fix:
- To update an existing copy of the update installer, back up and delete
the updateinstaller directory of the existing update
installer before downloading the new zipped or TAR file into the install_root directory.
- Download the most current version of the update installer, fix pack, or
refresh pack zipped or TAR file from the Support site into the install_root directory.
- Unpack the zipped or TAR file that you downloaded to create the updateinstaller directory
and several subdirectories, including the maintenance directory.
- Interim fix only: Download the interim fix from the Support Web
site into the maintenance directory.
- Use the update installer to install the interim fix, fix pack, or refresh
pack. The update installer creates a backup file in the install_root/properties/version/update/backup directory.
IBM does not support user modifications to backup files.
- Updating existing profiles in WebSphere ESB products
- The update installer updates the core product files in a WebSphere ESB product.
Service in a maintenance package might update the following core product files
in the installation root directory:
- JAR files in the lib directory
- Scripts in the bin directory
- Profile templates
Some maintenance packages provide required service for existing profiles
in addition to service for the core product files. Each maintenance package
that has profile maintenance provides a script that changes the profile. The
update installer prompts you to back up your configuration when installing
a maintenance package that has required maintenance for profiles.
Some
maintenance packages provide optional service for existing profiles. The readme
file for the maintenance package describes whether the maintenance package
contains optional service for existing profiles. If so, the readme file describes
how to use the script provided with the maintenance package.
Use the backupConfig command
to back up the configuration of each profile that the maintenance package
can update. Or archive the install_root/profiles directory
to back up all of the profiles at once.
If you uninstall a maintenance
package, the update installer does not uninstall the maintenance package from
profiles. The reason for not removing the maintenance is that you might have
configured the profile after installing the maintenance. To restore an original
profile, use the restoreConfig command or copy the profile
from the archived profiles directory to replace the changed
profile.
- Viewing the fix level of the node
- You can use the versionInfo command in the install_root/bin directory
to display the exact fix and version level of the product. However, do not
use the versionInfo command while installing or uninstalling
a maintenance package. Add the following bullet when we support clustering:
Updating
cluster members
Apply the same maintenance packages to all of
the WebSphere ESB nodes
in a cluster. When all of the cluster members are not at the same service
level, the following exception can occur:
This error can cause memory
replication to not function properly.
DRSCacheApp E DRSW0008E:
Exception is: com.ibm.disthub.impl.jms.JMSWrappedException:
{-1361012295|unknown|java.io.OptionalDataException|}
Do not launch multiple copies of the Update Installer
Wizard at one time: Concurrent launches of the update installer program
are not supported. Performing more than one update at the same time can produce
unpredictable results, which might include a failed or faulty installation.
Required
information
The graphical interface requires the following information
that you must supply:
Table 1. Information
required when installing a maintenance packageField |
Valid values |
Description |
File path of the installation root directory of the WebSphere
product and the Update Installer |
Identify the installation root directory for WebSphere ESB |
Download and unpack the Update Installer for WebSphere
Software within each set of core product files that you intend to update. The
Update Installer application selects the product in its parent directory by
default.
|
File name of the maintenance package to install. |
Select a maintenance package to install from the maintenance directory. |
The default maintenance package is the package with the
latest date stamp and time stamp. |
The following procedure describes how to install a maintenance
package. For a description of how to remove a maintenance package, see Uninstalling maintenance packages.
- Log on as root on a Linux or UNIX operating system,
or as a member of the Administrator group on a Windows system.
On AIX platforms: In addition, verify
that the umask setting is 0022. To verify the umask setting, issue the following
command:
umask
To set the umask setting to 0022, issue the following command:
umask 0022
On HP-UX,
Linux and Solaris platforms: In addition, verify that the umask setting
is 022. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Install the product that you intend to update.
You
have very likely already installed the software that you are now updating.
But if not, install the software now.
- Back up and delete any older copy of the update installer before
downloading the current update installer. To use a newer version
of the update installer, you must first remove the older version.
- Back up any files and subdirectories in the install_root/updateinstaller/maintenance directory,
if necessary.
- Delete the install_root/updateinstaller/maintenance directory
and all of its subdirectories.
- Refresh packs and fix packs only: Download the fix pack
or refresh pack zipped file or TAR file from the Support site into a temporary
directory.
The zipped file or TAR file for a refresh pack or
a fix pack contains the update installer. You can check for a newer version
of the update installer code. Download the latest version of the Update Installer
for WebSphere Software as a zipped file or a TAR file from the following IBM
Web site:
Update Installer for WebSphere Software
- Interim fixes only: Download the update installer from the
Support site into a temporary directory.
Download the zipped
file or TAR file for the Update Installer for WebSphere Software from the
following IBM Web site:
Update Installer for WebSphere Software
- Unpack the zipped file or the TAR file.
Unzip or
untar the file into one of the following directories in a
WebSphere ESB environment
(directories shown are the common default directories for
WebSphere ESB):
On AIX platforms: install_root,
which can be either /usr/IBM/WebSphere/AppServer or /usr/IBM/WebSphere/ESBServer
On HP-UX, Linux, and Solaris platforms: install_root,
which can be either /opt/IBM/WebSphere/AppServer or /opt/IBM/WebSphere/ESBServer
On Windows platforms: install_root,
which can be either C:\Program Files\IBM\WebSphere\AppServer or C:\Program
Files\IBM\WebSphere\ESBServer
Unpacking the file creates the following directory structure:
install_root /updateinstaller
/framework
/lib
/maintenance
/responsefiles
version information is stored in the version.txt file
in the updateinstaller directory. A new version might
ship to correspond to any new fix. Information in the version.txt file
is displayed prominently in the title bar of the wizard and is also recorded
in the updatelog.txt file.
Always download and
use the latest version of the Update Installer Wizard when installing an interim
fix.
- Interim fixes only: Download the maintenance package *.pak file
from the Support Web site into the maintenance directory.
Download maintenance packages for WebSphere ESB from
the product support Web page at http://www.ibm.com/software/integration/wsesb/support/
Tip: Do not attempt to unzip or unpack the *.pak file.
On Windows platforms: Use the Windows
Services panel to stop all services for WebSphere ESB processes.
- Stop all Java processes that use the IBM Software Developer Kit
(SDK) that the WebSphere ESB product
provides.
Before installing or uninstalling interim fixes, fix
packs, and refresh packs on a machine, stop all Java processes on the machine
that use the IBM SDK, Java Technology Edition that WebSphere ESB provides.
WebSphere ESB processes
include:
- Process server processes
- The nodeagent process on a node when the node is federated into a deployment
manager cell
- The dmgr process for the deployment manager server
The update installer program requires you to stop all
WebSphere ESB-related
Java processes that are running on the system where you are using the update
installer program. For example, Java processes can include:
- All Java Virtual Machines (JVMs)
- WebSphere ESB processes,
including:
- Process server processes
- The nodeagent process on a node when the node is federated into a deployment
manager cell
- The dmgr process for the deployment manager server
- IBM HTTP Server processes
- First steps consoles
- Installation verification test (IVT) processes
- The Profile Wizard
- Other InstallShield for Multiplatforms (ISMP) installation programs
- InstallShield for Multiplatforms uninstallation programs
- IBM WebSphere Integration Developer Java processes
- The IBM Agent Controller
Stop all Java processes, if necessary. If you install an interim
fix while a WebSphere ESB-related
Java process runs, IBM does not guarantee that the product can continue to
run successfully, or without error.
- The Update Installer for WebSphere software requires a valid Java
run time that is provided with WebSphere software. If the update installer
program cannot locate a valid IBM or Sun SDK, such as the one shipped with WebSphere ESB,
the update installer cannot install maintenance packages. The Update Installer
for WebSphere Software searches known locations for a suitable IBM SDK to
use.
In order, the Update Installer Wizard looks for a valid
Java Virtual Machine (JVM) in the following locations:
- The install_root/updateinstaller/java/jre directory
(when updating the product SDK)
- The install_root/java/jre directory (which
is the preferred SDK to use)
On Linux and UNIX platforms: The directory
identified by one of the following environment variables on a Linux or UNIX
system: - JAVA_HOME
- JAVAHOME
- JRE_HOME
- JREHOME
When no JVM is present in one of the first two locations, set one
of the environment variables to point the Update Installer Wizard to a valid
JVM.
The preferred method of setting the JAVA_HOME environment
variable is using the setupCmdLine script provided with the WebSphere ESB product.
In some cases, failure to run setupCmdLine can result in the update installer
program matching an SDK in an order that is different than the order described.
You can also force the installation to use the correct SDK with the
following command:
./update -is:javahome install_root/java/jre
To use the setupCmdLine script to set the JAVA_HOME variable,
perform the following procedure that is appropriate for your operating system:
On Linux and UNIX platforms:- Open a command shell window.
- Change directories to the install_root/bin directory.
- Issue the . ./setupCmdLine.sh command. Notice the space
between the periods. The special format for this command sources the command
to make the setting active for all processes started from the command shell.
- Use the same command shell window to start the update installer, as described
in a later step.
On Windows platforms:- Open a command prompt window.
- Change directories to the install_root\bin directory.
- Issue the setupCmdLine.bat command.
- Use the same command prompt window to start the update installer, as described
in a later step.
For more information about using the setupCmdLine script, see
: Using the setupCmdLine script to set JAVA_HOME
before running the Update Installer for WebSphere software.
- Verify that the following prerequisite conditions are met:
- Change directories to the updateinstaller directory
and use the update command to install the maintenance package.
Install the maintenance package on the deployment manager node before
installing the maintenance package on each process server node that you intend
to update.
Use the following command syntax to install the last maintenance
package that you downloaded. The Update Installer Wizard runs as a background
process and does not display the graphical user interface when running in
silent mode:
update -silent
Or, issue the update command to start the
graphical user interface:
update
To view tables that show all of the options available when
using the update command, see update command.
This procedure results in installing maintenance packages to update
WebSphere software.
After installing an maintenance package, continue to use your
WebSphere software.