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
file. CONFIG_FOLDER
/hawktcpdaemon.cfg
Each of the parameters are explained in more detail in the following table:
Property |
Description |
|||||||||||||||||||||
TCP Transport for TIBCO Hawk |
||||||||||||||||||||||
|
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
where,
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
Mandatory: Yes Suggested value: |
|||||||||||||||||||||
TCP Transport for TIBCO Hawk SSL Parameters |
||||||||||||||||||||||
|
Path of the key store file
Mandatory: No Suggested value: - |
|||||||||||||||||||||
|
Path of the trust store file
Mandatory: No Suggested value: - |
|||||||||||||||||||||
|
Password for the key store file
Mandatory: No Suggested value: - |
|||||||||||||||||||||
|
Encrypted key password
Mandatory: No Suggested value: - |
|||||||||||||||||||||
|
Password for the trust store file
Mandatory: No Suggested value: - |
|||||||||||||||||||||
|
Protocol for a secure connection
Mandatory: No Suggested value: TLSv1.2 |
|||||||||||||||||||||
|
Algorithm to be used for the security protocol. You can specify multiple algorithms as a comma-separated list without space
Mandatory: No Suggested value: |
|||||||||||||||||||||
|
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:
Mandatory: No Suggested value: Quorum |
|||||||||||||||||||||
|
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 |
||||||||||||||||||||||
|
The directory to store log files generated by the TIBCO Hawk Cluster Manager
Mandatory: No Suggested value: |
|||||||||||||||||||||
|
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 |
|||||||||||||||||||||
|
The maximum number of rotating log files
Mandatory: No Suggested value: 10 |
|||||||||||||||||||||
|
Specifies the level of diagnostic information stored in the logs. The following are the logging levels:
Mandatory: No Suggested value: 7 |
|||||||||||||||||||||
|
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.