Hawk Application Management Interface (AMI) Configuration (optional)

TIBCO Hawk AMI can be used to monitor BusinessEvents deployments.

TIBCO Hawk AMI Configuration
AMI Hawk Service
Specifies the TIBCO Hawk port number, for example, TIBCO Rendezvous connects with TIBCO Hawk on the default port 7474. AMI Hawk Service and AMI Hawk Daemon must be set with valid values together. Setting only one of them, results in an error.
AMI Hawk Daemon
Specifies the location of the TIBCO Hawk Daemon. A value of "tcp:yyyy" corresponds to a local Hawk Daemon where "yyyy" is the port number. A Hawk Daemon located elsewhere is specified by a value of the protocol, IP address, and port number: "tcp:xxx.xxx.xxx.xxx:yyyy".

The AMI Hawk Service and the AMI Hawk Daemon ports might be the same or they might be different. By default, different TLMs on the same engine daemon (physical machine) are using the same RV transport (default AMI Hawk Service=7475, and default AMI Hawk Daemon=tcp:7474). This setting enables visibility of all of the deployed applications on each TLM even if some applications are not deployed on this particular TLM.

Note: The actual AMI Hawk Service port for the runtime component instance is incremented by an integer according to the engine instance ID. For example, if the user sets the AMI Hawk Service to 6464 and the component is instantiated to run on engine instance 1, the service is reported in the hawkagent.cfg file as 6465. When the component is scaled up to other engine instances the AMI Hawk Service value is incremented higher by the enabler automatically.

Generally, AMI Hawk Network is an empty string.