Copyright © Cloud Software Group, Inc. All Rights Reserved

Configuring Hawk Display

All the required configuration parameters are stored in CONFIG_FOLDER/bin/hawkdisplay.cfg. The following table describes various Hawk Display related configuration properties in easy-to-understand logical groups. The various groups are as follows:

Table 13 Hawk Display Configuration Properties

Logical Group	Parameters
TIBCO DataGrid Session	-as_session <listenurl> <discoverurl>
	-agent_name <agent name>
	-agent_domain <agent domain name>
	-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>
TIBCO Hawk Domain	-hawk_domain <TIBCO Hawk domain name>
Logging Information	-logdir <directory to store Hawk Display logs>
	-logmaxsize <maximum size of one Hawk Display log>
	-logmaxnum <maximum number of Hawk Display logs>
	-log_level <desired trace level for logs>
	-log_format <Hawk or ActiveEnterprise format>

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

Table 14 Hawk Display Configuration Parameter Details

Property	Mandatory	Default Value	Description
-hawk_domain	Yes	“default”	See page 35 for details.
TIBCO DataGrid Transport Note: You can use the same configuration 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 or TIBCO EMS 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
TIBCO EMS Transport See page 30 for details
-ems_transport	No		Comment this option if you are using TIBCO DataGrid or TIBCO Rendezvous as the primary transport. Specifies the location of the EMS server. For example, -ems_transport tcp://server1:7222. Note: If EMS is configured as Transport, the ami_rvd_session parameter should be configured.
TIBCO EMS SSL Parameters (In case EMS Server is configured for SSL communication). Refer to page 32 for details.
-ssl_vendor	No		The name of the vendor of the SSL implementation. The valid choices are • j2se-default—Use this option when you want to use the default JCE bundled with the Java JRE. On IBM platforms (such as AIX), this option defaults to ibm. • entrust61—Use this option when you want to use the Entrust libraries. • ibm—On non-IBM platforms, this option can be used only if the IBM version of JCE is installed.
-ssl_ciphers	No		Cipher suite name
-ssl_no_verify_host	No		Indicate not to verify the EMS server
-ssl_trusted	No		File name of the server certificates. The file should be accessible locally/ shared drive
-ssl_no_verify_hostname	No		Indicates not to verify the name in CN field of the server certificate
-ssl_expected_hostname	No		If the -ssl_no_verify_host is not specified, the option -ssl_trusted has to be used. Along with the option-ssl_trusted specify either -ssl_no_verify_hostname or -ssl_expected_hostname.
-ssl_identity	No		Digital certificate
-ssl_private_key	No		Private key
-character_encoding	No		Character encoding to be used across the configured transport
Configuration for AMI communication AMI communication configuration options is used only in case of the Rendezvous or EMS transport. For TIBCO DataGrid, this will be ignored.
-ami_rvd_session	No	7474 127.0.0.1 tcp:7474	Configures the agent with a RVD session to be used to communicate with applications implementing the TIBCO Hawk Application Management Interface. Multiple -ami_rvd_session parameters may be specified. If none are specified, the RV session used for AMI is the primary session of the Self Module. # Note: When using TIBCO EMS transport for communication, 127.0.0.1 should be used as the network parameter. For example: ami_rvd_session 7474 127.0.0.1 tcp:7474
Logging
-logdir	No		The directory in which to store log files generated by the TIBCO Hawk Display.
-logmaxsize	No		The maximum size of a rotating log files in Kbytes.
-logmaxnum	No		The maximum number of rotating log files
-log_level	No	7	Specifies the level of diagnostic information stored in the logs. The following are the logging levels: 4 - Indicates error level trace messages should be enabled 6- Indicates warning level trace messages should be enabled 7 - Indicates information level trace messages should be enabled 8 - Indicates debug level trace messages should be enabled 16 - Indicates AMI level trace messages should be enabled A value of zero turns all tracing off. A value of -1 turns all tracing on.
-log_format	No		The format for trace log messages
-display_file	No		Specify the location of the display file (.hdp) to be loaded by Hawk Display. This file contains the saved UI state of the Network Topology.
-security_policy	No		The fully qualified name of the Java class which implements security policy. For more information refer to Chapter 4, TIBCO Hawk Security Model.
-variables	No		Properties file to specify variables file. The variables file can pass data to define external variables to be passed to rules for use in Rulebase configurations.

 

 

Copyright © Cloud Software Group, Inc. All Rights Reserved