Transport Mode Configuration

Different transport modes are available to be configured as a means of communication between Hawk Agent and HMA, and Hawk Agent and Hawk Console, and they are:

TIBCO Rendezvous (RV)
TCP Transport for TIBCO Hawk
TIBCO Enterprise Message Service (EMS)

Note 

At least one transport mode should be configured in the configuration files of Hawk Agent, Hawk Microagent, Hawk Event, and Hawk Console to enable message or event communication among various Hawk components.

TIBCO Hawk installation has TCP Transport for TIBCO Hawk configured as the default mode of message and event transport between Hawk Agent and AMI-based applications, as well as between Hawk Agent and Hawk Console.

If you choose TCP Transport for TIBCO Hawk as the transport between Hawk Agent and Console, you can use the same transport between Hawk Agent and AMI based application except HMA. For HMA, you can use TIBCO Rendezvous as transport and use TCP Transport for TIBCO Hawk and TIBCO Rendezvous Bridge for communicating with Hawk Agent.

If TIBCO Rendezvous is chosen as a transport between the Hawk Agent and the Hawk Console, 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.

If you choose to use TIBCO Enterprise Message Service as the transport between the Hawk Agent and the Console, you can only use TIBCO Rendezvous as the transport between the Hawk Agent and the HMA or other AMI based applications.

The above combinations can be configured using various configuration files, as described in next few sections of this chapter.

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, and whether any of them share the same TIBCO_HOME installation folder.