Embedded business process monitoring

1 . A method comprising:

hosting a business process associated with a business application, the business process including a business object and one or more process agents adapted to execute the business process;

modeling the business process using a modeled business process, the business application configured to perform the modeled business process; and

monitoring configuration data of the modeled business process and that of the business process associated with the business application for any inconsistency therebetween.

2 . A method comprising:

obtaining configuration data associated with an actual business process on a predetermined schedule without user intervention;

monitoring a modeled business process simulating the actual business process, the modeled business process having one or more process agents associated with a business object;

determining whether the configuration data has been modified based on the modeled business process; and

detecting a potential issue associated with the modified configuration data.

3 . The method of claim 2 , where determining whether the configuration data has been modified includes:

monitoring data or messages transmitted and received between process agents, or between the business object and one or more of the process agents; and

detecting data or messages indicative of inconsistency between the modeled business process and the actual business process based on the monitored data or messages.

4 . The method of claim 3 , where detecting a potential issue includes generating analysis information in response to the detected data or messages.

5 . The method of claim 2 , where monitoring the modeled business process includes monitoring errors or warnings created during processing of the business object.

6 . The method of claim 2 , where monitoring the modeled business process includes monitoring status of the business object or status of at least one process agent.

7 . The method of claim 2 , where monitoring the modeled business process includes periodically or continuously monitoring the modeled business process to detect a new configuration adopted by the actual business process.

8 . The method of claim 2 , where monitoring the modeled business process includes collecting information exchanged between two or more process agents, or between the business object and at least one of the process agents.

9 . The method of claim 2 , where monitoring the modeled business process includes retrieving information associated with how diagnostic messages or data exchanged between two or more process agents, or between the business object and at least one of the process agents are linked to the modeled business process.

10 . The method of claim 2 , where monitoring the modeled business process includes:

monitoring events in the modeled business process;

detecting predetermined business conditions and changes in the modeled business process; and

alerting a service provider to draw attention to the business object or the actual business process upon detection of the predetermined business conditions or changes.

11 . The method of claim 2 , further comprising presenting the detected potential issue associated with the modified configuration data to a user in real time.

12 . A method comprising:

obtaining configuration data associated with an actual business process;

monitoring a modeled business process simulating the actual business process on a predetermined schedule without user intervention, the modeled business process having one or more process agents associated with a business object;

collecting diagnostic data exchanged between process agents or between at least one of process agents and the business object to detect an event associated with the actual business process; and

evaluating whether the detected event is critical.

13 . The method of claim 12 , where evaluating whether the detected event is critical includes classifying the event as either an incident or an administrative task.

14 . The method of claim 13 , where classifying the event includes:

retrieving additional information about the event from the process agents;

searching a task catalog including predefined tasks to locate a task for solving the event;

classifying the event as the administrative task if the task is located in the task catalog; and

classifying the event as the incident if the task is not listed in the task catalog.

15 . The method of claim 14 , further comprising automatically generating a service request containing the diagnostic data associated with the detected event if the detected event is classified as an incident.

16 . The method of claim 14 , further comprising:

implementing the located task for solving the event if the detected event is classified as an administrative task; and

verifying successful implementation of the task by tracking performance of the actual business process.

17 . The method of claim 12 , further comprising displaying the collected diagnostic data in real time to a user.

18 . The method of claim 12 , where monitoring a modeled business process includes monitoring changes to configuration of the actual business process.

19 . A method comprising:

hosting an actual business process on a client;

modeling the actual business process running on the client;

monitoring the modeled business process to detect an event indicating a change in an operational parameter of the actual business process or the modeled business process without user intervention; and

automatically routing the event to a service provider if a change is made to the operational parameter of the actual business process or the modeled business process.

20 . The method of claim 19 , further comprising:

evaluating whether the routed event is critical;

classifying the routed event as either an incident or an administrative task;

searching a task catalog including predefined tasks to locate a task for solving the event;

classifying the routed event as the administrative task if a task for solving the routed event is located in a task catalog containing predefined tasks; and

classifying the routed event as the incident if the task is not listed in the task catalog.