Event processing with XML query based on reusable XML query template

Abstract

Methods, systems, and computer-readable media are disclosed for event processing with a query based on a reusable XML query template. A particular method includes receiving a plurality of events from a source and generating a plurality of event objects based on the plurality of events. A query represented by an XML file based on a reusable XML query template is executed with respect to the plurality of event objects to produce a plurality of result objects. Each result object is produced based on an application of at least one operator of the query. A plurality of results is generated based on the plurality of result objects, and the plurality of results is transmitted to a sink.

Description

BACKGROUND

The event-based computation paradigm has grown in importance for enterprises. For example, many business applications and system control applications can be developed based on event-based computation. Generally, event processing applications receive events, analyze the events, and output results (e.g., proposed actions) based on the analysis of the events.

Current event processing systems often use structured query language (SQL) queries to analyze events. Due to the fluid nature of event streams, the relational algebra underlying traditional SQL may not be well-suited for processing events at a high rate. Additionally, performing time-based calculations using the relational operators provided by SQL may be difficult. Further, the semantics of a SQL query may require recitation of specific data sources, rendering a particular SQL query that recites a particular data source unsuitable for use with a different data source.

SUMMARY

The present disclosure describes an event processing framework that utilizes queries based on reusable XML query templates. A single XML query template may be reused with respect to multiple event sources and sinks. For example, an XML query template may be instantiated and bound to a particular input adapter for a particular source and to a particular output adapter for a particular sink. To run the same query against another source and another sink, the XML query template may be re-instantiated and bound to another input adapter and another output adapter. Input adapters and output adapters for various sources and sinks may be user-defined to handle conversion to and from proprietary data formats associated with various sources and sinks.

An XML query template may include a directed graph of operators. The operators may be relational algebra operators, time-based operators, or any other type of operator.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram to illustrate a particular embodiment of a system of event processing that uses a query based on a reusable XML query template;

FIG. 2 is a block diagram to illustrate another particular embodiment of a system of event processing that uses a query based on a reusable XML query template;

FIG. 3 is a diagram depicting an illustrative query template that may be used with the system of FIG. 1 or the system of FIG. 2;

FIG. 4 is a flow diagram to illustrate a particular embodiment of a method of event processing that uses a query based on a reusable XML query template;

FIG. 5 is a flow diagram to further illustrate event processing that uses a query based on a reusable XML query template in accordance with the method of FIG. 4; and

FIG. 6 is a block diagram of a computing environment including a computing device operable to support embodiments of computer-implemented methods, computer program products, and system components as illustrated in FIGS. 1-5.

DETAILED DESCRIPTION

In a particular embodiment, a system is disclosed that includes an input adapter, a query engine, and an output adapter. The input adapter is configured to receive an event from a source and to generate an event object based on the event. The event object includes a payload, a validity start time, and a validity end time. The query engine is configured to execute a query with respect to the event object to produce a result object. The query is represented by an extensible markup language (XML) file that is based on a reusable XML query template. The XML query template is bindable to a plurality of input adapters and to a plurality of output adapters. Result objects are produced based on applying at least one operator of the query to an input of the event objects. The output adapter is configured to generate results based on the result objects and to transmit the results to a sink.

In another particular embodiment, a computer-readable medium is disclosed. The computer-readable medium includes instructions, that when executed by a computer, cause the computer to receive at least one event from a source at an event processing system. Each event is represented in a first data format that is native to the source. The computer-readable medium also includes instructions, that when executed by the computer, cause the computer to convert the at least one event from the first data format to at least one event object formatted in a second data format. Each event object includes a payload, a validity start time, and a validity end time. The computer-readable medium further includes instructions, that when executed by the computer, cause the computer to execute a query with respect to the at least one event object to produce a result object. The query is executed without storing the at least one event object and is represented by an XML file based on a reusable XML query template. The result object is based on an application of at least one operator of the query to the event object and is formatted in the second data format. The computer-readable medium includes instructions, that when executed by the computer, cause the computer to convert the result object from the second data format into a result formatted in a third data format that is native to a sink and to transmit the result to the sink.

