Apparatus and methods for managing messages sent between services

• US 9,037,726 B2
• Filed: 07/05/2007
• Issued: 05/19/2015
• Est. Priority Date: 03/30/2001
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Panec, Peter A., Douglas, Jason
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): DESAI, MARGISHI V
• Application Number:
  US11/773,931
• Publication Number:
  US 20080016242A1
• Time in Patent Office: 2,875 Days
• Field of Search: 370/392, 370/352, 709/227
• US Class Current: 709/227
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 45/44 Distributed routing
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04M 2203/5063 Centrally initiated conference, i.e. Conference server dials participants computer conference organisation arrangements H04L12/1818
• CPC Class Codes: H04Q 11/0407 using a stored programme control

Abstract

Disclosed are methods and apparatus for managing services within a computer network. In one embodiment, a message interchange network for exchanging application-level messages between services, which are located outside the message interchange network, is provided. At the message interchange network, a plurality of application-level messages, which each specify which one or more receiving services are to receive the each application-level message, are received. Each received application-level message is forward towards the one or more receiving services. Correlation information regarding each application-level message that is received into message interchange network is retained. The application-level messages are sent between pairs of the services, and the retained correlation information for each application-level message pertains to each application-level message and any other application-level messages related to the each application-level message. A query can then be received, at the message interchange network from a first service, to search the retained correlation information for specific one or more portions of the retained correlation information. A response to the query, which includes the specific one or more portions of the retained correlation information, is sent to the first service.

Claims

1. A method for correlating services within a computer network, the method comprising:

providing, at a message interchange network, a registry of a plurality of services implemented at least in-part by applications located outside of the message interchange network, each service being identified as accessible according to one or more properties associated with the service, the one or more properties being stored as data objects in at least one database;

receiving and sending, at the message interchange network, application-level messages between or among the services, wherein;

a first plurality of the application-level messages belong to a first one of a plurality of calls, each call being between a pair of the services, at least a portion of the calls being related to each other by invoking or causing invocation of a same service, and

the related calls belong to a first one of a plurality of sessions;

retaining correlation information regarding each application-level message received at the message interchange network, each call, and each session, the retained correlation information stored as one or more data objects in the at least one database, the retained correlation information including an identifier of the application-level message, a call identifier of the call associated with the application-level message, and a session identifier of the session associated with the call;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message, call, or session; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

2. The method as recited in claim 1, wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message.

3. The method as recited in claim 2, wherein the retained correlation information for each application-level message further includes an indication as to whether each application-level message has completed transmission.

4. The method as recited in claim 1, a session identifier for each session uniquely identifying each session, and wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific session, such one or more portions including an indication as to whether the specific session is complete and a reason for the specific session not being complete when the specific session fails to complete.

5. The method as recited in claim 1, wherein the retained correlation information for a particular call comprises an indication as to whether the particular call has completed and a reason for the particular call not completing when the call has not completed, and wherein the retained correlation information for a particular session comprises an indication as to whether the particular session has completed and a reason for the particular session not completing when the session has not completed.

6. The method as recited in claim 5, wherein the retained correlation information for the particular session further comprises a route for the application-level messages of the particular session and an identity and status of each service within the route for the application-level messages of the particular session.

7. A computer system operable to correlate services within a computer network, the computer system comprising:

one or more processors;

one or more memory devices, wherein at least one of the processors and memory devices are adapted for;

providing, at a message interchange network, a registry of a plurality of services implemented at least in-part by applications located outside of the message interchange network, each service being identified as accessible according to one or more properties associated with the service, the one or more properties being stored as data objects in at least one database;

receiving and sending, at the message network, application-level messages between or among the services, wherein;

a first plurality of the application-level messages belong to a first one of a plurality of calls, each call being between a pair of the services, at least a portion of the calls being related to each other by invoking or causing invocation of a same service, and

the related calls belong to a first one of a plurality of sessions;

retaining correlation information regarding each application-level message received at the message interchange network, each call, and each session, the retained correlation information stored as one or more data objects in the at least one database, the retained correlation information including an identifier of the application-level message, a call identifier of the call associated with the application-level message, and a session identifier of the session associated with the call;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message, call, or session; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

8. The computer system as recited in claim 7, wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message.

9. The computer system as recited in claim 8, wherein the retained correlation information for each application-level message further includes an indication as to whether each application-level message has completed transmission.

10. The computer system as recited in claim 7, a session identifier for each session uniquely identifying each session, and wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific session, such one or more portions including an indication as to whether the specific session is complete and a reason for the specific session not being complete when the specific session fails to complete.

11. The computer system as recited in claim 7, wherein the retained correlation information for a particular call comprises an indication as to whether the particular call has completed and a reason for the particular call not completing when the call has not completed, and wherein the retained correlation information for a particular session comprises an indication as to whether the particular session has completed and a reason for the particular session not completing when the session has not completed.

12. The computer system as recited in claim 11, wherein the retained correlation information for the particular session further comprises a route for the application-level messages of the particular session and an identity and status of each service within the route for the application-level messages of the particular session.

13. A computer program product for correlating services within a computer network, the computer program product comprising program code to be executed by at least one processor when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configured to cause:

providing, at a message interchange network, a registry of a plurality of services implemented at least in-part by applications located outside of the message interchange network, each service being identified as accessible according to one or more properties associated with the service, the one or more properties being stored as data objects in at least one database;

receiving and sending, at the message network, application-level messages between or among the services, wherein;

a first plurality of the application-level messages belong to a first one of a plurality of calls, each call being between a pair of the services, at least a portion of the calls being related to each other by invoking or causing invocation of a same service, and

the related calls belong to a first one of a plurality of sessions;

retaining correlation information regarding each application-level message received at the message interchange network, each call, and each session, the retained correlation information stored as one or more data objects in the at least one database, the retained correlation information including an identifier of the application-level message, a call identifier of the call associated with the application-level message, and a session identifier of the session associated with the call;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message, call, or session; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

14. The computer program product as recited in claim 13, wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific application-level message.

15. The computer program product as recited in claim 14, wherein the retained correlation information for each application-level message further includes an indication as to whether each application-level message has completed transmission.

16. The computer program product as recited in claim 13, a session identifier for each session uniquely identifying each session, and wherein the query is to search the retained correlation information for a specific one or more portions of the retained correlation information for a specific session, such one or more portions including an indication as to whether the specific session is complete and a reason for the specific session not being complete when the specific session fails to complete.

17. The computer program product as recited in claim 13, wherein the retained correlation information for a particular call comprises an indication as to whether the particular call has completed and a reason for the particular call not completing when the call has not completed, and wherein the retained correlation information for a particular session comprises an indication as to whether the particular session has completed and a reason for the particular session not completing when the session has not completed.

18. The computer program product as recited in claim 17, wherein the retained correlation information for the particular session further comprises a route for the application-level messages of the particular session and an identity and status of each service within the route for the application-level messages of the particular session.