updateSilent examples for cumulative fixes and fix packs: WAS ND

updateSilent examples for cumulative fixes and fix packs

The updateSilent command is the silent, command-line interface for the update installer program. This topic describes using the wizard to work with cumulative fixes and fix packs.

The update installer program installs interim fixes, cumulative fixes, and fix packs to WebSphere Application Server products. See updateWizard examples for interim fixes for information about using the update silent interface to work with interim fixes.

The relationship among interim fixes, cumulative fixes, and fix packs is shown in the Cumulative Fix Strategy for WebSphere Application Server V5.0 and V5.1 Web page.

Syntax examples

The updateSilent interface actually provides two functions. Depending upon the parameters you choose, the command performs the following functions:

Installs and uninstalls interim fixes, cumulative fixes, and fix packs

Provides information about the update state of interim fixes, cumulative fixes, and fix packs that you install or uninstall

The following examples describe various usage syntaxes. In each syntax example, optional parameters are enclosed by brackets ([]). Values that supply appear in italicized font. Choices are denoted by the pipe symbol (|).

Help

updateSilent -help | -? | -usage updateSilent /help | /? | -usage (Windows platforms)

Syntax for using a properties file to supply values

updateSilent myProps.properties

Syntax for processing cumulative fixes and fix packs

updateSilent -installDir "fully qualified product install_root" -fixpack -fixpackDir "fully qualified FixPack repository root, usually install_root/update/fixpacks" -install | -uninstall -fixPackID fix pack ID [-skipIHS | [-ihsOnly] -ihsInstallDir fully qualified IBM HTTP Server root] [-skipMQ | -mqInstallDir embedded messaging feature root] [-includeOptional space-delimited list of components] [-fixpackDetails]

All other valid arguments are ignored, such as the prereqOverride argument, which is for interim fix processing only.

You do not need to supply the -mqInstallDir argument for AIX, Linux, and UNIX-based platforms. The install location is fixed on those operating platforms. Use the argument on Windows platforms. The default location on Windows platforms is the C:\Program Files\IBM\WebSphere MQ directory.

Syntax for viewing installed cumulative fixes and fix packs

updateSilent -fixpack -installDir "fully qualified product install_root"

Syntax for viewing available cumulative fixes and fix packs

updateSilent -fixpack -installDir "fully qualified product install_root" -fixpackDir "fully qualified fix pack repository root, usually install_root/update/fixpacks"

Parameters

Use the following parameters for the updateSilent command:

-?

Shows command usage.

/?

Shows command usage on Windows platforms only.

-fixpack

Fix pack only: Identifies the update as a fix pack update.

-fixpackDetails

Fix pack only: Displays fix pack detail information.

-fixpackDir

Fix pack only: Specifies the fully qualified directory where you download and unpack fix packs. By default, this directory is the install_root/update/fixpacks directory.

-fixpackID

Fix pack only: Specifies the ID of a fix pack to install or uninstall. The value you specify does not include the .jar extension. The value is not the fully qualified package file name, but is the name of the individual fix pack within the JAR file.
The current Application Server strategy for fix pack JAR files uses one JAR file per fix pack. The fix pack ID is the name of the JAR file before the .jar extension.

For example:

Fix pack ID: was51_fp1_linux

Fix pack JAR file name: was51_fp1_linux.jar

Fix pack ZIP file name: was51_fp1_linux.zip

-help

Shows command usage.

/help

Shows command usage on Windows platforms only.

-ihsInstallDir

Fix pack only: Specifies the fully qualified path of the IBM HTTP Server product, and applies any service for the IBM HTTP Server product that might exist in the fix pack.
Important: Cumulative fixes and fix packs do not include service for the IBM HTTP Server powered by Apache 2.0. If you installed IBM HTTP Server powered by Apache 2.0, skip applying service to the IBM HTTP Server during the installation of a cumulative fix or a fix pack. Do not update the 2.0 level IBM HTTP Server with service for the 1.3 level IBM HTTP Server.

-ihsOnly

Fix pack only: Skips the installation of all service but that for the IBM HTTP Server product, and applies any service for the IBM HTTP Server product that might exist in the fix pack. Requires the -ihsInstallDir parameter.
Important: Cumulative fixes and fix packs do not include service for the IBM HTTP Server powered by Apache 2.0. If you installed IBM HTTP Server powered by Apache 2.0, skip applying service to the IBM HTTP Server during the installation of a cumulative fix or a fix pack. Do not update the 2.0 level IBM HTTP Server with service for the 1.3 level IBM HTTP Server.

-includeOptional

Fix pack only: Specifies a space-delimited list of features. The installer program applies any service for the components, if present in the fix pack. Otherwise, the installer program does not apply the service.

-install

Installs the update type.

-installDir

Specifies the fully qualified installation root of the WebSphere Application Server product.

-mqInstallDir

Fix pack only: Specifies the fully qualified installation root of the embedded messaging feature, which is based on WebSphere MQ technology.

<propertyFile>.properties

Specifies an externally supplied parameters file.
You can supply parameters in an external .properties file, rather than directly on the command line. There are some differences in the formats of parameters:

You must include all parameters.

Parameters are [name]=[value] pairs.

Lists of parameter values are comma-delimited instead of space-delimited.

There are two slashes before directory names.

A sample.properties file for installing a fix pack might look like the following example:

-skipIHS

Fix pack only: Skips any optional service for the IBM HTTP Server product that might exist in the fix pack.
If you installed the IBM HTTP Server product as a feature, use the update installer program to update it with service in an interim fix or fix pack. Otherwise, download an updated IBM HTTP Server product from http://www.ibm.com/software/webservers/httpservers/ and install it into the same directory as your existing version, to update the existing installation. You can also uninstall the current version and install the downloaded version, to avoid any issues with migration.

You must update your configuration if you reinstall. The process is described in the Manually configuring supported Web servers (tins_manualWebServer) topic in the information center for the base Application Server product.

Important: Cumulative fixes and fix packs do not include service for the IBM HTTP Server powered by Apache 2.0. If you installed IBM HTTP Server powered by Apache 2.0, skip applying service to the IBM HTTP Server during the installation of a cumulative fix or a fix pack. Do not update the 2.0 level IBM HTTP Server with service for the 1.3 level IBM HTTP Server.

-skipMQ

Fix pack only: Specifies no application of any optional service for the embedded messaging feature (which is based on the IBM WebSphere MQ product) that might exist in the fix pack.
Always apply any outstanding corrective service to the stand-alone IBM WebSphere MQ product if you have it, before using the WebSphere Application Server update installer program to update the embedded messaging feature with service in an interim fix or fix pack. You can skip the installation of service to the embedded messaging feature if install corrective service to the stand-alone IBM WebSphere MQ product.

-uninstall

Specifies to uninstall the identified interim fix, cumulative fix, or fix pack. You must uninstall all interim fixes, cumulative fixes, and fix packs before uninstalling a WebSphere Application Server product. However, if you are manually uninstalling all WebSphere Application Server products from the machine, it is not necessary to uninstall all interim fixes, cumulative fixes or fix packs. See Uninstalling manually for more information.

-usage

Shows command usage.

Examples overview

The following examples assume that:

The installation root is the C:\WebSphere\AppServer directory.

The location of the IBM HTTP Server feature is the C:\Program Files\IBMHttpServer directory.

The interim fix repository is the C:\WebSphere\AppServer\update\fixes directory.

The cumulative fix and fix pack repository is the C:\WebSphere\AppServer\update\fixpacks directory.
Examples in this section include:

Getting help for the command

Using a parameter properties file

Installing cumulative fixes and fix packs

Uninstalling cumulative fixes and fix packs