FIG. 1 is a block diagram to illustrate a particular embodiment of an event processing system 100 that uses an XML query based on a reusable XML query template. The system 100 is configured to receive events (e.g., an illustrative event 104) from a source 102 via a complex event processing (CEP) input adapter 106 and to transmit results (e.g., an illustrative result 128) to a sink 130 via a CEP output adapter 126. The system 100 includes a CEP query engine 116 configured to execute an XML query 118 based on a reusable XML query template. The XML query template may be “reusable” and “bindable” because the XML query template may be instantiated as multiple queries, where each query is bound to a particular input adapter and a particular output adapter. For example, the XML query 118 may be bound to the CEP input adapter 106 and the CEP output adapter 126. In a particular embodiment, the system 100 is included in a complex event processing (CEP) system.

The CEP input adapter 106 at the system 100 is configured to receive events, such as the event 104 from the source 102. For example, the source 102 may include a database, a server, an event ticker, a network port, a sensor, or some other event source that provides events to the CEP input adapter 106 periodically, randomly, or intermittently in bursts. The CEP input adapter 106 is also configured to generate (e.g., via translation or conversion) event objects (e.g., the illustrative event object 110) based on the events and to transmit the generated event objects to the CEP query engine 116 via an input stream 108. In a particular embodiment, the events received from the source 102 are formatted in a first data format (e.g., a proprietary data format) that is native to the source, and the event objects are formatted in a second data format that is native to the system 100. In a particular embodiment, the second data format that is native to the system 100 specifies that each event object 110 includes an event payload 112, an event validity start time and an end time 114.

The CEP query engine 116 is configured to receive event objects via the input stream 108 and to execute a query 118 with respect to the event objects to produce result objects (e.g., an illustrative result object 124). The CEP query engine 116 is also configured to transmit the result object 124 to the CEP output adapter 126 via an output stream 132.

The query 118 may be represented by an XML file based on a reusable XML query template that is bindable to multiple input adapters and multiple output adapters. Thus, the query template may be reusable with multiple sources and multiple sinks, where usage of the query template with a particular source includes binding the query template to a particular input adapter for the particular source and usage of the query template with a particular sink includes binding the query template to a particular output adapter for the particular sink. An adapter may be user-defined and may be written in a .NET programming language against an adapter application programming interface (API). Query template bindings are further described with respect to FIG. 2. The query 118 may include a directed graph of one or more operators 120. Operators may include, but are not limited to, projection operators, windowing operators, aggregation operators, grouping operators, join operators, and selection operators. Operators may be payload specific, validity start time-specific, validity end-time specific, or some combination thereof. Specific operator types are further described with respect to FIG. 3. The result object 124 is produced based on an application of the operators 120 of the query 118 to the event object 110.

In a particular embodiment, executing the query 118 at the CEP query engine 116 includes comparing event objects to static reference data retrieved from a static data source 122. Event objects may also be compared to historical data (e.g., historical data of the source 102, historical data of the sink 130, historical data of the query 118, or some other historical data) from the static data source 122. In another particular embodiment, executing the query 118 at the CEP query engine 116 includes storing data to the static data source 122.

In a particular embodiment, the query 118 represents a declarative query. Generally, declarative programming languages indicate “what” is to be done (e.g., what particular inputs will be provided and what particular outputs will be generated) rather than “how” it is done (e.g., the underlying algebra functions and the programmatic steps to convert the inputs into the outputs). Thus, it may be easier for users to specify declarative queries as compared to non-declarative queries, because event-level implementation details of declarative queries may not influence the result of declarative queries. For example, a declarative query may be defined in a language integrated query (LINQ) language, a .NET programming language other than LINQ, or a complex event detection and response (CEDR) algebra. For example, an illustrative LINQ query may include:

// filter by the value of event field SourceId and transform
// the event in the project expression
var filter = from e in inputDataStream
where e.SourceId == “s7”
select new { e.SourceId, ConvertedVal = e.Value *100 };

An illustrative XML file representation of the above LINQ query may include:

