Browse Prior Art Database

Event Launch Manager and Launch In Context Disclosure Number: IPCOM000021835D
Original Publication Date: 2004-Feb-11
Included in the Prior Art Database: 2004-Feb-11
Document File: 2 page(s) / 10K

Publishing Venue



The idea behind this article is to be able to seamlessly move from events to the applications associated with the event, in order to resolve the issues pertaining to that event . Current diagnostic solutions require manual steps to move from an event presented to a user on a console to the appropriate application console. Typically a user would cut data for the event and paste into the required application, assuming they could figure out what application to use. There are no existing solutions that allow this to happen programmatically. This article addresses the problem by using Event Launch Manager to provide all the information required to automate invocation of diagnostic application from any event.

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 72% of the total text.

Page 1 of 2

Event Launch Manager and Launch In Context

Event Launch Manager enables seamless integration of events/alerts to associated applications in order to diagnose and resolve the issues causing that event.

This invention uses three key pieces to enable such integration: 1) The population of the event with application required information (e.g. application identifier, application drill-down context)

    Events are usually generated by a monitoring application, hence when an event is being generated the application can embed information such as application identifier, event cause, event detail etc in easily extractable form right in an event.

2) Ability to extract the information from the event.

    Events from different applications could be formatted differently, hence a mechanism to recognize and parse events from multiple applications is required. Event Launch Manager gets this ability by using different parsers to parse the various event formats.

3) Rules and Rule engines.

    A mechanism to express rules to associate event with a diagnostic application based on the content of an event, and an implementation of rule engine to apply such rules against given event are required.

Together these components provide the necessary function required to programmatically move from an event to the application that is used to service that event. Figure 1 is an example implementation using the components explained above:


Page 2 of 2

Event Source


1. Fetch Event 2. Parse event