Hawk Cluster Manager Configurations

All the required configuration parameters are stored in CONFIG_FOLDER/hawk/bin/hawktcpdaemon.cfg. Each section in this configuration file begins with “-M” followed by the module name, such as –M Self. Within each modular section, all the command-line options that can be configured are listed. These options are as follows:

Hawk Cluster Manager Modules and Options

Module

Parameters

-M Self

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

 

-tcp_key_store <key store file path>

 

-tcp_trust_store <trust store file path>

 

-tcp_key_store_password <key store password>

 

-tcp_key_password <key password>

 

-tcp_trust_store_password <trust store password>

 

-tcp_ssl_protocol <security protocol>

 

-tcp_enabled_algorithms <security algorithms>

 

-strategy <Majority or Quorum>

 

-hawk_domain <domain_name>

-M LogService

-log_dir <directory to store TIBCO Hawk logs>

 

-log_max_size <maximum size of log file>

 

-log_max_num <maximum number of log files>

 

-log_level <desired trace level for logs>

 

-log_format <log format>

 

 

 

The following table provides more detailed information about each of the configuration parameters for the Cluster Manager.

Hawk Cluster Manager Configuration Options

Property

Mandatory

Default Value

Description

TCP Transport for TIBCO Hawk

-tcp_session

Yes

localhost:2561 localhost:2561

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 same.

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>

TCP Transport for TIBCO Hawk SSL Parameters

-tcp_key_store

No

-

Path of the key store file

-tcp_trust_store

No

-

Path of the trust store file

-tcp_key_store_password

No

-

Password for the key store file

-tcp_key_password

No

-

Encrypted key password

-tcp_trust_store_password

No

-

Password for the trust store file

-tcp_ssl_protocol

No

TLSv1.2

Protocol for a secure connection

-tcp_enabled_algorithms

No

TLS_RSA_WITH_AES_128_CBC_SHA

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

-strategy

No

Quorum

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 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 majority of nodes remains operational while the other partition is shut down.

For more information about the downing strategy of the TCP Transport for TIBCO Hawk, refer to the TIBCO Hawk Concepts guide.

-hawk_domain

No

default

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.

Logging

-log_dir

No

CONFIG_FOLDER/logs

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

-log_max_size

No

10M

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

-log_max_num

No

10

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

-log_format

No

“default”

The format for trace log messages.