<QueryTemplate
Name=“cep:/Server/Application/ObjectModelSample/QueryTemplate/SampleQueryTemplate”
xmlns=“http://schemas.microsoft.com/ComplexEventProcessing/2009/05/Metadata”>
<Import Name=“DataInput”
Type=“cep:/Server/Application/ObjectModelSample/EventType/SampleReading”>
<OutputStream Name=“Import.3.0” />
</Import>
<Export Name=“_outputStream_”>
<InputStream Name=“Project.1.2” />
</Export>
<Project Name=“Project.1.2”>
<InputStream Name=“Select.2.1” />
<OutputStream Name=“Project.1.2” />
<ProjectExpression OutputField=“ConvertedVal”>
<Multiply>
<InputField Name=“Value” StreamName=“Select.2.1” />
<Constant
Type=“cep:/Server/Application/system/EventType/System.Double”
Value=“100” />
</Multiply>
</ProjectExpression>
<ProjectExpression OutputField=“SourceId”>
<InputField Name=“SourceId” StreamName=“Select.2.1” />
</ProjectExpression>
</Project>
<Select Name=“Select.2.1”>
<InputStream Name=“Import.3.0” />
<OutputStream Name=“Select.2.1” />
<FilterExpression>
<Equal>
<InputField Name=“SourceId” StreamName=“Import.3.0” />
<Constant
Type=“cep:/Server/Application/system/EventType/System.String”
Value=“s7” />
</Equal>
</FilterExpression>
</Select>
</QueryTemplate>

In a particular embodiment, executing the query 118 at the CEP query engine 116 includes parsing the XML file representing the query in accordance with one or more XML schema definition (XSD) files. For example, such XSD files useable to parse XML queries may be available from Microsoft Corp. at 1, Microsoft Way Redmond, Wash. 98052.

In a particular embodiment, the CEP query engine 116 is configured to provide “in-flight” processing of event objects. That is, the CEP query engine 116 may receive event objects, execute the query 118, and transmit produced result objects without storing the event objects or the result objects in a memory of the system 100. In a particular embodiment, support for in-flight processing enables the system 100 to process hundreds of thousands of event objects per second, or more.

The CEP output adapter 126 at the system 100 is configured to transmit results such as the result 128 to the sink 130. The CEP output adapter 126 is also configured to generate (e.g., via translation or conversion) the results based on result objects (e.g., the result object 124) received from the CEP query engine 116 via the output stream 132. In a particular embodiment, result objects received from the query engine are in the second data format native to the system 100 and the results are formatted in a third data format (e.g., another proprietary data format) that is native to the sink 130. The sink 130 may include a communications device, a mobile device, a computer system, a database, a server, an event store, or some other consumer of results produced by the system 100.

In a particular embodiment, the CEP input adapter 106 and the CEP output adapter 126 are coupled to network interfaces, such as a wired interface (e.g., Ethernet), a wireless interface (e.g., IEEE 802.11a/b/g/n), or some other network interface. In another particular embodiment, one or more of the source 102 and the sink 130 may be local to a computer system that includes the system 100 of FIG. 1.

In a particular embodiment of operation, the CEP input adapter 106 may receive the event 104 from the source 102 and generate an event object 110 based on the event 104. The event object includes an event payload 112 and validity start/end times 114. The CEP query engine 116 may execute the query 118 with respect to the event object 110 to generate the result object 124. The query may be represented by an XML file that is based on a reusable XML query template (e.g., generated based on a LINQ query). The CEP output adapter 126 may generate a result 128 based on the result object 124 and may transmit the result 128 to the sink 130

It will be appreciated that the system 100 of FIG. 1 may enable event processing using XML queries based on reusable XML query templates. Thus, the system 100 of FIG. 1 may enable a user to define a query without reciting specific sources or sinks and without depending on technology-specific operations associated with the specific sources or sinks. It will further be appreciated that the system 100 of FIG. 1 may provide such event processing functionality in various embodiments. For example, the system 100 of FIG. 1 may be integrated into an embedded dynamically linked library (DLL), an executable file, an operating system service, or a server farm.

FIG. 2 is a block diagram to illustrate another particular embodiment of an event processing system 200 that uses an XML query based on a reusable XML query template. The system 200 is configured to receive events (e.g., an illustrative first event 204 and a third event 206 transmitted subsequent to the first event 204) from a first source 202 and to receive events (e.g., an illustrative second event 210) from a second source 208. The system 200 is also configured to transmit results (e.g., an illustrative first result 228) to a first sink 230 and to transmit results (e.g., an illustrative second result 232) to a second sink 234. The system 200 includes a complex event processing (CEP) query engine configured to execute XML queries (e.g., illustrative CEP queries 220, 222) based on a reusable XML query template.

