Uninstallation of BE 5.1.0 in console mode removes all jar files from the Hawk lib directory, all tra files from the Hawk bin directory and soft links from the EMS lib/64 directory.

Uninstallation of BE 5.1.0 in console mode removes all jar files from the Hawk lib directory, all tra files from the Hawk bin directory and soft links from the EMS lib/64 directory.

book

Article ID: KB0090985

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
=========
Uninstallation of BE 5.1.0 in console mode removes all jar files from the Hawk lib directory, all tra files from the Hawk bin directory and soft links from the EMS lib/64 directory.

Environment:
==========
TIBCO BusinessEvents (BE) 5.1.0
All Operating Systems.


Symptoms:
========
- Message of cleaning up of hawk/ems related files can be seen in console during BE 5.1.0 uninstallation in console mode.

- all jar files from the Hawk lib directory, all tra files from the Hawk bin directory and soft links from the EMS lib/64 directory will be removed.

Cause:
=====
The issue was the installation command used to install BE 5.1.0. The installer was launched as follows:
+++++
./TIBCOUniversalInstaller-aix.bin -silent -V responseFile="TIBCOUniversalInstaller_businessevents-standard_5.1.0.silent"
++++++

This does completely install the BE product stack as listed below, but the issue is that for the add on products ( views/datamodeling/decisionmanager ) is that the information needed for uninstallation is not recorded completely. Because of this it does cause the installer to trip up and run pre-uninstall tasks (the missing symlinks in EMS and files missing from Hawk at that point, it doesn't actually uninstall those products).

Resolution:
========
Instead of passing a responseFile,  use -silent.  Do not specify a response file. E.g.
+++++
./TIBCOUniversalInstaller-aix.bin -silent
+++++
This will cause the installer to take into account all the .silent files ( the ones for
each product) in the directory and will allow the installer to correctly record all information.  

If there are installations on systems that was performed with a response file,
just re-run the installation of the suite with the -silent option only.  This will re-install
the product and have the information recorded completely. and uninstall of the BE 5.1
stack will run successfully without disrupting other products.

References:
=========
None

Issue/Introduction

Uninstallation of BE 5.1.0 in console mode removes all jar files from the Hawk lib directory, all tra files from the Hawk bin directory and soft links from the EMS lib/64 directory.