Resolution:
Problem Description:
=================
We upgraded our environment to BE 5.1.1 HF7 from BE 5.1.1 HF5. After applying the hotfix 07 to TIBCO BusinessEvents 5.1.1, we do not see the latest be-engine version(5.1.1.121) in the drop down in TIBCO Administrator Gui. Instead, it shows be-engine 5.1.1.103.

Envrionment:
==================
TIBCO BusinessEvents 5.1.1, with any hotfixes
TIBCO Administrator

Symptoms:
=========
After you install BE 5.1.1 and apply a hotfix (or multiple fixes) to it, sometimes the be-engine version shown in the drop down list of Administrator is not the latest one.

Cause:
======
1). Every BE installation carries deploymentInfo. For example, if you have the following installation in your TIBCO_HOME: BE 5.1.1(35) --> BE 5.1.1 Hotfix 03(72) --> BE 5.1.1 Hotfix 05(103) --> BE hotfix 07(121), you will have the following XML files that carry deploymentInfo under _installInfo folder:

businessevents-stand_5.1.1_prodInfo.xml
businessevents-hf_5.1.1.003_prodInfo.xml
businessevents-hf_5.1.1.005_prodInfo.xml
businessevents-hf_5.1.1.007_prodInfo.xml

2). Hawk will detect all installed products as per the deploymentInfo. Enable debug on Hawk agent. You should be able to see the product lists in tsm.log:
>>>>>>>>>>>>>>>>>>>
&ltproduct displayname="TIBCO BusinessEvents" version="5.1" maintenanceversion="1" updateversion="72" type="be" location="C:/TIBCO_HOME/TRA58_HOME_64/be/5.1">
    &ltfeature name="serverfiles">
        &ltcomponent componentdisplayname="BE Engine" componentname="be-engine" deployactionspluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeployActions" deploypluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeploy" isdeployable="true" isjava="true" name="serverfiles" paletteresource="tibco.be.archive" pluginfilename="be-admin.jar" processname="be-engine" relativeprocesslocation="bin" undeployactionspluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeployActions" undeploypluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeploy"/>
    </feature>
</product>
&ltproduct displayname="TIBCO BusinessEvents" version="5.1" maintenanceversion="1" updateversion="103" type="be" location="C:/TIBCO_HOME/TRA58_HOME_64/be/5.1">
    &ltfeature name="serverfiles">
        &ltcomponent componentdisplayname="BE Engine" componentname="be-engine" deployactionspluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeployActions" deploypluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeploy" isdeployable="true" isjava="true" name="serverfiles" paletteresource="tibco.be.archive" pluginfilename="be-admin.jar" processname="be-engine" relativeprocesslocation="bin" undeployactionspluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeployActions" undeploypluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeploy"/>
    </feature>
</product>
&ltproduct displayname="TIBCO BusinessEvents" version="5.1" maintenanceversion="1" updateversion="121" type="be" location="C:/TIBCO_HOME/TRA58_HOME_64/be/5.1">
    &ltfeature name="serverfiles">
        &ltcomponent componentdisplayname="BE Engine" componentname="be-engine" deployactionspluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeployActions" deploypluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeploy" isdeployable="true" isjava="true" name="serverfiles" paletteresource="tibco.be.archive" pluginfilename="be-admin.jar" processname="be-engine" relativeprocesslocation="bin" undeployactionspluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeployActions" undeploypluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeploy"/>
    </feature>
</product>
&ltproduct displayname="TIBCO BusinessEvents" version="5.1" maintenanceversion="1" updateversion="35" type="be" location="C:/TIBCO_HOME/TRA58_HOME_64/be/5.1">
    &ltfeature name="serverfiles">
        &ltcomponent componentdisplayname="BE Engine" componentname="be-engine" deployactionspluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeployActions" deploypluginclassname="com.tibco.be.deployment.tsm.TSMBEEngineDeploy" isdeployable="true" isjava="true" name="serverfiles" paletteresource="tibco.be.archive" pluginfilename="be-admin.jar" processname="be-engine" relativeprocesslocation="bin" undeployactionspluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeployActions" undeploypluginclassname="com.tibco.tra.tsm.plugin.TSMComponentUndeploy"/>
    </feature>
<<<<<<<<<<<<<<<<<<<
The products are read randomly, there is no specific secquence between the products.

3). Administrator then display the products. If there are multiple entries for the same product (products with the same displayname, version and maintenanceversion), it only display the first entry returned in the list.

As the products returned by Hawk(installation jar) is random,  in some cases the first entry may not be that latest hotfix. As in the above example, although you have hotfix 7 installed successfully, in the drop down list you are seeing be-engine 5.1.1.072.

Resolution:
===========
This is an Administrator display rather than a BE issue. There should be no impact on runtime behaviors. Verify the runtime version of BE engine to confirm the runtime version is correct.

If customer does not like the display on the version, you may use the following manual option to disable displayInfo on any older version:

- Do a backup of any businessevents-*_prodInfo.xml which has deploymentInfo element. In general the files are:

  businessevents-standard_5.1.1_prodInfo.xml
  businessevents-hf_5.1.1.00n_prodInfo.xml

- Except in the XML for the latest hotfix, comment out the full deploymentInfo node from other XML files.

- Do a restart of the Hawk agent. Verify from tsm.log to see if only the latest entry is returned for BE 5.1.1

- Check the Administrator GUI from the drop down list.

After applying hotfix 07 to TIBCO BusinessEvents 5.1.1, the latest be-engine version (5.1.1.121) in the drop down list in TIBCO Administrator GUI is not seen.