Three transport modes are available to be configured as a means of communication between Hawk Agent and HMA, and Hawk Agent and Hawk WebConsole, and they are:
TIBCO Hawk 5.2 installation has TIBCO Rendezvous configured as the default mode of message and event transport between Hawk Agent and HMA, as well as between Hawk Agent and Hawk WebConsole.
|
|
If either TIBCO DataGrid or TIBCO Rendezvous is chosen as a transport between the Hawk Agent and the WebConsole, the same is used a transport between the Hawk Agent and the HMA or other AMI based applications. You cannot configure it to use a different transport. However, if you choose to use TIBCO EMS as the transport between the Hawk Agent and the WebConsole, you can only use TIBCO Rendezvous as the transport between the Hawk Agent and the HMA or other AMI based applications.
|
TIBCO Rendezvous and TIBCO EMS are two independent products that need to be installed separately. Additional configurations need to be performed manually based on whether they are installed before or after installing TIBCO Hawk 5.2, and whether any of them share the same
TIBCO_HOME installation folder.
If you are using or planning to use a single TIBCO_HOME for all TIBCO Rendezvous, TIBCO EMS, and TIBCO Hawk components, read this section. Otherwise, you might skip to the section
Different TIBCO_HOME Locations for Various TIBCO Products.
You use an existing transport (TIBCO Rendezvous or TIBCO EMS) either from a previous installation of TIBCO Hawk 4.x or independent installations of these TIBCO products in the same
TIBCO_HOME where Hawk 5.2 is installed. Update all the TRA configuration files (for example,
tibhawkagent.tra), script files (such as, startwebconsole and starthma), Hawk WebConsole configuration files with the correct locations of
EMS_HOME and
RV_HOME and the execution environment.
If you install TIBCO Rendezvous or TIBCO Enterprise Message Service in the same
TIBCO_HOME after TIBCO Hawk 5.2, ensure the following to set the correct runtime environment for the TIBCO Hawk components.
|
−
|
EMS_HOME/lib/jms.jar (whenever EMS version is below 8.0) or EMS_HOME/lib/jms-2.0.jar (in case of EMS 8.x)
|
If you are using or planning on using a different TIBCO_HOME for all TIBCO Rendezvous, TIBCO Enterprise Message Service, and TIBCO Hawk components, read this section. Otherwise, skip to the next section.
Since TIBCO_HOME for Hawk 5.2 is different from that of TIBCO Rendezvous and TIBCO Enterprise Message Service, ensure that appropriate installation locations are updated as follows:
|
−
|
EMS_HOME/lib/jms.jar (whenever EMS version is below 8.0) or EMS_HOME/lib/jms-2.0.jar (in case of EMS 8.x)
|
|
•
|
To configure Hawk WebConsole runtime environment, assuming TIBCO Hawk 5.2 is installed with default supplied Tomcat web server, edit and modify HAWK_HOME/webconsole/startwebconsole.bat and HAWK_HOME/webconsole/tomcat/bin/setenv.bat (the .bat file on Windows, and the .sh file on UNIX/Linux) to set RV_HOME and EMS_HOME correctly.
|
The TIBCO Rendezvous software is the default transport between the Hawk Micro Agent and Hawk Agent and also between the Hawk Agent and Hawk Console applications.
Configure the -rvd_session parameter in the configuration files to re-enable the TIBCO Rendezvous as transport back from TIBCO EMS or TIBCO DataGrid.
TIBCO Hawk connects to the TIBCO Rendezvous daemon by creating a session. In the configuration files, ensure that the
-as_session and
-ems_transport parameters are commented out, and then configure the
-rvd_session parameter. TIBCO Rendezvous transport creation calls accept three parameters that govern the behavior of the transport:
service,
network and
daemon.
|
•
|
service instructs the Rendezvous daemon to use this service whenever it conveys messages on this transport. You can specify the port number as the service to be used, for example, " 7474".
|
|
•
|
network instructs the Rendezvous daemon to use a particular network for all communications involving this transport. The network parameter consists of up to three parts, separated by semicolons: network, multicast groups, and send address.
|
|
•
|
daemon instructs the transport creation function about how and where to find the Rendezvous daemon and establish communication. For remote daemons, specify two parts (introducing the remote host name as the first part), for example, tcp:7474:
|
Configure the -as_session parameter in the configuration files to enable the TIBCO DataGrid as transport.
Because the TIBCO Hawk software uses the functionality of the TIBCO DataGrid system, it must connect to a TIBCO DataGrid by creating a session. In the configuration files, ensure that the
-rvd_session and
-ems_transport parameters are commented out, and then configure the
-as_session parameter.
|
•
|
listen url specifies the interface and the TCP port that the process uses to listen for incoming connections from new members to the metaspace, and specified in the form of a URL. To use a listen URL, use a string of the form:
|
|
•
|
discovery url determines how the members are discovered. Discovery can be unicast (TCP) or multicast (PGM —Pragmatic General Multicast).
|
Some parameters need to have the same values across all components within a Hawk Domain for the proper functioning of these components. These parameters are:
|
•
|
as_receive_buffer_size and as defined in the HawkAgent, HMA and receiveBufferSize in Webconsole. It is recommended not to change the default values.
|
|
•
|
as_virtual_node_count in Hawk Agent and HMA and virtualNodeCount in WebConsole respectively. It is recommended not to change the default values.
|
You can specify backup servers to connect to in the event of the failure of the primary server. The serverURLs for the primary and backup server(s) are specified as a comma-separated list of URLs.
If a connection to the first URL fails, the next URL in the list is used to attempt a reconnection. The connections in the list are attempted in sequence (wrapping to the start of the list, if the first connection was not the failed connection) until all URLs have been tried. If no connection is established after all URLs have been tried, the connection fails.
|
•
|
store—the directory to store TIBCO EMS data.
|
|
•
|
j2se—Use this option when you want to use the default Java Cryptography Extension (JCE) bundled with the Java JRE.
|
|
•
|
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 <suite-name(s)>—When specifying this option to specify the cipher suites that can be used, use the ^ qualifier instead of a - qualifier. For more information on specifying cipher suites, refer to the TIBCO Enterprise Message Service documentation.
|
|
•
|
-ssl_no_verify_host—If this option is present, it this indicates that the TIBCO Hawk component should not verify the server. Conversely, if this option is not included in the configuration file, it indicates that TIBCO Hawk component should verify the server.
|
|
•
|
-ssl_trusted—The option specifies the file name of the server certificates. This option can be repeated if more than one certificate file is used.
|
|
•
|
-ssl_no_verify_hostname—This option specifies that the client should not verify the name in the CN field of the server certificate. Conversely, if this option is not included in the configuration file, it indicates that TIBCO Hawk component should verify the name in the CN field of the server certificate.
|
|
•
|
-ssl_expected_hostname—The name that is expected in the name of the CN field of the server certificates is specified by this option. The value of this option is used when the -ssl_no_verify_hostname option absent from the configuration file.
|
|
|
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—This option specifies the digital certificate of the TIBCO Hawk components.
|
|
•
|
-ssl_private_key—This option indicates the private key of the TIBCO Hawk component. If the key is included in the digital certificate in -ssl_identity, then you may comment this parameter.
|
|
•
|
-ssl_password—The password to decrypt the identity file of the Hawk component.
|
On Microsoft Windows, the password is obfuscated before it is stored in the Microsoft Windows registry. In order to use the EMS password encrypt/decrypt functionality, all TIBCO Hawk components (including the tibhawkpassword wrapper) have to use JRE 1.8 or above.
If you need to change the username and password information for the EMS server after installation, a utility is provided to encrypt your password. The following steps detail the use of this utility:
A standalone TIBCO Hawk 5.2.0 installation does not need any changes in any of the configuration files for you to execute TIBCO Hawk and its components using TIBCO Rendezvous as the default transport. However, if you want to use different or existing transport(s) (TIBCO DataGrid or TIBCO EMS) or use different port or security, refer to the following table.
These executable or scripts are located in CONFIG_FOLDER/bin and
HAWK_HOME/webconsole.
A Hawk domain is a logical grouping of Hawk Components. The Hawk Agent, the WebConsole API and the AMI instrumented applications can all communicate with each other only if they all belong to the same hawk domain. A hawk domain constitutes of a transport and a domain name.
Some components may have additional requirements in order to communicate with the Hawk Agent such as to specify the Hawk Agent name to connect to.
