Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 TIBCO Hawk Component Configurations : Hawk Event Service Configurations

Hawk Event Service Configurations
The Hawk Event Service records:
Refer to the TIBCO Hawk Concepts Guide for details about TIBCO Hawk Event Service.
All the required configuration parameters are stored in CONFIG_FOLDER/bin/hawkevent.cfg. The following table describes various Hawk Event Service related configuration properties in easy-to-understand logical groups. The various groups are as follows:
-rvd_session <service> <network> <daemon>
-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>
-hawk_domain <TIBCO Hawk domain name>
-logdir <directory to store Event Service logs>
-logmaxsize <maximum size of one Event Service log>
-logmaxnum <maximum number of Event Service logs>
-log_level <desired trace level for logs>
-log_format <Hawk or ActiveEnterprise format>
Fault Tolerance
To enable fault tolerance, uncomment the -ft parameter.
This instance joins a fault tolerant group named HawkEventService:hawkdomain, where hawkdomain is the domain of the agent.
Weight
Assign the weight of this instance using a positive integer. The member with the highest weight receives rank 1 (so it outranks all other members). When an instance fails, the next-highest instance is activated and the member with the next highest weight receives rank 2; and so on.
-ft <fault tolerance weight>
-ft_rvd_session <service> <network> <daemon>
Be careful not to confuse TIBCO Hawk Event Service data files (Event.dat) with Event Service log files (Event.log).
Event.dat data files contain the data produced by the Event Service.
Event.log log files record the state of the Event Service itself.
Each of the parameters listed above are explained in more detail, in the following table.
See Hawk Domain for details.
-rvd_session <service> <network> <daemon>.
-tcp_session <self_IP>:<port> <cluster_manager_IP>:<port>
<self_IP>:<port> - The unique socket address of the Hawk Event service for joining the cluster.
<cluster_manager_IP>:<port> - The socket address of the Hawk Cluster Manager acting as the seed node for the cluster. This socket address is same as <cluster_manager_IP>:<port> specified for the -tcp_session parameter in hawktcpdaemon.cfg.
The following TLS/SSL parameters are applicable to -tcp_session and -ami_tcp_session.
-ami_tcp_session <self_IP>:<port> <hawk_agent_IP>:<AMI_session_port>
<self_IP>:<port> - The unique socket address of the Hawk Event service for AMI communication. The socket address should be different from the <self_IP>:<port> specified for the -tcp_session property of Hawk Event Service.
<hawk_agent_IP>:<AMI_session_port> - The socket address of the Hawk agent for AMI communication. This socket address is same as <self_IP>:<port> specified for the -ami_tcp_session parameter in hawkagent.cfg.
This option is ignored if the -ft option is not specified.
Database Configuration
To setup database, add the appropriate .jar file of the JDBC driver classes, from the database vendor, to the HAWK_HOME/lib based on the value of the -JDBCdbType parameter.
 
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved