Browse Prior Art Database

Dynamic distribution of rule engine Disclosure Number: IPCOM000030083D
Original Publication Date: 2004-Jul-27
Included in the Prior Art Database: 2004-Jul-27
Document File: 2 page(s) / 33K

Publishing Venue



Disclosed is a system for the automatic selection and deployment of an appropriate rules processing engine along with a rule base distribution.

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

Page 1 of 2

Dynamic distribution of rule engine

An event management system captures events from a variety of sources and correlates them together so that their relationships with each other may be discovered and some action may be performed. The subject matter expert, or "correlation rules writer", writes rules for the event management system that define these relationships and actions to be taken. As events arrive, they are evaluated by the event management system to determine the cause and effect relationship between event instances so that it can take appropriate action for each event, if any.

To simplify the task of writing correlation rules, a Graphical Rules Builder (GRB) may be provided by a vendor to build rules using a graphical notation. Using a GRB is desirable for most users because it hides the syntax of the rules language and allows them to focus on building business logic. This can be especially useful if a customer's environment has a need to implement multiple rules engine technologies across the enterprise (e.g. rules-based inference engines, state-based correlation, neural net engines, etc) and will write rules targeting these specific engines according to their need in the enterprise. In such an environment, rules are developed and saved to a local rule base on the event management server where they are executed by a rules engine. In most large IT environments, customers have several event management servers distributed throughout the enterprise for the purpose of workload distribution or to perform different tasks in different areas of the enterprise. While the rules for each engine technology may be implemented in different rule languages, a GRB can hide many of the implementation details of a language. In fact, this is the purpose of providing such a tool: to shield the user from the implementation details and syntax of any given rules technology. The rule writer should be able to focus on writing business rules and...