Overview

Configuration Objects

There are three types of configuration objects in TIBCO Hawk:

•

Rulebase

•

Schedule

•

Rulebase Map

A TIBCO Hawk Agent manages and monitors managed objects by processing rulebases. A rulebase is a named collections of rules that contain management logic. The management logic in a rule is defined by the tests and actions to be taken from data collected from a given data source. A rulebase can be loaded on a single agent, on a group of agents, or on every agent in the network depending on the TIBCO Hawk Agents' configuration mode.

A schedule defines when a rulebase, rule, test or action is active. If schedule is not specified in a rulebase, the rulebase is always active when loaded. A schedule contains inclusion and/or exclusion periods that will determine if a schedule is in-schedule or out-of-schedule at a specified time.

A rulebase map maps rulebases to TIBCO Hawk Agents on the network. It directs TIBCO Hawk Agents or groups of agents on the network to load particular rulebases at startup. It is used by TIBCO Hawk Agents running in either Manual Configuration Mode or Repository Configuration Mode.

Together with the Console API, these configuration objects can be retrieved and sent to TIBCO Hawk Agents or Repositories from a Java application.

How the TIBCO Hawk Configuration Object API Fits In

The TIBCO Configuration Object API provides classes to define configuration objects such as rulebases, schedules, and rulebase maps. These classes enable you to write programs that can create and modify rulebases, schedules, and rulebase maps programmatically without using the editors in the TIBCO Hawk WebConsole. Rulebases, schedules, and rulebase maps are used by TIBCO Hawk agents to monitor and manage systems and applications.

When using the Rulebase Editor, the context of the rulebase is implied. Using this context, the Rulebase Editor presents you with the data sources and actions that are available to the agent. These data sources and actions are in the form of microagents, methods and arguments. When using the Configuration Object API, rulebase objects specify their data sources and actions using the MethodSubscription and MethodInvocation classes of the TIBCO Hawk Console API.

When the TIBCO Hawk Configuration Object API is used with the TIBCO Hawk Console API, the application can dynamically create or update configuration objects on a TIBCO Hawk agent or repository.


	Any complex tests with valid operators can be built using the rulebase related classes in Configuration Object API. However, not all the test conditions built using the Configuration Object API can be modified using the rulebase editor in TIBCO Hawk WebConsole. In such cases, the rulebase editor will simply display the test as a string. However, such complex tests can be edited using a custom-built editor based on the TIBCO Configuration Object API.