|
Softpanorama
(slightly skeptical)
Open Source Software Educational Society |
May the
source be with you,
but remember the KISS principle ;-)
|
Removing endpoints
At some point during the life cycle of a Tivoli environment, there will be a
need for you to remove an endpoint For example, you might install endpoints on machines
in a prototype environment before you roll out Tivoli Management Framework to the
enterprise.
See the section about deleting and uninstalling endpoints in
Tivoli Enterprise Installation Guide
Removing endpoint consists of two separate operations:
- Deleting
an endpoint removes the endpoint information from the Tivoli object database.
this operation is performed on TMR server.
- Uninstalling an
endpoint removes the Tivoli Management Framework files from the endpoint.
This operation is performed ont he endpoint.
The wdelep command removes the specified endpoints from the
Tivoli object database. The wdelep command with the
-d option stops the endpoint service and removes the specified
endpoints from the Tivoli object database.
The endpoints that the wdelep command is run against
no longer appear on the desktop and no longer appear in reports. However, the endpoint
software remains on these machines for future use.
To delete the endpoint software from the machine, you must uninstall it. Procedures
for uninstalling endpoints are provided in the following section.
For additional information about the wdelep command,
refer to the Tivoli Management Framework Reference Manual.
Note: this section was modified from
Uninstalling endpoints
Uninstalling an endpoint erases the endpoint software on the machine where it
was installed. However, uninstalling the software from the machine does not delete
its associated information from the Tivoli object database. To delete the endpoint
from the object database, refer to
Deleting endpoints from the Tivoli object database.
The general procedure for uninstalling any endpoint involves the following
(step for RHEL 4):
- Stopping the endpoint service, for example:
. /etc/Tivoli/lcf/1/lcf_env.sh
/opt/tivoli/lcf/dat/1/lcfd.sh stop
- Erasing the endpoint directories and files on the client computer, for
example:
rm -R /etc/Tivoli
rm -R /opt/Tivoli
- Removing startup statements from system configuration files on the client
computer, for example:
rm /etc/init.d/Tivoli_lcfd1
find /etc -name S99Tivoli_lcf1 -exec rm {} \;
find /etc -name K99Tivoli_lcf1 -exec rm {} \;
Different platform types require different specific steps for uninstalling endpoints.
The next sections describe how to uninstall UNIX and PC endpoints.
Uninstalling endpoints from UNIX platforms
The general procedure for removing endpoints is the same on all UNIX platforms,
but the specific configuration files and directories vary. The next sections provide
removal steps specific to different UNIX platforms.
Note: The directories specified in the following procedures assume the default locations.
Uninstalling endpoints from AIX systems
To uninstall an endpoint on an AIX machine, perform the following steps:
- Stop the endpoint daemon using one of the following methods:
- Enter the /opt/Tivoli/lcf/dat/1/lcfd.sh stop
command.
- Find the process identification (PID) of the daemon and enter the
kill command against it.
- Remove the endpoint installation directory and subdirectories. The default
location is /opt/Tivoli/lcf.
- Remove the endpoint environment directory, subdirectory, and files. The
directory is /etc/Tivoli/lcf. The environment files are lcf_env.sh and lcf_env.csh.
- Remove the endpoint startup entry in /etc/inittab using the following command:
/etc/rmitab rctma1
- Remove the /etc/rc.tma1 and /etc/inittab.before.tma1 files.
- Remove the /etc/Tivoli/*/userlink.htm file.
Uninstalling endpoints from HP-UX systems
To uninstall an endpoint on an HP-UX machine, perform the following steps:
- Stop the endpoint daemon using one of the following methods:
- Enter the /opt/Tivoli/lcf/dat/1/lcfd.sh stop
command.
- Find the process identification (PID) of the daemon and enter the
kill command against it.
- Remove the endpoint installation directory and subdirectories. The default
location is /opt/Tivoli/lcf.
- Remove the endpoint environment directory, subdirectory, and files. The
directory is /etc/Tivoli/lcf. The environment files are lcf_env.sh and lcf_env.csh.
- Remove the /sbin/init.d/lcfd1.sh file, which is the endpoint startup script.
- Remove the following symbolic links:
/sbin/rc0.d/K100Tivoli_lcf1
/sbin/rc1.d/K100Tivoli_lcf1
/sbin/rc2.d/K100Tivoli_lcf1
/sbin/rc3.d/S500Tivoli_lcf1
- Remove the /etc/Tivoli/*/userlink.htm file.
Uninstalling Endpoints on Solaris systems
To uninstall an endpoint on a Solaris machine, perform the following steps:
- Stop the endpoint daemon using one of the following methods:
- Enter the /opt/Tivoli/lcf/dat/1/lcfd.sh stop
command.
- Find the process identification (PID) of the daemon and enter the
kill command against it.
- Remove the endpoint installation directory and subdirectories. The default
location is /opt/Tivoli/lcf.
- Remove the endpoint environment directory, subdirectory, and files. The
directory is /etc/Tivoli/lcf. The environment files are
lcf_env.sh and lcf_env.csh.
- Remove the /etc/init.d/lcfd1.rc file, which is the endpoint startup script.
- Remove the following symbolic links:
/etc/rc0.d/K50Tivoli_lcf1
/etc/rc1.d/K50Tivoli_lcf1
/etc/rc2.d/K50Tivoli_lcf1
/etc/rc3.d/S99Tivoli_lcf1
- Remove the /etc/Tivoli/*/userlink.htm file.
Uninstalling endpoints from Linux platforms
The general procedure for removing endpoints is the same as removing endpoints
from UNIX platforms. The specific configuration files and directories vary. The
next sections provides removal steps specific to the different Linux platforms.
The procedures describe how to use the command line to remove the endpoint.
Note
The directories specified in the following procedures assume you installed the
endpoint in the default location.
Uninstalling endpoints from Linux for Intel systems
To uninstall an endpoint from a Linux for Intel system, perform the following
steps:
- Stop the endpoint service using the lcfd.sh stop
command.
- Remove the installation directory:
rm -r /opt/Tivoli/lcf/1
- Remove the endpoint environment directory:
rm -r /etc/Tivoli/lcf/1
- Remove the /etc/Tivoli/*/userlink.htm file.
- Remove the following autostart files and symbolic links from the system,
if they exist:
/etc/rc.d/init.d/lcfd1.rc
/etc/rc.d/init.d/lcfd1.sh
/etc/rc.d/init.d/Tivoli_lcfd1
/etc/rc.d/rc0.d/K10Tivoli_lcf1
/etc/rc.d/rc1.d/K10Tivoli_lcf1
/etc/rc.d/rc2.d/S99Tivoli_lcf1
/etc/rc.d/rc3.d/S99Tivoli_lcf1
/etc/rc.d/rc4.d/S99Tivoli_lcf1
/etc/rc.d/rc5.d/S99Tivoli_lcf1
/etc/rc.d/rc6.d/S99Tivoli_lcf1
Uninstalling endpoints from SuSE systems (Intel and zOS)
To uninstall an endpoint from Intel and zOS SuSE system, perform the following
steps:
- Stop the endpoint service using the
lcfd.sh stop
command.
- Remove the installation directory:
rm -r /opt/Tivoli/lcf/1
- Remove the endpoint environment directory:
rm -r /etc/Tivoli/lcf/1
- Remove the /etc/Tivoli/*/userlink.htm file.
- Remove the following autostart files and symbolic links from the system,
if they exist:
/etc/rc.d/init.d/Tivoli_lcfd1
/etc/rc.d/rc2.d/K10Tivoli_lcf1
/etc/rc.d/rc2.d/S99Tivoli_lcf1
/etc/rc.d/rc3.d/K10Tivoli_lcf1
/etc/rc.d/rc3.d/S99Tivoli_lcf1
/etc/rc.d/rc4.d/K10Tivoli_lcf1
/etc/rc.d/rc4.d/S99Tivoli_lcf1
/etc/rc.d/rc5.d/K10Tivoli_lcf1
/etc/rc.d/rc.5.d/S99Tivoli_lcf1
Copyright © 1996-2008 by Dr. Nikolai Bezroukov.
www.softpanorama.org was
created as a service to the UN Sustainable Development Networking Programme (SDNP)
in the author free time.
Submit
comments This document is an industrial compilation designed and created
exclusively for educational use and is placed under the copyright of the
Open Content License(OPL).
Original materials copyright belong to respective owners. Quotes are made
for educational purposes only in compliance with the fair use doctrine.
Standard disclaimer: The statements, views and opinions presented on
this web page are those of the author and are not endorsed by, nor do they necessarily
reflect, the opinions of the author present and former employers, SDNP or any other
organization the author may be associated with. We do not warrant the correctness
of the information provided or its fitness for any purpose.
Last modified:
March 15, 2008