A first CEP input adapter 212 at the system 200 may receive events from the first source 202, produce event objects 216 based on the events, and transmit the event objects 216 to the CEP query engine 218 as described herein with reference to the CEP input adapter 106 of FIG. 1. Similarly, a second CEP input adapter 214 at the system 200 may receive events from the second source 208, produce event objects 216 based on the events, and transmit the event objects 216 to the CEP query engine 218 as described herein with reference to the CEP input adapter 106 of FIG. 1.

The CEP query engine 218 is configured to receive event objects 216 from the CEP input adapters and execute the CEP queries 220, 222 with respect to the event objects 216 to produce result objects 236. The CEP query engine 218 is also configured to transmit the result objects 236 to the CEP output adapters 224, 226. The CEP queries 220, 222 may be represented by XML files and may be based on the same XML query template. That is, the first CEP query 220 may be an instantiation of the XML query template bound to the first CEP input adapter 212 and the first CEP output adapter 224, and the second CEP query 222 may be an instantiation of the XML query template bound to the second CEP input adapter 214 and the second CEP output adapter 226.

It should be noted that CEP queries may not be limited to producing a single result object for each event object. Depending on the particular operator(s) in the query, any number of result objects may be produced from a single event object, and any number of event objects may be consumed in producing a single result object. For example, a result object may be produced by executing a query with respect to multiple events objects of a particular stream (e.g., a first event object based on the first event 204 and a second event object based on the third event 206).

In a particular embodiment, when the CEP queries 220, 222 are instantiations of the same XML query template, the event objects 216 produced by the CEP input adapters 212, 214 are identically typed. The result objects 236 transmitted to the CEP output adapters 224, 226 are also identically typed. For example, if a directed graph of operators in the XML query template accepts as input one integer value and two floating point values, each of the CEP input adapters 212, 214 produce event objects that include one integer value and two floating values as the event object payload. As another example, if the directed graph of operators in the XML query template produces as an output a single Boolean value, each of the CEP output adapters 224, 226 will accept result objects that include a single Boolean value as the result object payload. Thus, any user-defined input adapter (and by extension, event source) may be bound to an XML query template, provided that the user-defined input adapter produces event objects that fulfill data type expectations of the XML query template. Similarly, any user-defined output adapter (and by extension, result sink) may be bound to an XML query template, provided that the user-defined output adapter accepts result objects that include data types produced by the XML query template. It should be noted that although the particular embodiment illustrated in FIG. 2 depicts identically typed event objects, event objects from input adapters may be dissimilarly typed. For example, when a query template is bound to multiple input streams that are combined via query logic (e.g., a join operator), the event objects transmitted by the input adapters may not be identically typed.

An illustrative embodiment of an XML file that represents a bound query may include:

<?xml version=“1.0” encoding=“utf-8” ?>
<Query
xmlns=“http://schemas.microsoft.com/ComplexEventProcessing/2009/
10/Metadata”
Name=“cep:/Server/Application/appl/Query/AdvanceTameEdge”
QueryTemplate=“cep:/Server/Application/appl/QueryTemplate/AdvanceTimeQueryTemplate”
Description=“”>
<OutputStreamBinding OutputStream =“OutputStream”
OutputStreamTarget=“cep:/Server/Application/appl/OutputAdapter/MultiShapeOutputAdapter”
StreamEventOrdering=“ChainOrdered”
EventShape=“Edge”>
<AdapterConfiguration>
<MyOutputAdapterConfig>
<FileName>AdvanceTimeEdgeOutput.txt</FileName>
<EventCount>39</EventCount>
<SignalEventName>AdvanceTimeEdgeComplete</SignalEventName>
</MyOutputAdapterConfig>
</AdapterConfiguration>
</OutputStreamBinding>
<InputStreamBinding InputStream=“InputStream”
InputStreamSource=“cep:/Server/Application/appl/InputAdapter/MultiShapeInputAdapter”
EventShape=“Edge”>
<AdvanceTime Policy=“Adjust”>
<EventCountFrequency Value=“1” />
<DurationSlack Value=“PT0.000S” />
</AdvanceTime>
<AdapterConfiguration>
<MyInputAdapterConfig>
<FileName>AdvanceTimeEdgeInput.txt</FileName>
</MyInputAdapterConfig>
</AdapterConfiguration>
</InputStreamBinding>
</Query>

