A silent command-line update installer.
Installation and removal of individual or multiple updates (Fix Packs and interim fixes).
Logging, tracking and prerequisites handling.

This readme describes how to use the update installer.

2 Change History

6.0.0.2 February 27, 2006

Added new command-line options: -displayInstalledUpdates, -cleanPrepared, -rollback.
Bug fixes

6.0.0.1 December 14, 2005

First release.

3 Installing Updates

This section describes how to install Fix Packs and interim fixes.

3.1 Unpacking Update

The Fix Packs and interim fixes are distributed as tar files. Create a temporary directory, put the update package there and un-tar. Ensure that only DC tar files are extracted for a DC fix pack upgrade. Having DC and MS tar files extracted together in the same directory will lead to error during install.

After un-taring the update package you should get the updates directory that contains the file with the *.update extension. For example:

>tar xvf 6.0.0.1-TIV-ITCAMfWAS_MP-IF0002.tar

6.0.0.1-TIV-ITCAMfWAS_MP-IF0002.README

updates/

updates/6.0.0.1-TIV-ITCAMfWAS_MP-IF0002.update

3.2 Unpacking the Update Installer

Copy the update installer tar to the same directory were you un-tared the update package. This directory will typically contain the updates subdirectory. Un-tar the update installer package using the tar command, for example:

>tar xvf ITCAMfWAS_V6_UpdateInstaller.tar

silentUpdate.bat

silentUpdate.properties

silentUpdate.sh

update.jar

The resulting directory structure will contain both, the update installer and the update file. For example:

silentUpdate.bat

silentUpdate.properties

silentUpdate.sh

update.jar

6.0.0.1-TIV-ITCAMfWAS_MP-IF0002.README

updates/6.0.0.1-TIV-ITCAMfWAS_MP-IF0002.update

3.3 Preparing Environment

Before running the update installer you should login as root (Administrator) or owner of the product directory. Then update the environment as below.

The update installer requires the Java Runtime Environment version 1.3.1 or higher. Either include the java command into PATH or define the JAVA_HOME environment variable to point to the Java Runtime Environment home directory. It is recommended to use the JRE which comes with the WebSphere Installation located at $WAS_HOME/java.

For example, on UNIX or Linux, run:

JAVA_HOME=/opt/WebSphere/AppServer/java

export JAVA_HOME

3.4 Updating the Response File

The update installer is a non-interactive silent installer that works based on the response file. The default name of the response file is silentUpdate.properties and it is supplied with the update installer. Update the response file as follows:

Set the product.location property with the correct product location directory
Optionally, if the *.update files are not in default ./updates directory, then set the updates.loction property with the directory that contains the *.update files.
If the Visual Engine was not installed to the Managing Server runtime to be updated then set the updateVe property to false. Otherwise uncomment and set the updateVe.wasHome property with WAS_HOME of the Visual Engine application server. For WebSphere 6.x, WAS_HOME should be set to the profile location and set the following properties additionally; updateVe.was.node & updateVe.was.server
For Websphere 6.1 DC install, set wasInfo.wasHome property to specify the profile location that contains server to be configured with DC. Also, while applying fix for the first time on WebSphere 6.1 it's necessary to set properly wasPlugins.location in the response file.

Note: the response file is Java Properties file. Any backward-slashes should be doubled, for example:

product.location=C:\\Program Files\\IBM\\WSAM

3.5 Preparing Installation

To reduce the application server or Managing Server down-time the update installer allows to prepare installation while the product is running. This steps is optional but is recommended.

In order to prepare installation change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –prepareInstall

UNIX or Linux:

./silentUpdate.sh -prepareInstall

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -prepareInstall my.properties

UNIX or Linux:

./silentUpdate.sh -prepareInstall my.properties

A typical output of the -prepareInstall command is:

>./silentUpdate.sh -prepareInstall

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: prepare install

Finished successfully

3.6 Cleaning Prepared Installation

If you decide to not install the update after you already run -prepareInstall then you can clean results of the ‘-prepareInstall’ command. In order to do that change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –cleanPrepared

UNIX or Linux:

./silentUpdate.sh –cleanPrepared

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -cleanPrepared my.properties

UNIX or Linux:

./silentUpdate.sh -cleanPrepared my.properties

A typical output of the -cleanPrepared command is:

>./silentUpdate.sh -cleanPrepared

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: clean prepared

Finished successfully

3.7 Installing

It is recommended that you run the -prepareInstall command before installing the update, see the previous section for details.

Before installing the update you should stop the product that you will update, i.e. the application server being monitored or the Managing Server components.

After you stopped the product change to the directory where the update installer scripts are stored and run the following command.

Windows:

silentUpdate.bat –install

UNIX or Linux:

./silentUpdate.sh -install

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -install my.properties

UNIX or Linux:

./silentUpdate.sh -install my.properties

A typical output of the -install command is:

>./silentUpdate.sh -install

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/logs/update/update_20050916213723.log

Action: install

Finished successfully

3.8 Rolling Back Failed Installation

If the -install command fails and the automatic rollback fails also then the runtime will be locked for the updates until the rollback is completed successfully. In order to complete the rollback successfully do the following:

Review the update installer log and resolve the cause of the rollback failure.
Change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –rollback

UNIX or Linux:

./silentUpdate.sh –rollback

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -rollback my.properties

UNIX or Linux:

./silentUpdate.sh -rollback my.properties

A typical output of the -rollback command is:

>./silentUpdate.sh -rollback

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: rollback

Finished successfully

4 Uninstalling Updates

This section describes how to uninstall Fix Packs and interim fixes.

4.1 Unpacking the Update Installer

The all necessary uninstall information is stored to the product directory under the update sub-directory. You don’t need the original update package in order to uninstall it. So download the latest update installer and un-tar it:

>tar xvf ITCAMfWAS_V6_UpdateInstaller.tar

silentUpdate.bat

silentUpdate.properties

silentUpdate.sh

update.jar

4.2 Preparing Environment

Before running the update installer you should login as root (Administrator) or owner of the product directory. Then update the environment as below.

For example, on UNIX or Linux, run:

JAVA_HOME=/opt/WebSphere/AppServer/java

export JAVA_HOME

4.3 Updating the Response File

The update installer is non-interactive silent installer that works based on the response file. The default name of the response file is silentUpdate.properties and it is supplied with the update installer. Update the response file as follows:

Set the product.location property with the correct product location directory.

Optionally, if the *.update files are not in default ./updates directory, then set the updates.loction property with the directory that contains the *.update files.
If the Visual Engine was not installed to the Managing Server runtime to be updated then set the updateVe property to false. Otherwise uncomment and set the updateVe.wasHome property with WAS_HOME of the Visual Engine application server. For WebSphere 6.x, WAS_HOME should be set to the profile location and set the following properties additionally; updateVe.was.node & updateVe.was.server
For Websphere 6.1 DC uninstall, set wasInfo.wasHome property to specify the profile location that contains server to be configured with DC. Also, while applying fix for the first time on WebSphere 6.1 it's necessary to set properly wasPlugins.location in the response file.

Set the uninstall.updates property with the one of possible values:

all – uninstall all updates
last – uninstall the updates installed by the last -install command
<comma separated list of updates> -- uninstall the specified updates. The updates are specified by their identifiers as displayed by the –listInstalledUpdates command. (f.e. 6.0.0.1, 6.0.0.1.1)

Note: the response file is Java Properties file. Any backward-slashes should be doubled, for example:

product.location=C:\\Program Files\\IBM\\WSAM

4.4 Preparing Uninstallation

To reduce the application server or Managing Server down-time the update installer allows to prepare uninstallation while the product is running. This steps is optional but is recommended.

In order to prepare uninstallation change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –prepareUninstall

UNIX or Linux:

./silentUpdate.sh -prepareUninstall

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -prepareUninstall my.properties

UNIX or Linux:

./silentUpdate.sh -prepareUninstall my.properties

A typical output of the -prepareUninstall command is:

>./silentUpdate.sh -prepareUninstall

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: prepare uninstall

Finished successfully

4.5 Cleaning Prepared Uninstallation

If you decide to not uninstall after you already run -prepareUninstall then you can clean results of the ‘-prepareUninstall’ command. In order to do that change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –cleanPrepared

UNIX or Linux:

./silentUpdate.sh –cleanPrepared

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -cleanPrepared my.properties

UNIX or Linux:

./silentUpdate.sh -cleanPrepared my.properties

A typical output of the -cleanPrepared command is:

>./silentUpdate.sh -cleanPrepared

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: clean prepared

Finished successfully

4.6 Uninstalling

It is recommended that you run the -prepareUninstall command before uninstalling the update, see the previous section for details.

Before uninstalling the update you should stop the product that you will update, i.e. the application server being monitored or the Managing Server components.

After you stopped the product change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –uninstall

UNIX or Linux:

./silentUpdate.sh -uninstall

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -uninstall my.properties

UNIX or Linux:

./silentUpdate.sh -uninstall my.properties

A typical output of the -uninstall command is:

>./silentUpdate.sh -uninstall

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: uninstall

Finished successfully

4.7 Rolling Back Failed Uninstallation

If the -uninstall command fails and the automatic rollback fails also then the runtime will be locked for the updates until the rollback is completed successfully. In order to complete the rollback successfully do the following:

Review the update installer log and resolve the cause of the rollback failure.
Change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –rollback

UNIX or Linux:

./silentUpdate.sh –rollback

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -rollback my.properties

UNIX or Linux:

./silentUpdate.sh -rollback my.properties

A typical output of the -rollback command is:

>./silentUpdate.sh -rollback

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/MS/logs/update/update_20050916213723.log

Action: rollback

Finished successfully

5 Displaying Installed Updates

This section describes how to display a list of the installed Fix Packs and interim fixes.

5.1 Unpacking the Update Installer

Download the latest update installer and un-tar it:

>tar xvf ITCAMfWAS_V6_UpdateInstaller.tar

silentUpdate.bat

silentUpdate.properties

silentUpdate.sh

update.jar

5.2 Preparing Environment

Before running the update installer you should login as root (Administrator) or owner of the product directory. Then update the environment as below.

For example, on UNIX or Linux, run:

JAVA_HOME=/opt/WebSphere/AppServer/java

export JAVA_HOME

5.3 Updating the Response File

Set the product.location property with the correct product location directory

Note: the response file is Java Properties file. Any backward-slashes should be doubled, for example:

product.location=C:\\Program Files\\IBM\\WSAM

5.4 Displaying Installed Updates

To display a list of the installed Fix Packs and interim fixes change to the directory where the update installer scripts are stored and run the following command:

Windows:

silentUpdate.bat –displayInstalledUpdates

UNIX or Linux:

./silentUpdate.sh -displayInstalledUpdates

If your response file is named differently then the default silentUpdate.properties then specify it as a parameter:

Windows:

silentUpdate.bat -displayInstalledUpdates my.properties

UNIX or Linux:

./silentUpdate.sh -displayInstalledUpdates my.properties

A typical output of the - displayInstalledUpdates command is:

>./silentUpdate.sh - displayInstalledUpdates

Update installer version 6.0.0.2

Logging details into /opt/IBM/itcam/WebSphere/DC/logs/update/update_20060121163339.log

Action: display installed updates

Updates installed 21.02.06 16:43

6.0.0.1

Finished successfully