![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
All the required configuration parameters are stored in CONFIG_FOLDER/bin/hawkhma.cfg. The following table describes various HMA configuration properties in easy-to-understand logical groups. The various groups are as follows:
Table 14 HMA Configuration Properties
Table 15 HMA Configuration Parameter Details See Hawk Domain for details. Name of the agent. Ensure that the output of the '/usr/bin/hostname' UNIX command matches with the 'hostname' specified in the /etc/hosts file.For example, if the value of hostname is linux64 then the /etc/hosts file should have the entry, such as, 192.168.1.100 linux64. However, if you are using TCP Transport for TIBCO Hawk then uncomment this option, so that Hawk Agent can communicate with Hawk Microagent using the TCP-RV bridge. The value of this parameter must be same as the value of the -ami_rvd_session parameter in the Hawk Agent configuration file (hawkagent.cfg). CONFIG_FOLDER/logs The TIBCO Hawk HMA process creates log files for each MicroAgent, such as Hawk_Process.log. The HMA process also creates a Hawk_HMA.log file for MicroAgent-generic errors.To see console logs on command console, add "-console" argument as one of the application arguments in the file tibhawkhma.tra. Otherwise, the logs get logged as Windows Events. If the logging is enabled, the logs appear in the related files.You control the size and level of detail in HMA log files at the start using the hawkhma.cfg file or during runtime using the setTraceLevel() and setTraceParameters() methods. These standard methods are included for default platform-specific MicroAgents, and can be added when instrumenting an application using the AMI protocol.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |