Browse Prior Art Database

Rulebase Reorganizing Agent

IP.com Disclosure Number: IPCOM000019698D
Original Publication Date: 2003-Sep-25
Included in the Prior Art Database: 2003-Sep-25
Document File: 1 page(s) / 6K

Publishing Venue

IBM

Abstract

Processing Time for events is a crucial element for customers of the IBM Tivoli Enterprise Console. Since every event that is generated from a host that the TEC Server is monitoring must be processed by the rule engine that resides on the Tivoli Enterprise Server, the rule engine is a constant bottleneck for the processing time of TEC. The rule engine is made up of a list of classes and rules. Every event that comes into the TEC Server needs to be checked against the list of classes to see if it is a valid class, and if it is a valid class, it must be checked against every rule to see what needs to be done to it, if anything. As the number of classes and rules grow inside of a rulebase, processing time is decreased. Most customers do not keep track of which classes and rules are being utilized by the EventServer, so there is a strong possibility that there are rules in the rulebase that are never called. The more classes and rules that can be eliminated from the rulebase will speed up the processing time of events at the server.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 1

Rulebase Reorganizing Agent

Every event that is generated and sent to the IBM Tivoli Enterprise Console (ITEC) has to go through the Rule Engine. The Rule Engine is composed of what are known as rules and classes. Classes define what events the TEC server knows and cares about. The rules tell the Event Server what to do with the events. Rules are commonly grouped together and packaged into a RuleSet which is then loaded into TEC. The number of allowable rulesets is limitless and so is the number of rules that make up a ruleset. The more rules and rulesets that customers have, the longer processing time becomes because each event has to be checked against each ruleset. If the environment doesn't generate and send many events to TEC then processing time in the rule engine does not make much of a difference. On the other hand if the TEC Server is receiving events constantly from the many sources that it monitors, processing time in the rule engine becomes crucial. Currently today there is no checking on the performance of the rules in the rule engine. It is possible that some rulesets have rules that have not been used since the TEC Server was first installed. The only solution available today is done manually. Someone would have to sit down and look at the rules and figure out what rules are being used and which ones are the ones that require the most attention. Currently, since there is no way to keep track of this data, this is almost impossible and would require a significant amount of time and effort.

The rules and rulesets that make up a rule base can be thought of as being one long list and the same goes for the classes. Each new event that comes into the rule engine first has to go through the class list to see if it is a valid...