Why do Java processes (hawk agent, bwagent, appnode etc) get killed when installing TIBCO Runtime Agent?

Why do Java processes (hawk agent, bwagent, appnode etc) get killed when installing TIBCO Runtime Agent?

book

Article ID: KB0074527

calendar_today

Updated On:

Products Versions
TIBCO Runtime Agent (TRA) 5.10.1

Description

When installing TIBCO Runtime Agent (TRA) in an existing TIBCO_HOME where there are Java processes like adapters, bwengine, hawkagent etc running, we may have to stop those running processes first. This is true especially if TRA is going to install JRE in the same folder. 

For instances, there is TIBCO_HOME folder where BW 6.4 processes are running. Now users want to install TRA 5.10.1 in the same TIBCO_HOME folder. The installer of TRA 5.10.1 will upgrade the JRE if the existing JRE update is older than the one bundled in TRA 5.10.1. 
In this scenario, if it is a Windows machine, users have to stop the running Java processes like bwagent, AppNode etc first. Otherwise, TRA installation may run into problems as the JRE files are locked by running processes and can't be updated by TRA installer.  If it is a Linux/Unix machine, the TRA installer will kill all running Java processes to clear the environment for JRE upgrading. 

Issue/Introduction

Why do Java processes (hawk agent, bwagent, appnode etc) get killed when installing TIBCO Runtime Agent?

Environment

OS: All

Resolution

Stop running TIBCO processes before installing new TRA, and restart those processes after the installation.