Use the IBM Update Installer for the product to install interim
fixes, fix packs, and refresh packs. The Update Installer is also known as
the Update Installer program, the UpdateInstaller program, and the Update
Installation wizard.
Before you begin
Use the correct authorizations to successfully install product
updates.
When administrative security
is enabled on WebSphere Application Server Network Deployment,
for example, you must supply the administrative user ID and password before
you can update the files.
Use the Update Installer program from the
same installer ID that installed the product that you are updating. Otherwise,
the file ownership mismatches might require correction by the root user. See Limitations of non-root installers for more information.
Use the Update
Installer program from a user profile with *ALLOBJ special authority.
Important:
The user account that originally installed the WebSphere
Application Server product to be updated should be used to launch the Installation
Wizard to install the Update Installer, and the same user account should be
used to launch the Update Installer program to update a product.
- When a different user account uses the updi_root location,
that user account must have reading and running access to that location. It
must also have writing access to the updi_root/logs directory
and its subdirectory.
- When a different user account is used to update the target WebSphere Application
Server product location, that user account must have full access (reading,
writing, and running) to the target location where a maintenance package is
to be applied.
If a non-root user launches the Update Installer program,
that user account must be able to run the slibclean command;
otherwise, a root user must run the slibclean command
whenever the Update Installer program is used.
- Make sure that no processes from any users are locking any files in the
target location where a maintenance package is to be installed.
The Update Installer wizard is an InstallShield for Multiplatforms
wizard that runs with in silent mode with a response
file.
The Update Installer wizard is an InstallShield for Multiplatforms
wizard that runs with either a graphical user interface or in silent mode
with a response file.
The
following descriptions contain reference information about installing interim
fixes, fix packs, and refresh packs on WebSphere Application Server products
and components:
- Overview of the installation procedure
Download, unpack, and install the Update Installer for WebSphere Software; or install the
Update Installer that is on the WebSphere Application Server supplements disc.
Note on using the Update Installer for WebSphere Software on the Microsoft® Windows Vista™ operating system: To use the Update Installer for WebSphere
Software on the Microsoft Windows Vista operating system, you must have Version
6.1.0.9 or later of the Update Installer installed on your system. Earlier
versions of the Update Installer are not supported on the Windows Vista operating
system.
Ensure that the Update Installer for WebSphere Software is installed on your system. The
Update installer can be installed from the WebSphere Application Server for
i5/OS supplements disk, which is included with the installation media. Additionally,
when you apply the latest WebSphere Application Server for i5/OS group program
temporary fix (PTF), the current level of the Update Installer is installed
if it is not already installed on the system. The default install location
for the Update Installer is QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI.
Download the most current version of the interim fix,
fix pack, or refresh pack file from the Support site into the updi_root/maintenance directory.
Download the most current version of the interim fix,
fix pack, or refresh pack file from the Support site into the updi_root /maintenance directory. Note: The WebSphere Application Server for i5/OS group PTF always
includes the most recent fix pack or refresh pack for the product. If you
have applied the group PTF, there is no need to download the current fix or
refresh pack level.
Use the Update Installer to install the interim fix, fix
pack, or refresh pack. If you have multiple feature packs
installed on your system, refer to Working with multiple feature packs using the Update Installer,
for more details.
For
information about synchronizing levels of applications on your system, refer
to Required synchronization with feature packs with the Update Installer.
Notes on running the Update Installer for WebSphere Software on Microsoft® Windows Vista™ and Windows 2008 operating systems:
- To use the Update Installer for WebSphere Software on the Microsoft Windows
Vista operating system, you must have Version 6.1.0.9 or later of the Update
Installer installed on your system. To use the Update Installer for WebSphere
Software on the Microsoft Windows Server 2008 operating system, you must have
Version 6.1.0.17 or later of the Update Installer installed on your system.
- If a non-Administrator applies maintenance using the Update Installer,
that user must do so with Windows User Account Control (UAC) in the same state
that it was in when Websphere Application Server was originally installed.
- If UAC was enabled during installation of Websphere Application Server,
apply maintenance with UAC enabled.
- If UAC was disabled during installation of Websphere Application Server,
apply maintenance with UAC disabled.
If a non-Administrator applies maintenance to Websphere Application
Server with a UAC setting that is different from that used in the initial
installation, then the registry is adversely affected. This might result
in unreliable listings of the installation locations in the destination panels
of the Update Installer, or an existing installation location might not show
up in the dropdown menu.
When the Windows Vista or Windows 2008 operating
systems are asked to run a program that requires elevated (Administrator)
privileges, it first tells the user whether or not the publisher of the program
is recognized. For certain Websphere Application Server programs, for example,
an operating-system dialog might appear that states "An unidentified program
wants access to your computer." Examine the program details; and if it is
the Websphere Application Server program that you intend to run, click Allow to
proceed.
The Update Installer creates a backup file in the app_server_root/properties/version/nif/backup directory.
IBM does not support restoring a backup file that
you have modified.
Use the Update Installer to install the interim fix,
fix pack, or refresh pack. The Update Installer creates a backup
file in the
app_server_root/properties/version/nif/backup directory.
New feature: The group PTFs do
not contain any feature pack related items. These items can be downloaded
from the support site.
newfeat
- Updating existing profiles in WebSphere Application Server products
- The Update Installer updates the core product files in a WebSphere Application
Server product. Service in a maintenance package might update the following
files in the installation root directory:
The SDK, Java technology edition, in the java/jre directory
- JAR files in the app_server_root/lib directory
- Scripts in the app_server_root/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 app_server_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 profile_root directory
to replace the changed profile.
- Viewing the fix level of the product
- Use the versionInfo command and
the historyInfo command in the app_server_root/bin directory of the installation root directory to display the exact fix and
version level of the product. However, do not use either command while installing
or uninstalling a maintenance package.
- Updating cluster members
Apply the same maintenance packages to all of the WebSphere Application
Server installations in a cluster. If your applications installed on clusters
use DRS Caching, make sure you have the same patches on each cluster member
that is at the same WebSphere Application level, for example all v6.x members
are at the same level. If these are not at the same service level, the following
exception can occur:
DRSCacheApp E DRSW0008E:
Exception is: com.ibm.disthub.impl.jms.JMSWrappedException:
{-1361012295|unknown|java.io.OptionalDataException|}
This
error can cause memory replication to not function properly.
Required information. The graphical interface requires
you to supply the following information:
Table 1. Information required when installing a maintenance package
Field |
Valid values |
Description |
File path of the installation
root directory of the WebSphere product or component. Installation
root directory of the Update Installer.
See updi_root for
more information.
|
Identify the installation root directory for one of
the following products:
- IBM WebSphere Application Server
- IBM WebSphere Application Server - Express
- Embedded version of the IBM WebSphere Application Server - Express
- IBM WebSphere Application Server Network Deployment
- IBM WebSphere Extended Deployment
- IBM Application Client for WebSphere Application Server
- IBM WebSphere Business Integration Server Foundation
- Web server plug-ins for WebSphere Application Server
|
Download,
unpack, and install the Update Installer for WebSphere Software. Or install the Update Installer that is on the
WebSphere Application Server supplements disc. Install the Update Installer
into each component that you intend to update.
The Update Installer
application updates the product in its parent directory by default.
|
File name of the maintenance package to install. |
Select a maintenance package to install from the updi_root/maintenance directory. |
The default maintenance package is the package with
the latest date stamp and time stamp. |
Important: See the release notes for your product for the latest information
about the Update Installer.
Log on as a user profile with *ALLOBJ special
authority.
Log on as root on an operating system
such as AIX or Linux, or log on as a member of the administrator group on
a Windows system.
If Japanese locale is enabled, you need to use the silent
installation to avoid problems.
- 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.
Optional: Install a new version of
the Update Installer. Back up and uninstall any older copy of
the Update Installer before downloading and installing 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 updi_root/maintenance directory if necessary.
- Uninstall the older version of the Update Installer using the
program under updi_root/uninstall.
- Download, unpack, and install the Update Installer for WebSphere Software; or install the Update
Installer that is on the WebSphere Application Server supplements disc.
Optional: Install
a new version of the Update Installer. If you have installed
the current level of the WebSphere Application Server group PTF, the update
installer was updated to the most recent level for you and you do not need
to perform this step.
Back up and uninstall any older copy of the Update
Installer before downloading and installing 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 updi_root/maintenance directory if necessary.
- Uninstall the older version of the Update Installer using the
program under updi_root/uninstall.
- Download, unpack, and install the Update Installer for WebSphere Software; or install the Update
Installer that is on the WebSphere Application Server supplements disc.
Download the maintenance package *.pak file
from the Support Web site into the updi_root/maintenance directory.
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
Download maintenance packages for the Update Installer for WebSphere Software to install
from the following IBM Web pages:
Tip: Do not attempt to unzip or unpack the *.pak file.
Download the maintenance package *.pak file
from the Support Web site into the updi_root/maintenance directory.
Note: If you are installing the most current fix pack and you have installed
the current level of the WebSphere Application Server group PTF, the maintenance
package containing the fix pack was placed in the
updi_root/maintenance
directory for you and you do not need to perform this step.
Tip: Do
not attempt to unzip or unpack the *.pak file.
Make sure that all application servers are stopped.
Run the stopServer command on all WebSphere
Application Server profiles.
Stop all processes that use the WebSphere Application
Server product. Before installing or uninstalling interim fixes,
fix packs, and refresh packs on a machine, stop all Java processes on the
machine that use the WebSphere Application Server product.
WebSphere
Application Server processes include:
- Application server processes
- The nodeagent process on an application server node when the node is federated
into a deployment manager cell
- The dmgr process for the deployment manager server
See Shutting down the WebSphere Application Server subsystem to
stop all processes.
Stop all Java processes that use the IBM Software
Developer Kit (SDK) that the WebSphere Application Server 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 Application Server provides.
![[i5/OS]](../../iseries.gif)
WebSphere
Application Server processes include:
- Application server processes
- The nodeagent process on an application server node when the node is federated
into a deployment manager cell
- The dmgr process for the deployment manager server
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
Stop all WebSphere Application Server-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 Application Server processes:
WebSphere
Application Server processes include:
- Application server processes
- The nodeagent process on an application server node when the node is federated
into a deployment manager cell
- The dmgr process for the deployment manager server
- IBM HTTP Server processes
- Web server processes that use a plug-in that you are updating
- First steps consoles
- Installation verification test (IVT) processes
- The Profile Management tool
- Other InstallShield for Multiplatforms (ISMP) installation programs
- InstallShield for Multiplatforms uninstall programs
- The IBM Rational Application Developer Agent Controller
Stop all Java processes if necessary. If you install
an interim fix while a WebSphere Application Server-related Java process runs,
IBM does not guarantee that the product can continue to run successfully,
or without error.
See the following technote for more
information, Stop all WebSphere Application Server-related
Java processes before using the Update Installer for WebSphere software.
Verify that the following prerequisite
conditions are met:
Follow the instructions for installing the maintenance
package. If you obtained the fix or refresh pack by installing
the Websphere Application Server group PTF, the instructions for installing
the fix or refresh pack can be found in file: updi_root/ReadmeV61.html or updi_root/ReadmeV61.txt.If
you downloaded the maintenance package from the Support site, the instructions
are contained in the readme file link found on the download page.
Install
the maintenance package on the deployment manager installation before installing
the maintenance package on each application server installation that you intend
to update.
Change directories to the updi_root 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 application 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 in two modes: the silent
mode, as a background process, and the regular mode, using the graphical user
interface. The Update Installer wizard does not display the graphical user
interface when running in silent mode.
![[i5/OS]](../../iseries.gif)
For i5/OS,
only the silent mode is supported.
update -options responsefile
update.bat -silent -options responsefile
update.exe -silent -options responsefile
./update.sh -silent -options responsefile
newfeatThe procedure using the Feature Pack
for Web Services to uninstalling a fix pack, or interim fix, or interim feature
are similar when using the silent uninstall. For more information about uninstalling
using the silent uninstall, refer to Uninstalling a fix pack, an interim fix, a test fix using the silent uninstall.
Or, issue the update command
to start the graphical user interface:
update.bat
update.exe
./update.sh
newfeatThe procedure for uninstalling is similar
for both fix packs, interim fixes, or interim features. Uninstall only one
fix pack, or interim fix, or interim feature at a time. To find out more about
uninstalling a fix pack or refresh pack, refer to Uninstalling a fix pack, interim fix, interim feature or test fix using the graphic user interface for more information.
The following tables show
options that are available when using the update command.
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
The commands in the first table each start the Update Installer
wizard with a graphical user interface.
The command in the second table causes the
Update Installer wizard to run in silent mode.
Table 2. Update installer commands for installing with the graphical interface
Command example |
Description |
update.bat |
Initializes the maintenance package field with the name
of the maintenance package that has the most recent date stamp and time stamp. Accept
all of the default values to install the maintenance package with the most
recent time stamp.
|
update.bat -options "responsefiles/file_name" |
Overrides all graphical interface values with values
that you specified in the options response file. Always use a response
file that is based on the response file under updi_root/responsefiles.
|
update.bat -W maintenance.package="e: \IBM\WebSphere\AppServer
\updateinstaller\maintenance\ PQ20029.pak" |
Overrides the name of the maintenance package to apply. |
update.bat -W product.location="e: \IBM\WebSphere\AppServer" |
Overrides the location of the WebSphere software to
update. |
update.bat -W product.location="e: \IBM\WebSphere\AppServer"
-W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\
PQ20029.pak" |
Overrides the location of the WebSphere software to
update and the name of the maintenance package to apply. |
update.bat -OPT disableDiskSpaceCheck=true |
Overrides the prerequisite check for disk space. |
Recommendation: Use the Submit Job
(SBMJOB) CL command to run the update script as a batch job. This allows the
job to run in a single storage pool and can improve the performance of the
update. The following example submits the update as a batch job running in
the QBATCH subsystem:
SBMJOB CMD(STRQSH CMD('was_install_root/updi_root/update'))
JOB(UPDATE) ALWMLTTHD(*YES)
Specify an appropriate JOBQ
parameter value to have the job run in a different subsystem. Verify that
the storage pool that the job runs in has as much memory as possible.
The command in the following table starts
the Update Installer wizard in silent mode without the graphical user interface:
Table 3. Update Installer command for installing in silent mode
Command example |
Description |
update.bat -silent -options "responsefiles/file_name" |
Overrides all default values with values that you specified
in the options response file. Always use a response file that is based
on the response file under updi_root/responsefiles.
|
For i5/OS, only the silent mode is supported.
update -options responsefile
newfeatThe procedure using the Feature Pack
for Web Services to uninstalling a fix pack, or interim fix, or interim feature
are similar when using the silent uninstall. For more information about uninstalling
using the silent uninstall, refer to Uninstalling a fix pack, an interim fix, a test fix using the silent uninstall.
What to do next
Click Relaunch on the last
panel of the Update Installer to begin installing a second maintenance package.
After
installing all maintenance packages, continue to use your WebSphere software.