Softpanorama May the source be with you, but remember the KISS principle ;-)	Home	Switchboard	Unix Administration	Red Hat	TCP/IP Networks	Neoliberalism	Toxic Managers
	(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix

Uninstalling Tivoli Monitoring 5.1

News	Tivoli	Red Books	Recommended Links	wuninst command	Articles
Installation	Uninstalling	wdmdumpprf command	Tips	Humor	Etc

Uninstalling the product

This section describes how to uninstall the product components from endpoints, gateways, and servers, and how to remove the automatic endpoint reboot capability.

Note:

The Tivoli Monitoring Task Library is also uninstalled with the product. If it contains any user-defined tasks, they are lost. Therefore you should create any user-defined tasks in a separate library.

To uninstall the product follow either of these procedures:

Uninstall the endpoint components.
Uninstall from server and gateways.

or:

Uninstall from server and gateways and automatically uninstall all registered endpoints.

If reinstallation is planned then we can use the wdmdumpprf command to dump Tmw2kProfiles into xml files. After dumping the profiles, if at anytime in the future they must be reloaded, we can then use the wdmloadprf command.

I have a very simple script in my lab environment that grabs a list of all Tmw2kProfiles, then dumps the profiles to xml files, so your site could use something similar to this script.

Here is the sample script I use in my test environment:

cat ./backup_tmw2k-prf.sh

#!/usr/bin/sh

. /etc/Tivoli/setup_env94.sh

region=our-region

for profilename in `wlookup -ar Tmw2kProfile | grep -v @ | awk -F" " '{print $1}'`

do

wdmdumpprf -P $profilename#$region > /tmp/${profilename}.xml

done

exit 0

The xml files created by the wdmdumpprf command can then be stored in a safe location and your site can import the Tmw2kProfiles back in using the wdmloadprf command.

URL that documents the wdmdumpprf command: wdmdumpprf

by frank_tate on Mar 15, 2006 - 06:57 PM
(User information

It turns out that "most" newer Java installs include "xml.jar", which contains the Xalan XSLT processor. You can invoke it with:

java org.apache.xalan.xslt.Process

This class is in xml.jar on an AIX system, with:

[tivoli@testsysmgt3asjt:/usr/java14/jre/lib] $ ../bin/java -version
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM AIX build ca1411-20030930 (JIT enabled: jitc))

However, this file is NOT on a Windows system with:
C:\>java -version
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)

-- Frank

User's Guide

Uninstalling from servers and gateways

The Tivoli Management Framework provides the wuninst command to remove Tivoli applications from a specified node or from the entire region. You can use the wuninst command with product tags that are specific to Tivoli Monitoring to remove the product from any system in your environment or from the entire region.

In particular, use the -rmeps option to automatically uninstall also all registered endpoints.

When using the wuninst command, make sure you use it in this sequence:

Uninstall any Tivoli Monitoring components (for example: the Gathering Historical Data Component, or the Tivoli Business Systems Adapter)
Uninstall the Tivoli Monitoring base component (core product)

To uninstall the Tivoli Monitoring components from servers or gateways enter:

wuninst tagname destination_target -rmfiles

To uninstall the Tivoli Monitoring base component from servers or gateways enter:

wuninst tagname destination_target -rmfiles -rmeps

Where:

tagname

Is one of the registered product tags for IBM Tivoli Monitoring that are provided by Tivoli. List can be pobtained using

# wuninst -list
Creating Log File (/tmp/wuninst.log)...
------------------------------------------------
Uninstallable Products installed:
------------------------------------------------
ACF
TEC39_JRE
TEC_JCONSOLE
TEC_SERVER
TEC_UI_SRVR
TMNT_3.6.2

Note:

These tags do not indicate the version or release of the product)

DM_Advanced_Edition_TDS, to indicate Tivoli Decision Support for Server Performance Prediction.
DM_Advanced_Edition_TBSMA, to indicate Tivoli Business Systems Manager Adapter.
TMNT_3.6.2, to indicate Tivoli Monitoring.
ITM_TEDW, to indicate Tivoli Enterprise Data Warehouse Support.

destination_target

Is the gateway or server from which you want to remove the product. If you specify a server, the product is uninstalled from all its gateways.

For example

wuninst TMNT_3.6.2 nti246 -rmfiles -rmeps

For more information about command line syntax and usage of the wuninst command, refer to the Tivoli Management Framework Reference Manual and the Tivoli Management Framework Release Notes: Server, Gateway, and Endpoint.

Reference

wuninst

Uninstalls Tivoli applications from a specified node or from the entire Tivoli Management Region (TMR).

SYNOPSIS

wuninst

wuninst tag

wuninst -list

wuninst tag -list

wuninst tag node_name [-rmfiles] [options]

DESCRIPTION

The wuninst command is a wrapper script that invokes product-specific uninstall scripts. This section provides general usage information about the wuninst command. The usage statement for this command differs for each product.

To view the general usage statement, enter the following on the command line:

wuninst

To view the usage statement for an individual application, enter the following on the command line:

wuninst tag

The tag option is the registered product tag. To view a list of the product tags, enter the following on the command line:

wuninst -list

If you include the node_name option, the application specified with tag is removed from the specified node. If node_name is the TMR server, the application is removed from the entire TMR. You will be prompted with a confirmation message before the application is removed from the TMR.

The wuninst command cannot remove Tivoli Management Framework from a node. Use the command to remove Tivoli Management Framework and, therefore, remove the node from a TMR. You should use the wuninst command to remove all application files before running the wunstmn command.

Authorization

super

Arguments

tag: Specifies the product to remove.
node_name: Specifies the node to remove the product from. If node_name is the TMR server, the product is removed from the entire TMR.
-rmfiles: Indicates that all product files are to be removed from node_name. If this option is not included, the wuninst command removes only the database entries for node_name. If -rmfiles is used on the TMR server, all entries for each node in the TMR is removed.
-list: Lists the installed application tags or the node on which a product is installed. If used with the tag option, -list lists the nodes on which the specified product is installed. Without other arguments, -list shows the tags of all installed products.
options: Indicates options that might be required by each product. To view the options required to uninstall a particular product, enter wuninst tag on the command line.

EXAMPLES

The following example returns the general usage statement of the wuninst wrapper script.
```
wuninst
```
The following example returns the usage statement to remove Tivoli Software Distribution:
```
wuninst courier_3.7
```
The following example lists the tags of all products installed in the TMR:
```
wuninst -list
```
The following example lists the nodes on which Tivoli Software Installation Service is installed:
```
wuninst SIS_3.7 -list
```
The following example removes Tivoli Software Installation Service from node kiwi.
```
wuninst SIS_3.7 kiwi
```
The following example removes Tivoli Software Installation Service from node pctmp83. Because pctmp83 is the TMR server, Tivoli Software Installation Service is removed from every node in the TMR. The -rmfiles option indicates that all product files are removed as well as database entries.
```
wuninst SIS_3.7 pctmp83 -rmfiles
```

SEE ALSO

wunstmn

Old News

use this method to trace the uninstall.

On the ManagedNode:

> Source Tivoli Environment

> objcall 0.0.0 BEGIN

> Run the uninstall again

> objcall 0.0.0 END

> odstat > 26546_trace.txt

> wtrace -jHk %DBDIR% >> 26546_trace.txt