The tibhawkhma process spawned by TRA 5.9 Hawk Agent is from ;HAWK_CONFIG;/bin instead of ;HAWK_HOME;/bin; . Also, the spawned HMA always uses the RV transport "7474 ; rvd:7474".

The tibhawkhma process spawned by TRA 5.9 Hawk Agent is from ;HAWK_CONFIG;/bin instead of ;HAWK_HOME;/bin; . Also, the spawned HMA always uses the RV transport "7474 ; rvd:7474".

book

Article ID: KB0085544

calendar_today

Updated On:

Products Versions
TIBCO Runtime Agent (TRA) -
Not Applicable -

Description

Description:
The tibhawkhma process spawned by TRA 5.9 Hawk Agent is from <HAWK_CONFIG>/bin instead of <HAWK_HOME>/bin; . For older versions or TRA 5.9 on Windows, it is from <HAWK_HOME>/bin; . The spawned HMA always uses the RV transport "7474 ; rvd:7474". This is a known issue:  TRA-3486.
Symptoms:
The behavior needs to be consistent between different versions and different platforms. In addition, in the TRA documentation, the post installation of setuid for tibhawkhma points to <HAWK_HOME>/bin; . If a user is not using the default RV transport "7474 ; rvd:7474", the Hawk Agent cannot connect to the HMA.
Cause:
This is due to TRA 5.9 using the <HAWK_HOME>/bin/starthma script to spawn HMA while the script points to tibhawkhma under <HAWK_CONFIG>/bin; . Also, TRA passes "--propFile <TIBCO_HOME>/tra/domain/<DOMAIN_NAME>/tibhawkhma.tra" to the starthma script while the starthma script cannot handle two parameters.

Resolution

Modify the following line in the <HAWK_HOME>/bin/starthma script:

HMA_EXECUTABLE=$HAWK_ROOT/bin/tibhawkhma

To:

HMA_EXECUTABLE=$HAWK_INSTALL/bin/tibhawkhma

After:

if [ $# -eq 1 ]
then
    cmdlinargs="--propFile $1"
fi

Add:

if [ $# -eq 2 ]
then
    cmdlinargs="--propFile $2"
fi

Issue/Introduction

The tibhawkhma process spawned by TRA 5.9 Hawk Agent is from ;HAWK_CONFIG;/bin instead of ;HAWK_HOME;/bin; . Also, the spawned HMA always uses the RV transport "7474 ; rvd:7474".
Powered by Wolken Software