Local Event Infrastructure

1. A local event infrastructure for detecting events of a business application, the local event infrastructure comprising: an event manager, implemented by one or more processors, to detect one or more events of the business application based on a number of predetermined conditions associated with a state change of one of a plurality of business objects that comprise a workflow of the business application; an event filter, implemented by one or more processors, to filter the one or more events detected by the event manager according to a relevance of one or more of the number of predetermined conditions to an operation of a business application system that contains the business application; an event proxy, implemented by one or more processors, that receives an indication of a relevant event after the relevant event is detected by the event manager and filtered as relevant by the event filter, the event proxy casting the relevant event into an outbound proxy call configured as a message for a monitoring process instance of a business application monitoring system; and an event dispatcher, implemented by one or more processors, 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.

2. A local event infrastructure in accordance with claim 1 , further comprising a change documents module, implemented by one or more processors, 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, implemented by one or more processors, 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, implemented by one or more processors, 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 , 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.

6. 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, the one or more conditions being associated with a state change of one of a plurality of business objects that comprise a workflow of the business application; an event manager, implemented by one or more processors, to detect one or more events of the business application based the one or more conditions; an event filter, implemented by one or more processors, to filter the one or more events detected by the event manager according to a relevance of the one or more conditions to an operation of a business application system that contains the business application; an event dispatcher, implemented by one or more processors, 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; and an alert adapter, implemented by one or more processors, configured to cast events from the event handler into an alert for transmission to an alert server after the event is detected by the event manager and filtered as relevant by the event filter, the alert for transmission including an outbound proxy call configured as a message for a monitoring process instance.

7. An application system in accordance with claim 6 , further comprising a change documents module, implemented by one or more processors, 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.

8. An application system in accordance with claim 7 , further comprising a status management module, implemented by one or more processors, 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.

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

10. An application system in accordance with claim 6 , further comprising a binding runtime engine, implemented by one or more processors, to bind events to workflows of the business application.

11. An application system in accordance with claim 6 , further comprising a message adapter, implemented by one or more processors, configured to translate events from the event handler into a message for transmission to the event consumer.

12. An application system in accordance with claim 11 , wherein the event handler 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.

13. 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 associated with a state change of one of a plurality of business objects that comprise a workflow of the business application; storing the event signature in an enterprise services repository associated with an enterprise that executes the business application; detecting a local event within the business application; comparing the local event with the event signature; filtering the detected local event based on a relevance according to the one or more conditions; interpreting links between events of the business application and an event consumer, the links being represented in linkage tables stored in a linkage storage; and generating, by the enterprise services repository, an outbound message proxy for the event according to the defined event signature, after the event is detected and filtered as relevant, the outbound message proxy casting the event as an outbound proxy call configured as a message for a monitoring process instance of a business application monitoring system.

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

15. A method in accordance with claim 14 , further comprising transmitting the outbound message proxy call by the outbound message proxy to the event consumer associated with the business application monitoring system.