Hawk Display Configurations

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:

Hawk Display Configuration Properties

Logical Group

Parameters

TIBCO Rendezvous (RVD) Session

-rvd_session <service> <network> <daemon>

TCP Transport for TIBCO Hawk

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

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.

Hawk Display Configuration Parameter Details

Property

Mandatory

Default Value

Description

-hawk_domain

Yes

“default”

See Hawk Domain for details.

TIBCO Rendezvous Transport

-rvd_session

No

7474 "" tcp:7474

Comment this option if you are using TCP Transport for TIBCO Hawk 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

TCP Transport for TIBCO Hawk

-tcp_session

No

localhost:2581 localhost:2561

Set this option to configure the TCP Transport for TIBCO Hawk as the primary transport for the communication.

The syntax of the property is:

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

where,

• <self_IP>:<port> - The unique socket address of Hawk Display 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 the Hawk Cluster Manager (hawktcpdaemon.cfg).

TIBCO EMS Transport

-ems_transport

No

 

Comment this option if you are using TCP Transport for TIBCO Hawk 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).

-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

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