Description:
Description:
============
Deploy a BE application and then start it from the TIBCO Administrator. The status of the application will never change to "Running" but the application will be running and also processing messages if checked from the machine (at the OS level).


Symptoms:
========
Start the application from the backend and check if it has started completely and can process the requests. If no requests are not processed it is an application's start up issue.

Enable the detailed tracing for Hawk and check the tsm.log file. You should see that the status of the application will be reported as "Initializing", which is equivalent to "Starting Up" on the TIBCO Administrator. After enabling tracing also check the Hawk.log file. You should see that the application's microagent is not getting registered with the domain's hawkagent. The following entry will be absent in the hawk.log file where every running application should register their microagent.

"Adding MicroAgent: COM.TIBCO.ADAPTER.be-engine.<domain-name>.<application-name>.<service-instance-name>"


Cause:
=====
The following variables may not have been set correctly in the application's tra file.
*************************************************************************************
tibco.env.BW_HOME, tibco.env.BW_MIGRATION_APPEND_VERSION, tibco.env.BW_PLUGINS_HOME_OLD, tibco.env.BW_PLUGINS_HOME, tibco.env.TPCL_HOME, tibco.env.TRA_HOME, tibco.env.TRA_APPEND_VERSION, tibco.env.HAWK_HOME, tibco.env.RV_HOME,
*************************************************************************************

The above values in case of BE are not set by default. It is only needed if you want to monitor and deploy the BE application using TIBCO Administrator. For future deployments these values have to be correctly set in the base be-engine.tra file on that machine. The tibco.env.HAWK_HOME, tibco.env.RV_HOME and tibco.env.TRA_HOME are required for the applications running status to be correctly shown on the TIBCO Administrator page.

Also check if the below variables are set in the application's tra file.
Hawk.AMI.DisplayName=COM.TIBCO.ADAPTER.be-engine.<domain-name>.<application-name>.<service-instance-name>
Hawk.Daemon=<domain hawkagent's ami rvd daemon>
Hawk.Service=<domain hawkagent's ami rvd service>
Hawk.Network=<domain hawkagent's ami rvd network>
Hawk.Enabled=true

Resolution:
==========
Set the values of the following variables correctly in the deployed application's tra file and start the application.
*************************************************************************************
tibco.env.BW_HOME, tibco.env.BW_MIGRATION_APPEND_VERSION, tibco.env.BW_PLUGINS_HOME_OLD, tibco.env.BW_PLUGINS_HOME, tibco.env.TPCL_HOME, tibco.env.TRA_HOME, tibco.env.TRA_APPEND_VERSION, tibco.env.HAWK_HOME, tibco.env.RV_HOME,
*************************************************************************************
Hawk.AMI.DisplayName=COM.TIBCO.ADAPTER.be-engine.<domain-name>.<application-name>.<service-instance-name>
Hawk.Daemon=<domain hawkagent's ami rvd daemon>
Hawk.Service=<domain hawkagent's ami rvd service>
Hawk.Network=<domain hawkagent's ami rvd network>
Hawk.Enabled=true

For future deployments set the following set of values correctly in the base be-engine.tra file on that machine.
*************************************************************************************
tibco.env.BW_HOME, tibco.env.BW_MIGRATION_APPEND_VERSION, tibco.env.BW_PLUGINS_HOME_OLD, tibco.env.BW_PLUGINS_HOME, tibco.env.TPCL_HOME, tibco.env.TRA_HOME, tibco.env.TRA_APPEND_VERSION, tibco.env.HAWK_HOME, tibco.env.RV_HOME,
*************************************************************************************

A deployed BE application shows the application's status as "Starting Up" on the TIBCO Administrator and never goes to "running" even though the application has started up correctly at the back end and is also processing messages.