Viewing information about cumulative fixes and fix packs
Most of the examples are split into more than one line, for ease of publication.

Getting help for the command

To get help for the updateSilent command:

C:\WebSphere\AppServer\update> updateSilent -help

Using a parameter properties file

To use the myProps.properties file to supply parameter values for the updateSilent command:

C:\WebSphere\AppServer\update> updateSilent myProps.properties

Installing cumulative fixes and fix packs

To install a fix pack:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -ihsInstallDir "C:\Program Files\IBMHttpServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -install -fixpackID was510_cf2_win

To install a fix pack, and display fix pack details:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -ihsInstallDir "C:\IBMHttpServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -install -fixpackID was510_cf2_win -fixpackDetails

To perform a partial installation of a fix pack, by choosing to skip the installation of optional service to the WebSphere Application Server embedded messaging feature, which is based on WebSphere MQ:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -ihsInstallDir "C:\Program Files\IBMHttpServer" -install -fixpackID was510_cf2_win -skipMQ
The fix pack status shows partial installation.

About installation status

An interim fix or a fix pack is a collection of updates to one or more product components. Depending on installed product components and on update installer program selections you make, the update installer program applies either a full or partial set of interim fix or fix pack updates to product components.

Installed status implies that the interim fix or fix pack has no more updates to product components that you can install.

Partially installed status implies that you have updated one or more product components, but the interim fix or fix pack has at least one more update you can apply to an installed product component. (There might be other updates to product components you never installed. These updates do not count in the status determination.)

Uninstalled status implies that you have not updated a single product component.

Examples of partially installed states: Several scenarios can lead to a partial installation of an interim fix or fix pack:

Installation fails, leaving some component updates applied and some unapplied. This is a partial installation accompanied by error messages that describe the problem.

You select to skip certain optional component updates, such as might be present in a fix pack for these features: IBM HTTP Server or embedded messaging. This is a partial installation.

You trigger a dynamic change in interim fix or fix pack status because:

You apply all changes in an interim fix or fix pack that results in an installed status.

You reinstall the WebSphere Application Server product to select an additional, optional feature.

The interim fix or fix pack contains an update to a product component you just installed.
The status changes dynamically from installed to partially installed.

How to distinguish between a normal partially installed state and an installation failure

A partially installed state implies that some components on the system are at the level of the fix pack being applied. However, there might be some scenarios where the update installer program can report a partially installed state even if no components are at the newer level. A partially installed state does not imply a failed install. However, a failed install does result in a partially installed state.

To check for a failed install, open the master log file and search for errors. The update installer program outputs the name of the master log file at the start of the installation process. The file name matches this pattern: install_root/logs/update/time-stamp_was51_fpnumber_platform_selective-install.log

To perform a partial installation of a fix pack by choosing to skip the installation of optional service to the IBM HTTP Server feature:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -mqInstallDir "C:\WebSphere MQ" -install -fixpackID was510_cf2_win -skipIHS
The fix pack status shows partial installation.

To perform a partial installation of a fix pack, by choosing to skip the installation of optional service to both the embedded messaging feature and the IBM HTTP Server feature:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks" -install -fixpackID was510_cf2_win -skipIHS -skipMQ
The fix pack status shows partial installation.

Uninstalling cumulative fixes and fix packs

To uninstall a fix pack:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -uninstall -fixpackID was510_cf2_win

To uninstall a fix pack, and display fix pack details:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -uninstall -fixpackID was510_cf2_win -fixpackDetails

Viewing information about cumulative fixes and fix packs

To view a list of installed fix packs:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer"

To view a list of fix packs available in the repository for the base WebSphere Application Server product:

C:\WebSphere\AppServer\update> updateSilent -fixpack -installDir "C:\WebSphere\AppServer" -fixpackDir "C:\WebSphere\AppServer\update\fixpacks"

updateSilent command
updateWizard examples for cumulative fixes and fix packs