The first CEP output adapter 224 at the system 200 may receive result objects 236 from the query engine 218, produce results (e.g., the first result 228) based on the result objects 236, and transmit the results to the first sink 230 as described herein with reference to the CEP output adapter 126 of FIG. 1. Similarly, the second CEP output adapter 226 at the system 200 may receive result objects 236 from the query engine 218, produce results (e.g., the second result 232) based on the result objects 236, and transmit the results to the second sink 234 as described herein with reference to the CEP output adapter 126 of FIG. 1.

In a particular embodiment of operation, the first CEP input adapter 212 may generate event objects 216 based on events (e.g., the first event 204 and the third event 206) received from the first source 202, and the second CEP input adapter 214 may generate event objects 216 based on events (e.g., the second event 210) received from the second source 208. The event objects 216 are identically typed. The CEP query engine may execute a first CEP query 220 bound to the first CEP input adapter 212 and to the first CEP output adapter 224 to generate result objects 236 that are transmitted to the first CEP output adapter 224. The CEP query engine may also execute a second CEP query 222 bound to the second CEP input adapter 214 and to the first CEP output adapter 226 to generate result objects 236 that are transmitted to the second CEP output adapter 226. The result objects 236 may be identically typed. The first CEP output adapter 224 may transmit results (e.g., the first result 228) to the first sink 230 and the second CEP output adapter 226 may transmit results (e.g., the second result 232) to the second sink 234

In a particular embodiment, the first CEP query 220 and the second CEP query 222 execute simultaneously. In another particular embodiment, the first CEP query 220 executes during a first time period and the second CEP query 222 executes during a second time period (e.g., subsequent to the first time period).

It will be appreciated that the system 200 of FIG. 2 may enable the instantiation of multiple queries based on the same query template. It will further be appreciated that the instantiations (and the input/output adapters bound to the instantiations) may execute simultaneously or successively.

FIG. 3 is a diagram depicting an illustrative query template 300 that may be used with the system of FIG. 1 or the system of FIG. 2. For example, the query template 300 may be the basis for the query 118 of FIG. 1 or the CEP queries 220, 222 of FIG. 2.

A query template may be viewed as a computational assembly line, where the input of the assembly line is attached to an input adapter and the output of the assembly line is attached to an output adapter. To illustrate the use of the query template 300, consider a plurality of power meters configured to measure power consumption (in watts) by a particular machine component. Each of the power meters may function as an event source for an event processing system and my transmit power data 302 to the event processing system in the form of events, where events from a particular power meter include wattage readings from the particular power meter. The power meters may produce multiple event objects per second.

An input adapter 304 of the event processing system may generate event objects (e.g., the illustrative event object 306) based on the power data 302. Each such event object may include as payload an integer power meter identifier (ID) and an integer wattage reading (W, a fixed point reading measured in tenths of Watts), where the ID identifies the particular power meter that produced the wattage reading W. Each such event object includes a validity start time and a validity end time (not shown).

The event objects generated by the input adapter 304 may be transmitted to a query execution engine that is configured to execute a query based on the query template 300. That is, the query execution engine may be configured to execute an instantiation of the query template that is bound to the input adapter 304 and to an output adapter 322. The query template 300 may include a directed graph of operators. For example, in the particular embodiment illustrated in FIG. 3, the operators include a projection operator 308, a hopping window operator 310, a grouping operator 312, a first aggregation operator 314, a second aggregation operator 316, and a join operator 318. In general, the query template 300 may be configured to perform the following calculation logic: “First, divide every received wattage value by 10 to convert the fixed point reading to Watts. Then apply a hopping window of one second to the objects. Next, group the objects by power meter ID and average the wattage readings separately for each group (i.e., average each power meter separately). Calculate the total sum of all such average values over all meters and use that calculated total sum to compute a ratio of wattage consumption reported by a particular power meter to overall wattage consumption (i.e., how much power each machine component associated with each power meter contributes to the overall consumption of the machine).”

