Microsoft Technology Licensing, LLC

Patrick R Kenny

Alexander Evgenievich Nosov

Lev Novik

Ashvinkumar J Sanghvi

Raymond W McCollum

Travis Muhlestein

Ahmed El-Shimi

Michael A Thatcher

Howard M Hance

A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Method and apparatus for creating templates

Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Flexible subscription-based event notification

An event management system includes an email consumer for handling email, a paging consumer, an active scripting consumer, a log file consumer, an event log consumer, and a command line consumer. The events in the event management system are represented as objects and each consumer is represented as a class. The system also includes an event forwarding consumer to forward events. The event management system allows the creation of an instance of an event filter which filters events based on event filter properties. The system also allows the creation of an instance of an event consumer which defines an action and creation of a binding between the instance of the event filter and the instance of the event consumer such that the binding includes properties identifying the instance of the event filter and the instance of the event consumer.

Event consumers for an event management system

A correlation system receives multiple events and multiple data elements. The multiple events and data elements are applied to a correlation function which is implemented as a state machine. A specific event is generated if the correlation function is satisfied by the multiple events and the multiple data elements. Additional events and data elements are received if the correlation function is not satisfied by the original events and data elements. The system allows for the identification of a schema for creating state machines that correlate events and/or data. An instance of a particular state machine is created and transitions for the particular state machine are defined by subscribing to one or more events. An update consumer is applied to the particular state machine to update the state of the particular state machine.

Method and apparatus for correlating events

An event distribution and event handling system receives a first event at a first event filter. The first event filter has a set of associated filter criteria, which is applied to the first event. If the first event satisfies the filter criteria, the first event is transformed into a second event and the second event is communicated to a second event filter having a set of associated filter criteria. The second event filter is associated with an event consumer, which performs an action if the second event satisfies the filter criteria associated with the second event filter. The second event includes an event header having a standard format and a payload having multiple payload objects.

Method and apparatus for event distribution and event handling in an enterprise

Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Growing community of inventors

Redmond, WA, United States of America

Patrick R Kenny