IBM Tivoli Composite Application Manager for WebSphere V6.1
Readme for the update installer V6.1.0
Jan 14, 2009
Contents
3.2 Unpacking the Update Installer
3.4 Updating the Response File
3.5 Creating dcInputs.txt - for IBM i5/OS only
3.7 Cleaning Prepared Installation
3.9 Rolling Back Failed Installation
4.1 Unpacking the Update Installer
4.3 Updating the Response File
4.5 Cleaning Prepared Uninstallation
4.7 Rolling Back Failed Uninstallation
5 Displaying Installed Updates
5.1 Unpacking the Update Installer
The Update Installer for IBM Tivoli Composite Application Manager for WebSphere V6.1 provides the following functionality:
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.
6.1.0 January 11, 2007
First release.
This section describes how to install Fix Packs and interim fixes.
Note: For 6.1 FP4, the Update Installer is packaged with the MS and DC package, so the Update Installer package (ITCAM_V61_UpdateInstaller.tar) is no longer used.
The Fix Packs and interim fixes are distributed as tar files. Create a temporary directory, put the update package there and un-tar.
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.1.0-TIV-ITCAMfWAS_MP-FP0004.tar
silentUpdate.sh
updates/
6.1.0-TIV-ITCAMfWAS_MP-FP0004.README
ITCAM_V61_UpdateInstaller.htm
ITCAM_V61_UpdateInstaller.pdf
Notices_Supp1_05052008
configUtil.jar
silentUpdate.bat
silentUpdate.properties
update.jar
updates/6.1.0-TIV-ITCAMfWAS_MP-FP0004.update
IBM i5/OS: use /qopensys/usr/bin/tar
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.4 or higher. Define the JAVA_HOME environment variable to point to the Java Runtime Environment provided with the Data Collector (or Managing Server) installation.
For example, on UNIX or Linux, run:
JAVA_HOME=<DC_HOME>/_jvm/jre
export JAVA_HOME
These are the defaults for <DC_HOME>/_jvm/jre:
- UNIX and Linux: /opt/IBM/itcam/WebSphere/DC/_jvm/jre
- Windows: C:\Program Files\IBM\itcam\WebSphere\DC\_jvm\jre
Note: JAVA_HOME for IBM Tivoli Composite Application Manager for J2EE V6.1:
<DC_HOME>/installer/_uninst/java/jre
IBM i5/OS: use standard JDK 1.4:
export JAVA_HOME= /qibm/proddata/java400/jdk14
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.location
property with the directory that contains the *.update files.
If the Visualization 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_PROFILE_HOME of the Visualization Engine application server.
If the Visualization Engine is installed on a WebSphere Network Deployment, use SOAP connection to install the update. For that uncomment and set the following properties in the silentUpdate.properties file:
updateVe.was.soap.host=<HOST>
updateVe.was.soap.port=<PORT>
If WebSphere Security is enabled, uncomment and set the following properties:
updateVe.was.user=<WAS USER>
updateVe.was.password=<WAS PASSWORD>
Note: WebSphere Deployment Manager and
Node Agent should be in running state.
If the Data Collector is configured on a WebSphere Network Deployment and WebSphere Security is enabled the following properties must be specified:
connection.user=<WAS USER>
connection.password=<WAS PASSWORD>
Note: WebSphere Deployment Manager and Node Agent should be in running state.
Using
user and password information specified in
the *.client.props file
To retrieve user name and password from
*.client.props file set the following property in the
silentUpdate.properties file:
connection.useClientProps=true
If SOAP connection is used, the user name and password will be retrieved from the soap.client.props file.
If RMI connection is used (for Data Collector only), the user name and password will be retrieved from the sas.client.props file.
Note: Do not set connection.useClientProps=true if user name and password are not specified in the *.client.props file, it may lead to hang of UpdateInstaller.
If you specify user and password information in the silentUpdate.properties file and set connection.useClientProps=true, the silentUpdate.properties file information overrides the information in the *.client.props file.
Note: the response file is Java Properties file. Any backward-slashes should be doubled, for example:
product.location= C:\\Program Files\\IBM\\itcam\\WebSphere\\DC
Update installer uses the dcInputs.txt file created for the installation of the Data Collector on IBM i5/OS.
Check that this file exists in the <DC_HOME>/config_dc directory.
If the file does not exist, create and customize it as described in the WebSphereDistributed Data Collector Installation and Customization Guide: Chapter 19. Silent Installation and configuration for the Data Collector on IBM i5/OS and save it to the <DC_HOME>/config_dc directory.
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -prepareInstall my.properties
A typical output of the -prepareInstall command is:
>./silentUpdate.sh -prepareInstall
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: prepare install
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -cleanPrepared my.properties
A typical output of the -cleanPrepared command is:
>./silentUpdate.sh -cleanPrepared
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: clean prepared
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -install my.properties
A typical output of the -install command is:
>./silentUpdate.sh -install
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: install
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -rollback my.properties
A typical output of the -rollback command is:
>./silentUpdate.sh -rollback
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: rollback
Finished successfully
This section describes how to uninstall Fix Packs and interim fixes.
See Unpacking Update in section 3.1 for information on unpacking the Update Installer.
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.4 or higher. Define the JAVA_HOME environment variable to point to the Java Runtime Environment provided with the Data Collector (or Managing Server) installation.
For example, on UNIX or Linux, run:
JAVA_HOME=<DC_HOME>/_jvm/jre
export JAVA_HOME
These are the defaults for <DC_HOME>/_jvm/jre:
- UNIX and Linux: /opt/IBM/itcam/WebSphere/DC/_jvm/jre
- Windows: C:\Program Files\IBM\itcam\WebSphere\DC\_jvm\jre
Note: JAVA_HOME for IBM Tivoli Composite Application Manager for J2EE V6.1:
<DC_HOME>/installer/_uninst/java/jre
IBM i5/OS: use standard JDK 1.4:
export JAVA_HOME= /qibm/proddata/java400/jdk14
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 Visualization 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 Visualization Engine application server.
If the Visualization Engine is installed on a WebSphere Network Deployment, use SOAP connection to install the update. For that uncomment and set the following properties in the silentUpdate.properties file:
updateVe.was.soap.host=<HOST>
updateVe.was.soap.port=<PORT>
If WebSphere Security is enabled, uncomment and set the following properties:
updateVe.was.user=<WAS USER>
updateVe.was.password=<WAS PASSWORD>
Note: WebSphere Deployment Manager and
Node Agent should be in running state.
If the Data Collector is configured on a WebSphere Network Deployment and WebSphere Security is enabled the following properties must be specified:
connection.user=<WAS USER>
connection.password=<WAS PASSWORD>
Note: WebSphere
Deployment Manager and Node Agent should be in running state.
Using
user and password information specified in the *.client.props
file
To retrieve user name and password from *.client.props file
set the following property in the silentUpdate.properties file:
connection.useClientProps=true
If SOAP connection is used, the user name and password will be retrieved from the soap.client.props file.
If RMI connection is used (for Data Collector only), the user name and password will be retrieved from the sas.client.props file.
Note: Do not set connection.useClientProps=true if user name and password are not specified in the *.client.props file, it may lead to hang of UpdateInstaller.
If you specify user and password information in the silentUpdate.properties file and set connection.useClientProps=true, the silentUpdate.properties file information overrides the information in the *.client.props 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.1.0.1, 6.1.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\\itcam\\WebSphere\\DC
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -prepareUninstall my.properties
A typical output of the -prepareUninstall command is:
>./silentUpdate.sh -prepareUninstall
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: prepare uninstall
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -cleanPrepared my.properties
A typical output of the -cleanPrepared command is:
>./silentUpdate.sh -cleanPrepared
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: clean prepared
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -uninstall my.properties
A typical output of the -uninstall command is:
>./silentUpdate.sh -uninstall
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: uninstall
Finished successfully
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -rollback my.properties
A typical output of the -rollback command is:
>./silentUpdate.sh -rollback
Update installer version 6.1.0
Logging details into C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20050916213723.log
Action: rollback
Finished successfully
This section describes how to display a list of the installed Fix Packs and interim fixes.
See Unpacking Update in section 3.1 for information on unpacking the Update Installer.
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.4 or higher. Define the JAVA_HOME environment variable to point to the Java Runtime Environment provided with the Data Collector (or Managing Server) installation.
For example, on UNIX or Linux, run:
JAVA_HOME=<DC_HOME>/_jvm/jre
export JAVA_HOME
These are the defaults for <DC_HOME>/_jvm/jre:
- UNIX and Linux: /opt/IBM/itcam/WebSphere/DC/_jvm/jre
- Windows: C:\Program Files\IBM\itcam\WebSphere\DC\_jvm\jre
Note: JAVA_HOME for IBM Tivoli Composite Application Manager for J2EE V6.1:
<DC_HOME>/installer/_uninst/java/jre
IBM i5/OS: use standard JDK 1.4:
export JAVA_HOME= /qibm/proddata/java400/jdk14
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
Note: the response file is Java Properties file. Any backward-slashes should be doubled, for example:
product.location=C:\\Program Files\\IBM\\itcam\\WebSphere\\DC
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, Linux and i5/OS:
./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, Linux and i5/OS:
./silentUpdate.sh -displayInstalledUpdates my.properties
A typical output of the - displayInstalledUpdates command is:
>./silentUpdate.sh - displayInstalledUpdates
Update installer version 6.1.0
Logging details into
C:\Program Files\IBM\itcam\WebSphere\DC\logs\update\update_20060121163339.log
Action: display installed updates
Updates installed 21.02.06 16:43
6.1.0
Finished successfully