Web Service Information Management in Service-Oriented Architecture Applications

• US 20070143474A1
• Filed: 09/26/2006
• Published: 06/21/2007
• Est. Priority Date: 12/15/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Sheng, Mao Xin, Yi, Li
• Granted Patent: US 8,375,122 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Web server information management in a service-oriented architecture application comprises intercepting a service request message issued by a Web service requester for a Web service in response to executing the service-oriented architecture application on the Web service requester side, adding a tracing header in the service request message for requesting the detailed runtime information of the Web service and sending the message to the Web service provider side, intercepting the service request message coming from the Web service requester on the Web service provider side, tracing detailed runtime information based on the tracing header for requesting the detailed runtime information in the message during the execution of the Web service with respect of the service request message, and adding an acknowledgement tracing header containing the traced detailed runtime information into the response message to be returned to the Web service requester by the Web service provider and returning the message to the Web service requester.

Claims

1. A method for Web service information management in a service-oriented architecture application, comprising:

intercepting a service request message issued by a Web service requester for a Web service in response to executing said service-oriented architecture application on the Web service requester side;

adding a tracing header in the service request message for requesting the detailed runtime information of the Web service and sending the message to the Web service provider side;

intercepting the service request message coming from the Web service requester on the Web service provider side;

tracing detailed runtime information based on the tracing header for requesting the detailed runtime information in the message during the execution of the Web service with respect of the service request message; and

adding an acknowledgement tracing header containing the traced detailed runtime information into the response message to be returned to the Web service requester by the Web service provider and returning the message to the Web service requester.

2. The method as claimed in claim 1, further comprising:

said Web service requester acquires the detailed runtime information from the acknowledgment tracing header of the received response message coming from said Web service provider and transfers the acquired detailed runtime information to a management server.

3. The method as claimed in claim 2, further comprising:

setting message intercepting rules on said Web service requester side; and

based on the message intercepting rules, executing the step of intercepting the service request message on the Web service requester side.

4. The method as claim in claim 1, further comprising:

setting message intercepting rules on said Web service provider side; and

based on the message intercepting rules and the security and management rules on the Web service provider side, executing the step of intercepting the service request message on the Web service provider side, and the step of adding an acknowledgement tracing header containing the detailed runtime information in the returned response message.

5. The method as claimed in claim 1, further comprising:

defining pre-condition and post-condition checking logics on the Web service requester side, so as to trigger specific management events based on the message content and service context.

6. The method as claimed in claim 1, wherein the detailed runtime information tracing header in said service request message comprises a context identifier and an operation identifier for identifying this service invocation.

7. The method as claimed in claim 6, wherein the detailed runtime information tracing header in said service request message further comprises a security credential used in the authentication of said Web service requester by said Web service provider.

8. The method as claimed in claim 6, wherein said operation identifier is a globally unique identifier produced according to the operation related to said service request message, while said context identifier is an existing context identifier in case that there is the context on said Web service requester side, and a newly produced globally unique identifier in the case that there is no existing context identifier on the Web service requester side.

9. The method as claimed in claim 8, further comprising:

when receiving a service request message containing a detailed runtime information tracing header, said Web service provider takes the operation identifier in the tracing header as its context identifier; and

during the execution, the Web service invokes another Web service with the contest identifier and a produced corresponding operation identifier, and requests the detailed runtime information of the other Web service in the service request message in the form of a detailed runtime information tracing header, so as to realize the recursive collection of the Web service information.

10. The method as claimed in claim 6, wherein the detailed runtime information in the acknowledgement tracing header of said response message comprises the context identifier and the operation identifier corresponding to the Web service request message.

11. The method as claim in claim 10, wherein said detailed runtime information in the acknowledgment tracing header of said response message further comprises at least one of following:

the invocation topology of said Web service, the management information of said Web service and the method for retrieving the management information of said Web service.

12. The method as claimed in claim 1, wherein the tracing header in said service request message and the acknowledgement tracing header in said response message take the form of a SOAP header.

13. A message interceptor on the Web service requester side, comprising:

a message intercepting module for intercepting the messages communicated between the Web service requester and the Web service provider during a service-oriented architecture application is executed;

a message analysis module for analyzing messages intercepted by said message intercepting module to identify the service request messages issued by the Web service requester and the response messages containing tracing headers provided by the Web service provider;

a tracing header adding module for adding a tracing header in a service request message sent by the Web service requester for requesting the detailed runtime information of the Web service, and sending the message to the Web service provider through the message intercepting module; and

a management information acquiring module for acquiring the detailed runtime information based on an acknowledgment tracing header in the response message coming from the Web service provider, and transferring the acquired detailed runtime information of the Web service to a management server.

14. A message interceptor on the Web service provider side, comprising:

a message intercepting module for intercepting the messages sent to the Web service provider side;

a message analysis module for analyzing the messages intercepted by said message intercepting module to identify service request messages issued by the Web service requester, which contain tracing headers for requesting the detailed runtime information of the Web service, and response messages returned by the Web service;

a detailed runtime information tracing module for tracing the detailed runtime information during the execution of the Web service in respect of a service request message when said message analysis module has identified the service request message containing a tracing header; and

an acknowledgment tracing header adding module for adding an acknowledgment tracing header containing the traced detailed runtime information into the response message when said message analysis module has identified the response massage returned by the Web service, and sending the message to the Web service requester through said message intercepting module.

15. The message interceptor as claimed in claim 14, wherein the detailed runtime information tracing header in said service request message comprises a context identifier and an operation identifier for identifying this service invocation.

16. The message interceptor as claimed in claim 15, wherein the detailed runtime information tracing header in said service request message further comprises a security credential used in the authentication of said Web service requester by said Web service provider.

17. The message interceptor as claimed in claim 15, wherein said message analysis module takes the operation identifier contained in the tracing header of said service request message as the context identifier on the Web service provider side, and said message analysis module further identifies, among the messages intercepted by said message interceptor module, the service request messages sent to other Web services by the Web service during the execution and the response messages returned by the other Web services.

18. The message interceptor as claimed in claim 17, further comprising:

a tracing header adding module for adding a tracing header containing said context identifier and a newly produced corresponding operation identifier into the service request messages sent to other Web services and identified by said message analysis module, and sending the service request messages to the other Web services through said message interceptor module.

19. The message interceptor as claimed in claim 17, wherein said detailed runtime information tracing module acquires and records the detailed runtime information of the other Web services from the response messages returned by the other Web services and identified by said message analysis module.

20. A computer program product for Web service information management in a service-oriented architecture application, the computer program product comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

a computer usable program code configured to intercept a service request message issued by a Web service requester for a Web service in response to executing said service-oriented architecture application on the Web service requester side;

computer usable program code configured to add a tracing header in the service request message for requesting the detailed runtime information of the Web service and sending the message to the Web service provider side;

computer usable program code configured to intercept the service request message coming from the Web service requester on the Web service provider side;

computer usable program code configured to trace detailed runtime information based on the tracing header for requesting the detailed runtime information in the message during the execution of the Web service with respect of the service request message; and

computer usable program code configured to add an acknowledgement tracing header containing the traced detailed runtime information into the response message to be returned to the Web service requester by the Web service provider and returning the message to the web service requester.