In accordance with the above logic, during operation of the event processing system, the projection operator 308 may generate an intermediate value “Wattage=W/10.” Next, the hopping window operator 310 may apply a one second window to the calculation (e.g., collect event objects with validity start times within the last second). The grouping operator 312 may then partition the collection of event objects by power meter ID, and the aggregation operator 314 may compute a value “w” for each power meter, where “w” for a particular power meter represents the average power consumption of the particular power meter over the previous one second. The second aggregation operator 316 may compute a value “wSum” that represents a sum of the “w” value for all power meters. Finally, a join operator 318 may compute a value “Ratio=w/wSum” representing the ratio of power consumption reported by the power meter associated with the event object 306 to total power consumption of all power meters.

The query template 300 may produce result objects (e.g., the illustrative result object 320) having as payload an integer power meter identifier (ID), a floating point wattage reading (W), and a floating point power consumption ratio (Ratio). The result objects may be transmitted by the query execution engine to an output adapter 322, and the output adapter may transmit result data 324 to a client of the event processing system. For example, the client may be a power throttling computer configured to selectively down-throttle power provided to a particular machine component in response to receiving result data 324 indicating that the particular machine component is consuming over 50% of total power.

FIG. 4 is a flow diagram to illustrate a particular embodiment of a method 400 of event processing with a query based on a reusable XML query template. In an illustrative embodiment, the method 400 may performed by the system 100 of FIG. 1 or the system 200 of FIG. 2.

The method 400 includes, at a system including a processor and a memory, receiving a plurality of events from a source, at 402. For example, the plurality of events may be received periodically, randomly, intermittently in bursts, or in some other fashion. For example, in FIG. 1, the system 100 may receive a plurality of events including event 104 from the source 102.

The method 400 also includes generating a plurality of event objects based on the plurality of events, at 404. For example, in FIG. 1, the CEP input adapter 106 may generate a plurality of event objects including illustrative event object 110 based on the plurality of events.

The method 400 further includes, at the processor, executing a query with respect to the plurality of event objects to produce a plurality of result objects, at 406. The query is executed without storing any of the plurality of event objects at the memory and the query is represented by an XML file that is based on a reusable XML query template. Each of the plurality of result objects is based on an application of at least one operator of the query. For example, in FIG. 1, the CEP query engine 116 may execute the query 118 with respect to the plurality of event objects to produce a plurality of result objects, where the query 118 is represented by an XML file based on a reusable XML query template. The result object 124 may be produced by executing the query 118 with respect to the event object 110, including applying the operators 120 of the query 118 to the event object 110.

The method 400 includes generating a plurality of results based on the plurality of result objects, at 408. For example, in FIG. 1, the CEP output adapter 126 may generate a plurality of results including illustrative result 128 based on the plurality of result objects. The method 400 also includes transmitting the plurality of results to a sink, at 410. For example, in FIG. 1, the plurality of results may be transmitted to the sink 130.

FIG. 5 is a flow diagram to further illustrate event processing using a query based on a reusable XML query template in accordance with the method 400 of FIG. 4. In an illustrative embodiment, the method 500 of FIG. 5 may be performed by the system 100 of FIG. 1 or the system 200 of FIG. 2.

The method 500 includes, at a system, receiving at least one event from a source, where the event is represented in a first data format that is native to the source, at 502. For example, in FIG. 1, the CEP input adapter 106 may receive the event 104 from the source 102, where the event 104 is represented in a first data format that is native to the source 102.

The method 500 also includes converting the at least one event from the first data format to at least one event object formatted in a second data format, at 504. The at least one event object includes a payload, a validity start time, and a validity end time. For example, in FIG. 1, the CEP input adapter 106 may convert the event 104 to the event object 110, where the event object 110 is formatted in a second data format and includes the event payload 112 and the event validity start/end times 114.

The method 500 further includes executing a query with respect to the at least one event object to produce a result object, at 506. The query is executed without storing the at least one event object, and the query is represented by an XML file that is based on a reusable XML query template. The result object is produced based on an application of at least one operator of the query and is formatted in the second data format. For example, in FIG. 1, the CEP query engine 116 may execute the query 118 with respect to the event object 110 to produce the result object 124 without storing the event object 110, where the query is represented by an XML file based on a reusable XML query template and where the result object 124 is produced based on application of the operators 120 to the event object 110. The result object 124 may be formatted in the second data format.

