Tibco hawk rules

architekt:
TIBCO Administrator is the preferred monitoring and management application for TIBCO BusinessWorks. However, the process engine is instrumented with a TIBCO Hawk microagent that can be used to perform most administrative functions.

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.
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.
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.
TIBCO Hawk Event Service
The TIBCO Hawk Event Service is a process that records TIBCO Hawk alerts and changes in agent status. When communication with an agent is lost, the Event Service can invoke a user-provided script. Alerts and notifications can be recorded to log files or a database.
Typically, the TIBCO Hawk Event Service is installed on a minimal number of computers in the network.

madhusudhaneai:
Hi,

Here i am adding few more points

Hawk- The Tibco monitor.

The tool hawk is used to monitor the servers, individual machines and the processes and many more. This is very active and accurate as its name suggests. Hawk has the capability to monitor the smallest bit of events, processes, services, system information and other things involved. Hawk can monitor the above artifacts in the distributed systems/network. The domain utility is already defined to give the benefit of the distributed systems. The domain configured artifacts classify works, as the Namespaces does for the OOPs.

Some BENEFITS of Hawk are as under:

Hawk monitors all the artifacts on the basis of the micro-agents, agents and nodes. This traps the alerts sent by the network system hence this minimizes the network traffic by not exclusively asking for messages.


·        This provides a centralized view of the system to be monitored.

·        It gives you the flexibility to monitor all the domains simultaneously.

·        Rules can be put together in Rulebase and implemented over the Hawk.



How to make RULEBASE:

There are two ways to create and deploy the rulebase.


1)      Through Hawk Display:


·        Open the Hawk Display

·        Create the domain if required.

·        Create the agent

·        Identify the micro-agent on the agent.

·        Create the rule for the specific event, messaging etc you want.

·        Send this for deployment.


2)      Through the template:


·        Create a template where rules can be written.

·        Set the parameters in the template for your rules.

·        Create the .hrb (hawk rulebase) file.

·        Create the .mar(Contains all the hrb files) file.

·        Now deploy the .mar file on the server.


After all these steps restart the hawk to implement the hawk rules created.

Now you will get the result in the form of mails, logs process restarts etc whatever you configured for the problem/observation in the rulebase

Regards
Madhusudhan

bisu:
Hi,
  I'm learning TIBCO Hawk(4.8.1 on WinXP) for past few days. I have managed to get a basic idea about the product and the configuration. I have managed write monitoring rules for Files, Processes etc. Now my target is to monitor TibcoBW processes. To do that I have written two BW processes, first one reads a file and writes the content of the file to a JMS Queue, the second process reads the JMS Queue and writes the same to a file. I have deployed them manually using TIBCO Administrator(5.6). I can see that the processes are running, also I can see the microagents associated with the processes and can invoke the methods as well. However when I open my Hawk Display, right click on the agent and say "Get Microagents", I can't see the microagents associated with the BW Processes. Can anybody please help?

Regards