Copyright © Cloud Software Group, Inc. All Rights Reserved

Configuring HMA

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 8 HMA Configuration Properties

Logical Group	Parameters
TIBCO HMA Common	-hawk_domain <TIBCO Hawk domain name>
	-agent_name <agent name>
	-agent_domain <agent domain name>
TIBCO DataGrid Session	-as_session <listenurl> <discoverurl>
	-as_transport_timeout <timeout in milliseconds>
	-as_receive_buffer_size <size in bytes>
	-as_worker_thread_count <numeric count>
	-as_virtual_node_count <numeric count>
TIBCO Rendezvous (RVD) Session	-rvd_session <service> <network> <daemon>
Logging Information	-logdir <directory to store HMA logs>
	-logmaxsize <maximum size of one HMA log>
	-logmaxnum <maximum number of HMA logs>
	-log_format <Hawk or ActiveEnterprise format>
Timeout	-timeout <milliseconds>
Trace Level	-tracelevel <desired trace level>
UNIX Signal Handling	-ignore_sigint
	-ignore_sigterm
	-ignore_sigabrt
Encoding	-codepage

Each of the parameters listed above are explained in more detail, in the following table.

Table 9 HMA Configuration Parameter Details

Property	Mandatory	Default Value	Description
TIBCO HMA Common
-hawk_domain	Yes	“default”	See page 35 for details.
-agent_name	Yes	Host Name of the computer	When Hawk is configured with TIBCO DataGrid as the transport mechanism, on non-Windows platforms, and agent_name is not specified, then the host name is used as the default agent_name implicitly. 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.
-agent_domain	Yes	“none”	An agent domain must be specified when two computers within the same TIBCO Hawk domain have the same name but reside in different network domains. For example, you might specify this option as: -agent_domain pa.tibco.com.
TIBCO DataGrid Transport Note: Same configuration will be used for AMI communication
-as_session	No	"" tibpgm://8989/	Comment this option if you are using TIBCO Rendezvous as the primary transport. The format is -as_session <listen url> <discover url>. See TIBCO DataGrid Transport for more details. Use a semicolon (;) to indicate a null value, or use an empty string, for example: -as_session "" tibpgm://8989/
-as_transport_timeout	No	30000	Timeout (in milliseconds) used by transport for internal invocations
-as_receive_buffer_size	No	1000	Internal buffer size in bytes
-as_virtual_node_count	No	100	Virtual node count
-as_worker_thread_count	No	32	Worker threads
TIBCO Rendezvous Transport
-rvd_session	No	7474 "" tcp:7474	TIBCO Rendezvous is the default primary transport for TIBCO Hawk 5.2.0. Comment this option if you are using TIBCO DataGrid as the primary transport. The format is -rvd_session <service> <network> <daemon>. If you use this option, all three parameters must be present and separated by white space. Use a semicolon (;) to indicate a null value, or use an empty string, for example: -rvd_session 7474 "" tcp:7474
Logging
-logdir	No	CONFIG_FOLDER/logs	The directory in which to store log files generated by the TIBCO Hawk HMA.
-logmaxsize	No	1024	The maximum size of a rotating log files in Kbytes.
-logmaxnum	No	5	The maximum number of rotating log files
-log_format	No	“default”	The format for trace log messages
Timeout
-timeout	No	10000	The method invocation timeout period to be used by all AMI methods. Timeout value is in milliseconds.
Trace Level
-tracelevel	No	7	Specifies the level of diagnostic trace output. The desired trace level is specified by adding the following values together: 1 - Indicates information level trace messages should be enabled. 2 - Indicates warning level trace messages should be enabled. 4 - Indicates error level trace messages should be enabled. 8 - Indicates debug level trace messages should be enabled. 16 - Indicates AMI level trace messages should be enabled. 32 - Adds source file name and line number to all messages. A value of zero turns all tracing off A value of -1 turns all tracing on.
Unix Signal Handling
-ignore_sigint	No	-	Ignore SIGINT signal
-ignore_sigterm	No	-	Ignore SIGTERM signal
-ignore_sigabrt	No	-	Ignore SIGABRT signal
Encoding
-codepage	No	65001 (UTF-8)	The desired code-page for multi-byte/Unicode character sets

Logging for HMA

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.

Following are some representative lines in an HMA log file for the Services MicroAgent:

INFO 01/15/2013 11:14:39

OPTIONS: Transport: AS

Discovery URL : tcp://10.97.123.88:40000

Listen URL : tcp://10.97.123.88:40000

Invocation Timeout : 30000

Virtual Node Count : 100

Worker Thread Count : 32

Received Buffer Size : 1000

CodePage : 65001

TraceLevel : -1

Logdir : C:/ProgramData/hawkv16/tibco/cfgmgmt/hawk/log --

LogMaxSize : 1024 -- Max Log Files : 5 -- Log Format : default

INFO 01/15/2013 11:14:53 TIBCO Hawk HMA initialization completed successfully.

Copyright © Cloud Software Group, Inc. All Rights Reserved