The method 500 includes converting the at least one result object from the second data format to at least one result formatted in a third data format that is native to a sink, at 508. For example, in FIG. 1, the CEP output adapter 126 may convert the result object 124 to the result 128, where the result 128 is formatted in a third data format that is native to the sink 130. The method 500 includes transmitting the at least one result to the sink, at 510. For example, in FIG. 1, the CEP output adapter 126 may transmit the result 128 to the sink 130.

It will be appreciated that with a reusable query template, the method 500 of FIG. 5 may enable users to reuse the XML query template with a new source or a new sink by simply encapsulating the conversion logic to translate to and from the data of the new source or the new sink into a new input adapter or a new output adapter.

FIG. 6 depicts a block diagram of a computing environment 600 including a computing device 610 operable to support embodiments of computer-implemented methods, computer program products, and system components according to the present disclosure. In an illustrative embodiment, the computing device 610 may include one or more of the CEP input adapter 106 of FIG. 1, the CEP output adapter 126 of FIG. 1, the CEP input adapters 212, 214 of FIG. 2, the CEP output adapters 224, 226 of FIG. 2, the CEP query engine 116 of FIG. 1, and the CEP query engine 218 of FIG. 2. Each of the CEP input adapter 106 of FIG. 1, the CEP output adapter 126 of FIG. 1, the CEP input adapters 212, 214 of FIG. 2, the CEP output adapters 224, 226 of FIG. 2, the CEP query engine 116 of FIG. 1, and the CEP query engine 218 of FIG. 2 may include or be implemented using the computing device 610 or a portion thereof.

The computing device 610 includes at least one processor 620 and a system memory 630. Depending on the configuration and type of computing device, the system memory 630 may be volatile (such as random access memory or “RAM”), non-volatile (such as read-only memory or “ROM,” flash memory, and similar memory devices that maintain stored data even when power is not provided), or some combination of the two. The system memory 630 typically includes an operating system 632, one or more application platforms 634, one or more applications (e.g., a query engine 636), and may include program data 638 associated with the one or more applications. In an illustrative embodiment, the query engine 636 is the CEP query engine 116 of FIG. 1 or the CEP query engine 218 of FIG. 2.

The computing device 610 may also have additional features or functionality. For example, the computing device 610 may also include removable and/or non-removable additional data storage devices such as magnetic disks, optical disks, tape, and standard-sized or miniature flash memory cards. Such additional storage is illustrated in FIG. 6 by removable storage 640 and non-removable storage 650. Computer storage media may include volatile and/or non-volatile storage and removable and/or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program components or other data. The system memory 630, the removable storage 640 and the non-removable storage 650 are all examples of computer storage media. The computer storage media includes, but is not limited to, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disks (CD), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store information and that can be accessed by the computing device 610. Any such computer storage media may be part of the computing device 610.

The computing device 610 also contains one or more communication connections 680 that allow the computing device 610 to communicate with other computing devices (e.g., an input source 690, an output sink 692, and a static data source 694) over a wired or a wireless network. In an illustrative embodiment, the communication connections 680 include the adapters 106, 126 of FIG. 1 or the adapters 212, 214, 224, 226 of FIG. 2. In another illustrative embodiment, the source 690 is the source 102 of FIG. 1, the first source 202 of FIG. 2, or the second source 208 of FIG. 2. In another illustrative embodiment, the sink 692 is the sink 130 of FIG. 1, the first sink 230 of FIG. 2, or the second sink 234 of FIG. 2. In another illustrative embodiment, the static data source 694 is the static data source 122 of FIG. 1.

It will be appreciated that not all of the components or devices illustrated in FIG. 6 or otherwise described in the previous paragraphs are necessary to support embodiments as herein described. For example, the removable storage 640 and non-removable storage 650 may be optional.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

