Method and system for business-oriented web services management

• US 8,291,061 B2
• Filed: 10/08/2003
• Issued: 10/16/2012
• Est. Priority Date: 10/08/2003
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Casati, Fabio, Shan, Ming-Chien, Dayal, Umeshwar
• Primary Examiner(s): Neurauter, George C
• Application Number:
  US10/681,782
• Publication Number:
  US 20050080661A1
• Time in Patent Office: 3,296 Days
• Field of Search: 709/203, 709/224, 715/234, 719/330
• US Class Current: 709/224
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A method and system are disclosed for monitoring the performance of web-based services. The method comprises receiving a transaction from a client and routing the transaction to an appropriate web service for execution of the transaction. During execution of the transaction, performance data relating to the execution of the transaction is monitored and logged. The collected performance data is then queried based on pre-defined performance metrics and web service performance reports are generated. A system for the foregoing method is also disclosed.

Claims

1. A method for monitoring performance of web-based services, the method comprising:

receiving a transaction from a client;

routing the transaction to an appropriate web service for execution of the transaction;

executing the transaction;

monitoring and logging transaction execution performance data relating to receiving and executing the transaction;

reporting the performance data based on pre-defined performance metrics; and

correlating the performance data to composition metric information to determine the relationship between execution of instances of the execution of composition and instances of execution of conversation in terms of the performance of the web service;

wherein receiving the transaction includes tracking, via a Simple Object Access Protocol (“

SOAP”

) tracker, of information relating to the transaction;

wherein receiving the transaction includes communicating, via the SOAP tracker, the information to a web services manager (WSM) for performance analysis.

2. The method of claim 1, wherein the routing step is performed by a SOAP router or application server.

3. The method of claim 1, wherein the monitoring and logging step includes the use of a service registry and a service composition engine to record and store data in service execution logs relating to instances of conversation transaction or composition transaction.

4. The method of claim 1, wherein the reporting step includes extracting data from a service registry or the service execution logs for use by the WSM to generate performance reports.

5. The method of claim 1, wherein the reporting step is performed by the WSM.

6. The method of claim 5, wherein the WSM further includes a WSM definer, a metric schema and a WSM engine to generate performance reports.

7. The method of claim 6, wherein the WSM engine receives data from the SOAP tracker and data relating to conversation definitions, composition service definitions and related execution data.

8. The method of claim 5, wherein the WSM engine communicates with a web framework and related application servers to provide performance reports to business or IT personnel.

9. A system, comprising:

one or more processors;

memory coupled to the one or more processors, the memory storing executable instructions that when executed by the one or more processors, cause the one or more processors to;

track information relating to a transaction communicated from a client;

route the transaction to an appropriate web service for execution of the transaction;

collect performance data relating to the communication of the transaction from the client and the execution of the transaction by the web service;

extract the performance data and generate reports relating to the performance of the web services based on pre-defined performance metrics; and

correlate the performance data to composition metric information to determine the relationship between execution of instances of the execution of composition and instances of execution of conversation in terms of the performance of the web service;

wherein a Simple Object Access Protocol (“

SOAP”

) tracker comprises a processor, out of the one or more processors, caused to track the information relating to the transaction communicated from the client.

10. A system as recited in claim 9, wherein the one or more processors receive tracking information relating to the transaction and communicates the information to a web services manager (WSM).

11. A system as recited in claim 9, further comprising a SOAP router or application server.

12. A system as recited in claim 9, wherein the one or more processors memorialize web service performance data in service execution logs.

13. A system as recited in claim 12, wherein the web service performance data in the service execution logs comprises data relating to instances of conversation transaction or composition transaction.

14. A system as recited in claim 9, further comprising a WSM.

15. A system as recited in claim 9, wherein the one or more processors receive data from a service registry or service execution logs and transmit the data to the WSM.

16. A system as recited in claim 15, wherein the WSM comprises a WSM definer, a metric schema and a WSM engine.

17. A system as recited in claim 16, wherein the WSM engine receives data from the SOAP tracker and data relating to conversation definitions, composition service definitions and related execution data.

18. A system as recited in claim 16, wherein the WSM engine communicates with a web framework and related application servers.

19. A method for creating custom metrics for monitoring performance of web-based services, the method comprising:

providing a metrics construction model;

providing a metrics library containing metrics definitions;

selecting at least one built-in metric function from the metrics library;

customizing the selected built-in metric function based on the metrics construction model by selecting parameters for the built-in metric function, wherein the metrics library is included in a web services manager (“

WSM”

); and

correlating the selected built-in metric function to conversation metric information to determine the relationship between execution of instances of the execution of composition and instances of execution of conversation in terms of the performance of the web-based service.

20. The method of claim 19, wherein the metrics construction model includes an algorithm for assembling the selected at least one metric function and the selected parameters into a custom metric.

21. A method for correlating conversation metrics to composition metrics to analyze performance of web-based services, the method comprising:

collecting information relating to at least one metric associated with a conversation;

collecting information relating to at least one metric associated with a composition; and

correlating the collected conversation metric information to the collected composition metric information to determine the relationship between execution of instances of the execution of the composition and instances of execution of the conversation in terms of the performance of the web-based service.

22. The method of claim 21, wherein conversation metric information is obtained from a service registry;

and wherein composition metric information is obtained from a service composition engine.

23. A computer-readable non-transitory storage medium for storing an executable set of software instructions, wherein the instructions are configured for managing business-oriented web services by a method comprising:

transmitting a transaction from a client to an appropriate web service for execution of the transaction;

executing the transaction;

monitoring and logging, via a Simple Object Access Protocol (“

SOAP”

) tracker, transaction execution performance data relating to transmitting and executing the transaction to a service execution log;

extracting the performance data from the service execution log;

parsing the performance data into a format readable by a web services manager;

correlating the performance data to composition metric information to determine the relationship between execution of instances of the execution of composition and instances of execution of conversation in terms of the performance of the web service; and

compiling the performance data into a report.

24. The computer-readable non-transitory storage medium of claim 23, wherein the compiling step is coordinated by a web services manager.