An Instrumented Application Looks like a Microagent

You interact with the instrumented application using the TIBCO Hawk agent by calling the methods of microagents associated with that agent. An AMI-instrumented application appears and acts as though it were a microagent in the TIBCO Hawk system.

Interaction with an AMI-instrumented application can use the following means:

Interactive monitoring using the TIBCO Hawk Console. See Monitoring an Instrumented Application through the TIBCO Hawk Console for more information on this.

An example of this might be using the TIBCO Hawk Console to survey many instances of the instrumented application by means of a network query. Another example might be to make simultaneous changes to many such instances by performing a network action.

Automating monitoring and management of the application by creating rulebases to be processed by TIBCO Hawk agents.

An example of this might be creating rulebases to monitor the application’s error state, detect critical conditions, and increase the output of debug information until the problem is resolved.

Note: An instrumented application is not dependent on the presence of an TIBCO Hawk agent. The relationship between TIBCO Hawk agent and TIBCO Hawk instrumented application is completely voluntary. The management interface might be active only in some instances of the application, or only at specific times during an instance’s activity.

A management interface can be divided into two major portions:

The initialization code. This code creates a TIBCO Hawk AMI session, passes on the address of a callback function through which messages are to be received, and sets up the functionality to negotiate discovery with a manager.
A callback function that receives messages from the TIBCO Hawk AMI session. The callback function examines the message and passes it on to one of several internal methods for processing.