DISTRIBUTED REQUEST AND RESPONSE QUEUES FOR SERVICE PROCESSOR

• US 20090164571A1
• Filed: 03/02/2009
• Published: 06/25/2009
• Est. Priority Date: 05/02/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Upton, Mitch, Golding, Christa, Potter, Tim
• Granted Patent: US 7,953,787 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Claims

1. A system comprising:

a distributed input queue to receive and store messages, the distributed input queue including multiple physical queues;

a first service processor to pull a first message of the messages from the distributed input queue;

a second service processor to pull a second message of the messages from the distributed input queue; and

a distributed output queue to receive and store messages from the first and second service processor, the distributed output queue including more than one physical queue.

2. A system according to claim 1, wherein the first service processor invokes a service for the service request, the service processor further receiving a service response for the service request from the invoked service.

3. A system according to claim 2, wherein the distributed output queue receives the service response from the first service processor and stores the service response.

4. A system according to claim 2, further comprising:

an enterprise information system containing the service invoked by the first service processor.

5. A system according to claim 1, wherein the first service processor is packaged as a message-driven Enterprise JAVABean.

6. A system according to claim 3, further comprising:

an application view client for sending the service request to the distributed input queue and retrieving the service response from the distributed output queue on behalf of a client application.

7. A system according to claim 6, wherein the application view client generates failure recovery semantics for the client application.

8. A system according to claim 6, wherein the distributed output queue is adapted to store the service response until the response is retrieved by the application view client.

9. A system according to claim 6, wherein the application view is adapted to determine whether any service responses are waiting in the distributed output queue for the client application.

10. A system according to claim 6, further comprising:

a client identifier for identifying the client application, the client identifier used to process the service request and service response for the client application.

11. A system for according to claim 6, wherein the application view client passes the service request to the distributed input queue in a request document.

12. A system according to claim 1, wherein the first and second service processors are deployed on different nodes in a cluster.

13. A system comprising:

multiple service processors to operate on messages; and

a distributed queue interoperating with the multiple service processors to store the messages, the distributed queue including multiple physical queues, wherein if one of the multiple service processors is unavailable, another of the multiple service processors will handle the messages and if one of the physical queues is unavailable, another one of the physical queues will store the messages.

14. The system of claim 13, wherein the distributed queue is a distributed output queue.

15. The system of claim 14, further comprising a distributed input queue.

16. The system of claim 13, wherein the multiple service processors invoke a service.

17. A system comprising:

a distributed queue to store messages, the distributed queue including multiple physical queues; and

multiple service processors to operate on the messages, wherein if one of the multiple service processors is unavailable, another of the multiple service processors will handle the messages and if one of the physical queues is unavailable, another one of the physical queues will store the messages.

18. The system of claim 17, wherein the distributed queue is a distributed input queue.

19. The system of claim 17, further comprising a distributed output queue.

20. The system of claim 17, wherein the service processors invoke a service.