Those of skill would further appreciate that the various illustrative logical blocks, configurations, modules, and process or instruction steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Various illustrative components, blocks, configurations, modules, or steps have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The steps of a method described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in computer readable media, such as random access memory (RAM), flash memory, read only memory (ROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor or the processor and the storage medium may reside as discrete components in a computing device or computer system.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments.

The Abstract of the Disclosure is provided with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments.

The previous description of the embodiments is provided to enable a person skilled in the art to make or use the embodiments. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope possible consistent with the principles and novel features as defined by the following claims.

Claims

1. A system comprising: a memory; anda processor connected with the memory, the processor executing as a query engine configured to execute queries with respect to event objects to produce result objects, wherein a query is represented by an extensible markup language (XML) file that is based on a reusable XML query template that is bindable to a plurality of input adapters and a plurality of output adapters, the processor executing: binding the reusable XML query template to a first input adapter for a source to input data for execution of the query to produce a first result for the query,binding the reusable XML query template to a second input adapter, different from the first input adapter, for another source to input data for execution of the query to produce a second result for the query, andexecuting processing of the query.

2. The system according to claim 1, wherein the processor further executing outputting of the first result.

3. The system according to claim 2, wherein at least one of the first input adapter, the second input adapter, the query engine, the first output adapter, and the second output adapter are integrated into a complex event processing (CEP) system.

4. The system according to claim 2, wherein the input adapter generates event objects that match an input type specification of the reusable XML query template and wherein the first output adapter accepts result objects that match an output type specification of the reusable XML query template.

5. The system according to claim 1, wherein the processor further executing outputting of the second result.

6. The system according to claim 1, wherein the binding to the first input adapter further comprises binding the reusable XML query template to a first output adapter for a sink to output the first result of the query, and the binding to the second input adapter further comprises binding the reusable XML query template to a second output adapter, different from the first output adapter, for another sink to output the second result.

7. The system according to claim 6, wherein the first input adapter transmits an event object to the query engine via an input stream and the first output adapter receives a result object from the query engine via an output stream.

8. The system according to claim 1, wherein both the first input adapter and the second input adapter are used to produce identically typed event objects in accordance with a type specification of the reusable XML query template.

9. The system according to claim 1, wherein the XML file includes a directed graph of the at least one operator.

10. The system according to claim 9, wherein the directed graph includes a projection operator, a windowing operator, an aggregation operator, a grouping operator, a join operator, a selection operator, or any combination thereof.

11. The system according to claim 1, wherein the XML file representing the query is generated based on a language integrated query (LINQ) language, a query in a .NET programming language other than LINQ, a complex event detection and response (CEDR) algebra query, or any combination thereof.

12. The system according to claim 1, wherein the system is integrated into an embedded dynamically linked library (DLL), an executable file, an operating system service, or a server farm.

13. The system according to claim 1, wherein at least one of the first input adapter, the second input adapter and the query engine are integrated into a complex event processing (CEP) system.

14. A system comprising: a memory; anda processor connected with the memory, the processor executing as a query engine configured to execute queries with respect to event objects to produce result objects, wherein a query is represented by an extensible markup language (XML) file that is based on a reusable XML query template that is bindable to a plurality of input adapters and a plurality of output adapters, the processor executing: binding the reusable XML query template to a first output adapter for a sink to output first results from execution of the query,binding the reusable XML query template to a second output adapter, different from the first output adapter, for another sink to output second results from execution of query, andexecuting the query to generate the first results and the second results.

15. The system according to claim 14, wherein the processor further executing binding the reusable XML query template to a first input adapter for a source to input data for execution of the query.

16. The system according to claim 14, wherein the processor further executing binding the reusable XML query template to a second input adapter, different from the first input adapter, for another source to input data for execution of the query.

17. The system according to claim 14, wherein the processor further executing outputting of at least one of the first results and the second results.

18. The system according to claim 14, wherein both the first input adapter and the second input adapter are used to produce identically typed event objects in accordance with a type specification of the reusable XML query template.

19. The system according to claim 14, wherein the reusable XML query template is integrated into a complex event processing (CEP) system.

20. A computer-implemented method comprising: binding a reusable XML query template to a first input adapter for a source and a first output adapter for a sink to produce a first result for a query;binding the reusable XML query template to a second input adapter for another source and a second output adapter for another sink to produce a second result for the query; andexecuting, using a query engine operating on a processing device, the query to produce the first result and the second result,wherein the query engine is configured to execute queries with respect to event objects to produce result objects, and wherein a query is represented by an extensible markup language (XML) file that is based on the reusable XML query template that is bindable to a plurality of input adapters and a plurality of output adapters.