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.
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, the product might
not continue to run successfully.
8. Choose to install the product in silent
or graphical user interface mode. Install
the maintenance package on the deployment manager node before installing
the maintenance package on each application server node that you intend
to update.
For more information on root versus non-root for
installing maintenance with the Update Installer, refer to Using root or non-root when installing with the Update Installer.
The
Update Installer wizard runs in two modes: the silent mode, as a background
process, and the regular mode, using the graphical user interface.
- Silent mode
The Update Installer wizard does not display
the graphical user interface when running in silent mode. The following
commands initiate a silent installation:
update.bat -silent -options responsefile
update.exe -silent -options responsefile
./update.sh -silent -options responsefile
- Graphical user interface mode
Issue the update command to start the
graphical user interface:
update.bat
update.exe
./update.sh
The following tables show options that are available when
using the update command.
Table 1. Update installer commands
for installing with the graphical interface. This table
contains commands for the graphical user 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. |
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.
Table 2. Update Installer
command for installing in silent mode. The command
in the following table starts the Update Installer wizard in silent
mode without the graphical user interface.
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.
|
Optional: Re-apply any ownership and permissions changes
that were made after the product was originally installed. You
must complete this step if the user owner, group owner, or permissions
of any product files has changed prior to the installation or removal
of a fix pack.
In some situations, the user ownership, group
ownership, and permissions of the product files, including files that
are associated with profiles, might have been changed after the product
was installed. For example, you might have installed the product
as the root user, and then afterward changed the file ownership to
a non-root user. Typically, the a command, such as chown or chmod is
used to change the ownership of these files.
When a fix pack
is either installed or uninstalled, the UpdateInstaller might change
the ownership and permissions of the product files, including the
files that are associated with profiles. The changed ownership and
permissions might interfere with starting application servers or using
certain features.
To prevent this interference, you must re-apply
any ownership and permissions changes that were made after the product
was originally installed. For example, if the ownership was changed
from root user to non-root user, and then the UpdateInstaller is run
as root user to install a fix pack, the file ownership needs to be
changed back to non-root user after the fix pack is installed or removed.
Avoid trouble: When using the
chown or
chmod commands,
you must apply the changes to
* instead of
*.*.
Using
*.*does not sufficiently update all
product files.
gotcha