Service oriented architecture automation by cab or taxi design pattern and method

• US 7,886,019 B2
• Filed: 08/31/2006
• Issued: 02/08/2011
• Est. Priority Date: 08/31/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Srinivasachar, Nagaraj C.
• Primary Examiner(s): Patel; Haresh N
• Application Number:
  US11/514,713
• Publication Number:
  US 20080075267A1
• Time in Patent Office: 1,622 Days
• Field of Search: 709/217, 709/224, 709/203, 707/693
• US Class Current: 709/217
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Abstract

Computer implemented method, system, and computer usable program code for handling service requests. A service request is received at one service provider of a plurality of service providers, each service provider adapted to receive service requests from service requesters and being in communication with middleware software and with one another. The received service request is sent to one service acceptor of a plurality of service acceptors, each also being in communication with the middleware software and with one another. If the one service acceptor is able to process the request, the one service acceptor processes the request and sends a response back to the one service provider and to each other of the plurality of service acceptors. If the one service acceptor is unable to process the request, the one service acceptor determines if another service acceptor is able to process the request and notifies the middleware software. A service acceptor that is able to process the request accepts and processes the request and provides a result. Overall Service Requestors, Service Providers, Service Stations (middleware) and Service Acceptors communicate among themselves and maintain respective logs to further make it the invention as an automated process.

Claims

1. A computer program product, comprising:

a non-transitory computer usable storage medium having computer usable program code encoded thereon configured for handling service requests in a data processing system, the computer program product comprising;

computer usable program code configured for receiving, at one service provider of a plurality of service providers, a service request from a service requestor, each of the plurality of service providers adapted to receive service requests from service requestors and being in communication with middleware software;

computer usable program code configured for sending the received service request to one service acceptor of a plurality of service acceptors, each of the plurality of service acceptors being in communication with the middleware software and in communication with one another; and

;

when said one service acceptor is able to process said request, said one service acceptor;

computer usable program code configured for processing the request; and

computer usable program code configured for sending a response back to said one service provider and to each other of said plurality of service acceptors,

wherein the response is stored in a log that is associated with each of said plurality of service acceptors; and

when said one service acceptor is unable to process the request;

computer usable program code configured for determining if another one of said plurality of service acceptor is able to process the request and further configured for determining if the log associated with the one service acceptor indicates that another one of said plurality of service acceptors has previously processed a corresponding request;

computer usable program code configured for notifying the middleware software of the determination;

and

wherein each of said service requestor, service provider and middleware software includes a log for storing information regarding service requests and responses to service requests; and

wherein when it is determined that another one of said plurality of service acceptors is not able to process the request, storing information regarding inability to process the request in logs of each of the middleware software, the service providers and the service requestors.

2. A system for handling service requests in a data processing system comprising:

a bus;

a communications unit connected to the bus;

a memory connected to the bus, wherein the memory includes a set of computer usable program code; and

a processor unit connected to the bus, wherein the processor unit executes the set of computer usable program code to perform the steps of;

receiving, at one service provider of a plurality of service providers, a service request from a service requestor, each of the plurality of service providers adapted to receive service requests from service requestors and being in communication with middleware software;

sending the received service request to one service acceptor of a plurality of service acceptors, each of the plurality of service acceptors being in communication with the middleware software and in communication with one another;

when said one service acceptor is able to process said request, said one service acceptor;

processing the request; and

sending a response back to said one service provider and to each other of said plurality of service acceptors; and

when said one service acceptor is unable to process the request;

a mechanism for determining if another one of said plurality of service acceptor is able to process the request; and

for notifying the middleware software of the determination; and

associating a log with each of said service acceptors for storing the response sent to each other of said plurality of service acceptors, and wherein the one service acceptor determines if another one of said plurality of service acceptors is able to process the request by determining if the log associated with the one service acceptor indicates that another one of said plurality of service acceptors has previously processed a corresponding request, and wherein the middleware software, upon being notified that another service acceptor is able to process the request, sends the request to the another service acceptor for processing.