System and method for managing conversations

• US 20040230650A1
• Filed: 05/14/2003
• Published: 11/18/2004
• Est. Priority Date: 05/14/2003
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Murray, Bryan P., Catania, Nicolas, Vambenepe, Guillaume N., Pourheidari, M. Homayoun
• Granted Patent: US 7,945,860 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system for managing a conversation includes one or more interfaces configured to provide management information about the conversation to a manager. The interface can be configured to provide information regarding a resource such as a Web service that contains the conversation. Information regarding the conversation that may be made available to the manager includes the number of failed messages processed by the conversation; the number of successful messages processed by the conversation; the total number of messages processed by the conversation; the number of other resources participating in the conversation; the identity of other resources participating in the conversation; an identifier of the conversation; the last message received; the last fault message received; and an identifier of the resource that contains the conversation.

Claims

1. A system for managing a conversation in a Web service, comprising:

a computer processor;

a conversation managed object executable on the computer processor, wherein;

the conversation managed object includes at least one interface configured to provide management information about the conversation to at least one manager; and

the at least one interface is configured to provide information regarding the Web service that contains the conversation.

2. The system of claim 1, wherein the at least one interface is configured to provide a list of other managed objects participating in the conversation.

3. The system of claim 1, wherein the at least one interface is configured to provide an identifier associated with the conversation.

4. The system of claim 1, wherein the at least one interface is configured to provide information regarding the last message received by the conversation.

5. The system of claim 1, wherein the conversation is further configured to receive messages, and the at least one interface is configured to provide information regarding the last fault message returned from the conversation.

6. The system of claim 1, wherein the at least one interface is configured to provide information regarding the number of other Web service managed objects involved in the conversation.

7. The system of claim 1, wherein the conversation is further configured to receive messages, and the at least one interface is configured to provide information regarding the number of successful messages processed by the conversation.

8. The system of claim 7, wherein the conversation is further configured to receive messages, and the at least one interface is configured to provide information regarding the number of failed messages processed by the conversation.

9. The system of claim 8, wherein the at least one interface is configured to provide information regarding the total number of messages for the conversation.

10. The system of claim 1, wherein the at least one interface is configured to allow the at least one manager to end the conversation.

11. The system of claim 1, wherein the at least one interface is configured to provide information regarding the total number of failed messages processed by the conversation.

12. The system of claim 1, wherein the conversation managed object is configured to notify the at least one manager when an incorrect message is received.

13. The system of claim 1, wherein the conversation managed object is configured to notify the at least one manager when at least one of:

a message could not be sent to a participant in the conversation, and an expected response was not received.

14. The system of claim 1, wherein the conversation managed object is configured to notify the at least one manager when one of the participants in the conversation sent an unexpected fault message.

15. The system of claim 1, wherein the conversation managed object is configured to notify the at least one manager when a fault happened while processing a message for the conversation.

16. The system of claim 8, wherein the messages are exchanged via a simple object access protocol (SOAP).

17. The system of claim 1, further comprising an interface description that describes the at least one conversation interface to the at least one manager.

18. The system of claim 17, wherein the interface description is formatted according to a Web services description language (WSDL).

19. A system capable of monitoring messages between a first resource and a second resource, comprising:

a computer processor configured to communicate with the first resource, wherein the computer processor includes executable instructions operable to;

discover whether a conversation has been established between the first resource and the second resource;

end the conversation; and

request information regarding the conversation including;

at least one of;

the number of failed messages;

the number of successful messages;

the total number of messages;

the last message received by the first resource;

the last fault message received by the first resource; and

at least one of;

the identity of resources participating in the conversation;

the number of resources participating in the conversation;

an identifier of the conversation; and

an identifier of the resource that contains the conversation interface.

20. The system of claim 19, wherein the messages are exchanged via the simple object access protocol (SOAP).

21. The system of claim 19, wherein a manager discovers whether the conversation has been established between the first resource and the second resource through an interface, wherein the interface comprises:

a managed object interface that includes information regarding the first resource; and

a conversation interface that includes information regarding the messages exchanged with the first managed object.

22. The system of claim 21, wherein the first resource is associated with at least one of the group of:

a first interface description that describes the managed object interface to a manager; and

a second interface description that describes the conversation interface to a manager.

23. The system of claim 22, wherein descriptions of at least one of:

the first interface description and the second interface description are formatted according to a Web services description language (WSDL).

24. A computer program product comprising:

a conversation interface;

a managed object interface associated with the conversation interface, wherein the conversation interface includes information for monitoring messages in a conversation, including;

at least one of;

the number of failed messages;

the number of successful messages;

the total number of messages;

the last message received by a resource;

the last fault message received by the resource; and

at least one of;

the identity of resources participating in the conversation;

the number of resources participating in the conversation;

an identifier of the conversation; and

an identifier of the resource that contains the conversation interface.

25. The computer program product of claim 24, wherein the conversation interface further includes information regarding at least one of the following events:

receipt of an incorrect message;

an expected response was never received;

a participant in the conversation is not responding;

a participant in the conversation sent a fault message; and

a fault occurred while processing a message for the managed service.

26. The computer program product of claim 25, wherein the messages are exchanged via the simple object access protocol (SOAP).

27. The computer program product of claim 26, further comprising a conversation interface description that describes the conversation interface to a manager.

28. The computer program product of claim 27, further comprising:

an extension to the conversation object interface to expose additional conversation management capabilities to a manager.

29. The computer program product of claim 28, wherein the conversation interface description is formatted according to a Web services description language (WSDL).

30. The computer program product of claim 29, wherein the extension to the conversation interface is implemented by including another port type in another interface description.

31. The computer program product of claim 30, wherein the extension to the conversation interface exposes management information regarding a business transaction.

32. A method for managing a conversation for a Web service, comprising:

creating a conversation object representing the conversation;

exposing management capabilities for the conversation via a description of a plurality of interfaces; and

allowing a manager to subscribe with the conversation object to receive notification of events regarding the conversation.

33. The method of claim 32 further comprising:

storing information regarding the conversation including;

at least one of;

the number of failed messages;

the number of successful messages;

the total number of messages received;

at least one of;

the identity of other resources participating in the conversation;

the number of other resources participating in the conversation;

an identifier of the conversation; and

at least one of;

the last message received;

the last fault message received; and

an identifier of the Web service that contains the conversation.

34. An apparatus for managing a conversation for a Web service, comprising:

object means for representing the conversation;

description means for exposing management capabilities for the conversations; and

subscription means for allowing a manager to subscribe to receive notification of events regarding the conversation.

35. The apparatus of claim 34 further comprising:

means for providing information regarding the conversation including the messages processed; and

other resources participating in the conversation.