Local Event Infrastructure

• US 20090063218A1
• Filed: 08/31/2007
• Published: 03/05/2009
• Est. Priority Date: 08/31/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Stuhrmann, Joerg, Schmidt, Patrick
• Granted Patent: US 8,966,500 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management

Abstract

A local event infrastructure and method for detecting events of a business application. An event manager is configured to detect one or more events of the business application based on a number of predetermined conditions. An event filter is configured to filter the one or more events detected by the event manager according to a relevance to an operation of a business application system that contains the business application.

Claims

1. A local event infrastructure for detecting events of a business application, the local event infrastructure comprising:

an event manager to detect one or more events of the business application based on a number of predetermined conditions; and

an event filter to filter the one or more events detected by the event manager according to a relevance to an operation of a business application system that contains the business application.

2. A local event infrastructure in accordance with claim 1, further comprising a change documents module that detects a state change in a process of the business application and triggers the event manager to detect the state change.

3. A local event infrastructure in accordance with claim 1, further comprising a status management module that detects a state change in a status of the business application and triggers the event manager to detect the state change.

4. A local event infrastructure in accordance with claim 1, further comprising an alert management module that detects an alert generated by the business application and triggers the event manager to detect the alert.

5. A local event infrastructure in accordance with claim 1, further comprising an event proxy that receives an indication of a relevant event detected by the event manager and filtered as relevant by the event filter, the event proxy translating the relevant event into a message.

6. A local event infrastructure in accordance with claim 5, wherein the event proxy includes an event handler to generate a workflow event message that is heterogeneously compliant with components of the business application system.

7. An application system comprising:

a business application configured to execute one or more business processes on a computing system;

a condition storage that contains one or more conditions that are imposed on the business application by a condition runtime engine;

an event manager to detect one or more events of the business application based the one or more conditions; and

an event filter to filter the one or more events detected by the event manager according to a relevance based on the one or more conditions.

8. An application system in accordance with claim 7, further comprising a change documents module that detects a state change in a process of the business application and triggers the event manager to detect the state change in the process.

9. An application system in accordance with claim 8, further comprising a status management module that detects a state change in a status of the business application and triggers the event manager to detect the state change in the status.

10. An application system in accordance with claim 9, further comprising an alert management module that detects an alert generated by the business application and triggers the event manager to detect the alert.

11. An application system in accordance with claim 7, further comprising an event dispatcher that interprets links between events of the business application and an event consumer, the links being represented in linkage tables stored in a linkage storage.

12. An application system in accordance with claim 7, further comprising a binding runtime engine to bind events to workflows of the business application.

13. An application system in accordance with claim 11, further comprising a message adapter configured to translate events from the event handler into a message for transmission to the event consumer.

14. An application system in accordance with claim 7, further comprising an alert adapter configured to translate events from the event handler into an alert for transmission to an alert server.

15. An application system in accordance with claim 13, wherein the event consumer includes a central event monitoring server hosting an alert server, the alert server responsive to alerts generated by an alert adapter that is configured to translate events from the event handler into an alert.

16. A method of monitoring activity of a business application, the method comprising:

defining an event signature for an event related to the business application based on one or more conditions;

storing the event signature in an enterprise services repository associated with an enterprise that executes the business application; and

generating an outbound message proxy for the event according to the defined event signature.

17. A method in accordance with claim 16, further comprising

detecting a local event within the business application;

comparing the local event with the event signature.

18. A method in accordance with claim 17, further comprising casting the local event as an outbound message proxy call if the local event corresponds with the event signature.

19. A method in accordance with claim 18, further comprising transmitting the outbound message proxy call by the outbound message proxy to an event consumer.

20. A method in accordance with claim 17, further comprising filtering each detected local event based on a relevance according to the one or more conditions.