Browse Prior Art Database

Configuration Model for Event Transmission on an Event Management Solution.

IP.com Disclosure Number: IPCOM000028515D
Original Publication Date: 2004-May-18
Included in the Prior Art Database: 2004-May-18
Document File: 2 page(s) / 145K

Publishing Venue

IBM

Abstract

The core idea of this invention is the organization of configuration data for event sources on an event management solution. By separating data processing aspects from data transmission aspects, the configuration data can modeled in a way that allows combination of processing and transmission aspects into a single event source configuration profile. Such arrangement simplifies the configuration and administration of a large number of event sources distributed across the network.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Configuration Model for Event Transmission on an Event Management Solution .

The three layers of a large event management solution can be dividied in 'event sources', 'event server', and 'event consumers'

The vendor of the event server layer is usually the owner of the client libraries used at the event sources and event consumers. Such control is required to ensure that (1) the event server layer receives data in the format it expects, (2) ensures a common format for the data served to the consumers.

The library provided to event sources is hereafter called an 'event emitter library'.

Event sources are, by far, more numerous than event consumers. Typical IT installations may easily contain thousands of event sources spread through the network. Managing the configuration for these sources is a daunting task, which requires proper modelling to alleviate at least the burden of managing the configuration for the event emitters embedded into these sources.

The invention separates the configuration aspects in terms of a data transport profile and a local data processing profile.

The data transport profile contain all attributes required to transmit the event data from an event source to an event server. For instance, the event server hostname, the encoding mechanism, and the wire format.

The data processing profile contain attributes that the event emitter could use to refine the local processing of the event data. For instance, a filtering expression indicating that events with a certain characteristic should not be sent to the event server layer.

The invention assigns symbolic names to each profile. A list of these symbolic names to define an Event Emitter Configuration Profile. Other solutions, such as TEC, do not have this separation and list the actual attributes in the Event Emitter Configuration Profile. Arranged this way, there is a combinatorial aspect to the system administration. For instance, let us assume three different kinds of event sources (NT monitors, WBI monitors, and TBSM), each with their own event filtering policies sending event data to the same event server. While establishin the event emitter configuration profile for these sources, a system administrator would have to define three different profiles with the same destination (but with different filters for each kind of event data). If the destination ever changes, the system administrator would have to update it in three different places.

With the proposed new approach, a system administrator woul...