Overview

 This chapter gives a basic overview of the

TIBCO Hawk monitoring system, its
components.

12/30/09 Infokall Enterprise Solutions 1

 Components
 The TIBCO Hawk monitoring
system consists of the following
main software components.

12/30/09 Infokall Enterprise Solutions 2

 Components
 TIBCO Hawk Agent
 TIBCO Hawk Microagent
 TIBCO Hawk Display Program

12/30/09 Infokall Enterprise Solutions 3

 TIBCO Hawk Agent

 A TIBCO Hawk agent is an autonomous process

that resides on each computer and monitors
systems and applications on that computer.
Agents run independently of the TIBCO Hawk
Display.

 Agents operate autonomously and are active

whenever the operating system they monitor is
active. Agents use sets of rules, called
rulebases, to configure system management,
status, and automation tasks.

 A TIBCO Hawk agent must be installed on each

computer you wish to monitor.

12/30/09 Infokall Enterprise Solutions 4

 TIBCO Hawk
Microagent
 A TIBCO Hawk Microagent (HMA) is a partner
process to the TIBCO Hawk agent and provides
the local agent with methods for monitoring the
host operating system.

 Like the agent, a TIBCO Hawk Microagent is

generally installed on each computer you wish to
monitor.

12/30/09 Infokall Enterprise Solutions 5

 TIBCO Hawk
Display Program
The TIBCO Hawk Display program is used by
system administrators to view network health and
to create rulebases (sets of rules that automate
monitoring activities).

A TIBCO Hawk Display should be installed on any

computers you wish to use for monitoring the
network or for building rulebases.

12/30/09 Infokall Enterprise Solutions 6

 TIBCO Hawk
System
Architecture

12/30/09 Infokall Enterprise Solutions 7

 TIBCO Hawk
System
Architecture
 The TIBCO Hawk system is made up of two main components: agents and
Console Applications. Agents perform the bulk of the monitoring duties, and
Console Applications act as user interfaces for status and configuration (TIBCO
Hawk Display), historical event loggers (TIBCO Hawk Event Service), or bridges
to other management systems.

 The right side of the diagram shows TIBCO Hawk agents installed on machines
to monitor local resources and conditions. Default microagents are used to
monitor objects such as operating system performance, processes, log files,
application metrics or the status of TIBCO Rendezvous sessions.

 The left side of the diagram shows how user applications can be instrumented
and monitored using TIBCO Hawk agents. In both scenarios, the TIBCO Hawk
Application Management Interface (AMI) protocol acts as a gateway between
the application’s management capabilities and the local TIBCO Hawk agents.
An application can be directly instrumented with the AMI protocol to expose its
management operations and data. If an application already employs a
management interface other than AMI, an AMI adapter can be built to allow the
agent to discover and exercise it.

12/30/09 Infokall Enterprise Solutions 8

 TIBCO Hawk
System
Architecture
 The left side of the diagram shows how user applications can be
instrumented and monitored using TIBCO Hawk agents. In both
scenarios, the TIBCO Hawk Application Management Interface
(AMI) protocol acts as a gateway between the application’s
management capabilities and the local TIBCO Hawk agents. An
application can be directly instrumented with the AMI protocol to
expose its management operations and data. If an application
already employs a management interface other than AMI, an AMI
adapter can be built to allow the agent to discover and exercise it.

12/30/09 Infokall Enterprise Solutions 9

 Building a Rule
 Most monitoring tasks consist of periodic checking for some
problem condition. When the problem is detected, an alarm is sent
or corrective actions are taken. If the application goes down, for
example, capture some diagnostics and execute a startup script. If
too much disk space is consumed, delete some temporary files. If
duplicate processes are running, terminate the most recent one.
When you create a rule, you specify this monitoring logic and
package it for a TIBCO Hawk agent. The agent can apply the rule
again and again without intervention. If a problem occurs, the agent
can solve it by taking corrective action, or notify you that the
problem requires attention, or both, depending on rule design.

 Rules consist of data sources, tests, and actions. Data sources are
microagent methods that periodically collect or asynchronously
return information to an agent. One or more tests are applied to the
resulting data set. When a particular test evaluates to true, one or
more actions can be triggered.

12/30/09 Infokall Enterprise Solutions 10

 Flow of Rules
and Tests

12/30/09 Infokall Enterprise Solutions 11

 AMI Protocol
 The TIBCO Hawk Application Management Interface
(AMI) is a protocol programmers can use to expose
internal application methods to TIBCO Hawk. Such
applications are said to be instrumented with an AMI
interface. Applications instrumented with AMI are
represented by microagents and can be used as a
data source by TIBCO Hawk agents. AMI is also used
to build adapters and gateways between external
applications and the TIBCO Hawk system. AMI uses
TIBCO Rendezvous messaging to communicate
between an AMI application and TIBCO Hawk agents.

12/30/09 Infokall Enterprise Solutions 12