Products | Versions |
---|---|
TIBCO Hawk | - |
Not Applicable | - |
Description:
A Hawk display is able to connect to only one Hawk domain on any machine. It does not support multiple domains. If monitoring multiple Hawk domains is required, use the Hawk webconsole which is bundled with Hawk version 5.0 and above. For more details about the Hawk webconsole, refer to the Hawk documentation.
Follow the steps below to configure the Hawk display.
a). If standalone Hawk agents have been used, hawkagent.cfg should be located in the <cfgmgmt>/hawk/bin folder. If TRA hawkagents have been used, the hawkagent.cfg should be located under <tra>/domain/<domain>/.
a). Find out the version of Hawk. If Hawk 5.x has been used on all platforms or hawk 4.9.x has been used on the Linux platform, make the modification in <cfgmgmt>/hawk/bin/hawkdisplay.cfg. If Hawk 4.9.x has been used on a Windows machine, make the modification in the Hawk Configuration Utiltiy tool.
b). Change the Hawk domain name (case sensitive) in hawkdisplay.cfg or "Hawk Configuration Utiltiy" according to your hawkagent configuration.
c). Change the transport in hawkdisplay.cfg or "Hawk Configuration Utiltiy" according to your hawkagent configuration.
a). In the Hawk display, click "Help" menu->Click "Runtime Information..." .
b). In the new window, confirm the Hawk domain name and transport is correct. If the Hawk domain name and transport are not the same as configured before, contact TIBCO Hawk Support for further investigation.
Notes:
If RV is the primary transport, the hawkagent machine and Hawk display machine are supposed to be in the same subnet. If they are not in the same subnet, apply the remote daemon as follows to make Hawk the display work.
a). Go to the Windows services panel by running "services.msc".
b). Find the service "TIBCO Hawk HMA" and stop it.
c). Set the startup type to manual or disable by right clicking the "TIBCO Hawk HMA" service and select properties.
2). When configuring the Hawk display with the RV transport, apply the remote daemon by adding the IP address of the hawkagent in daemon parameter before the TCP port.