Hawk Cluster Manager Configurations

You can optionally install and configure the Admin Agent as a console to monitor the Hawk agents. If you plan to use TCP transport for Admin Agent to Hawk Agent communication, then you must configure the Hawk Cluster Manager. All the required configuration parameters are stored in the CONFIG_FOLDER/hawktcpdaemon.cfg file.

Each of the parameters are explained in more detail in the following table:

Hawk Cluster Manager Configuration Details

Property

Description

TCP Transport for TIBCO Hawk

tcp_session

Setups the TCP session for the Hawk components. Hawk Cluster Manager joins the TCP Transport for TIBCO Hawk cluster as seed node using this property.

The syntax of the property is:

-tcp_session <self_IP>:<port> <cluster_manager_IP>:<port>

where,

<self_IP>:<port> - Unique socket address of the Hawk agent for connecting to the cluster.
<cluster_manager_IP>:<port> - The socket address of the Cluster Manager acting as the seed node for the cluster.

In case there is only one daemon in the cluster then both the socket addresses (self and daemon) are the same.

Note: Multiple agents/console/clustermanagers running on the same instance must be bound to separate ports.

For fault tolerance, you can specify multiple seed daemon’s socket addresses in a comma-separated list.

-tcp_session <self_IP>:<port> <daemon1_IP>:<port>, <daemon2_IP>:<port>

 

Mandatory: Yes

Suggested value: localhost:2561 localhost:2561

TCP Transport for TIBCO Hawk SSL Parameters

tcp_key_store

Path of the key store file

 

Mandatory: No

Suggested value: -

tcp_trust_store

Path of the trust store file

 

Mandatory: No

Suggested value: -

tcp_key_store_password

Password for the key store file

 

Mandatory: No

Suggested value: -

tcp_key_password

Encrypted key password

 

Mandatory: No

Suggested value: -

tcp_trust_store_password

Password for the trust store file

 

Mandatory: No

Suggested value: -

tcp_ssl_protocol

Protocol for a secure connection

 

Mandatory: No

Suggested value: TLSv1.2

tcp_enabled_algorithms

Algorithm to be used for the security protocol. You can specify multiple algorithms as a comma-separated list without space

 

Mandatory: No

Suggested value: TLS_RSA_WITH_AES_128_CBC_SHA

strategy

Specifies the strategy for resolving network partitions of the cluster members from the TCP Transport for TIBCO Hawk cluster. The two strategies that you can choose are:

Quorum - This strategy defines the minimum number of daemons required for a cluster to be operational (quorum size). In case of network partition, the partition with the required quorum size remains operational while the other partition is shut down.
Majority - If the network partition occurs then the partition that has the majority of nodes remains operational while the other partition is shut down.

 

Mandatory: No

Suggested value: Quorum

hawk_domain

Specifies the Hawk domain name. The Hawk agents, Hawk cluster managers, and the console applications must have the same hawk domain value in order to communicate.

 

Mandatory: No

Suggested value: default

Logging

log_dir

The directory to store log files generated by the TIBCO Hawk Cluster Manager

 

Mandatory: No

Suggested value: CONFIG_FOLDER/logs

log_max_size

The maximum size of a rotating log files in kilobytes. You can apply the suffix ’m’ or ’M’ for indicating MB values

 

Mandatory: No

Suggested value: 10M

log_max_num

The maximum number of rotating log files

 

Mandatory: No

Suggested value: 10

log_level

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.
0 - A value of zero turns OFF all tracing.
-1 - A value of -1 turns ON all tracing.

 

Mandatory: No

Suggested value: 7

log_format

The format for trace log messages

 

Mandatory: No

Suggested value: "default"

For more information about the Admin Agent and its configurations, see TIBCO® Operational Intelligence Hawk® RedTail Admin Agent.