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

• US 20080075267A1
• Filed: 08/31/2006
• Published: 03/27/2008
• Est. Priority Date: 08/31/2006
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Srinivasachar, Nagaraj C.
• Granted Patent: US 7,886,019 B2
• Time in Patent Office: Days
• US Class Current: 379/265.01
• 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 implemented method for handling service requests in a data processing system, the computer implemented method comprising:

receiving, at one service provider of a plurality of service providers, a service request from a service requester, each of the plurality of service providers adapted to receive service requests from service requesters 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; and

;

if 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

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

determining if another one of said plurality of service acceptors is able to process the request; and

notifying the middleware software of the determination.

2. The computer implemented method according to claim 1, and further comprising:

storing the response sent to each other of said plurality of applications in a log that is associated with each of said service acceptors; and

wherein determining if another one of said plurality of service acceptors is able to process the request comprises;

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.

3. The computer implemented method according to claim 2, wherein notifying the middleware software of the determination comprises notifying the middleware software that another service acceptor is able to process the request, and further comprising:

the middleware software sending the request to the another service acceptor for processing.

4. The computer implemented method according to claim 1, wherein said plurality of service providers are in communication with one another, and further comprising:

said plurality of service providers communicating with one another.

5. The computer implemented method according to claim 1, and further comprising a plurality of service requesters, each of said plurality of service requesters in communication with one another, and further comprising:

said plurality of service requesters communicating with one another.

6. The computer implemented method according to claim 1, wherein sending the received service request to one service acceptor of a plurality of service acceptors comprises:

sending the received service request via a queuing mechanism in the middleware software.

7. The computer implemented method according to claim 2, wherein each of said service requester, service provider and middleware software includes a log for storing information regarding service requests and responses to service requests.

8. The computer implemented method according to claim 7, wherein if it is determined that another one of said plurality of service acceptor is not able to process the request, information regarding inability to process the request is stored in logs of each of the middleware software, the service providers and the service requesters.

9. The computer implemented method according to claim 1, wherein the service request is sent to a plurality of service acceptors for processing the request.

10. The computer implemented method according to claim 1, wherein the data processing system is implemented in a Service-Oriented Architecture.

11. A computer program product, comprising:

a computer usable medium having computer usable program code 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 requester, each of the plurality of service providers adapted to receive service requests from service requesters 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

;

if 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; and

if 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

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

12. The computer program product according to claim 11, and further comprising:

computer usable program code configured for storing the response sent to each other of said plurality of service acceptors in a log that is associated with each of said service acceptors; and

wherein the computer usable program code configured for determining if another one of said plurality of service acceptors is able to process the request comprises;

computer usable program code 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.

13. The computer program product according to claim 12, wherein the computer usable program code configured for notifying the middleware software of the determination comprises computer usable program code configured for notifying the middleware software that another service acceptor is able to process the request, and further comprising:

computer usable program code configured for the middleware software to send the request to the another service acceptor for processing.

14. The computer program product according to claim 11, further comprising a plurality of service requesters, wherein said plurality of service requesters are in communication with one another, and wherein said plurality of service providers are in communication with one another, and further comprising:

computer usable program code configured for said plurality of service requesters to communicate with one another and for said plurality of service providers to communicate with one another.

15. The computer program product according to claim 12, wherein each of said service requester, service provider and middleware software includes a log for storing information regarding service requests and responses to service requests, and wherein if it is determined that another one of said plurality of service acceptors is not able to process the request, further comprising:

computer usable program code configured for storing information regarding inability to process the request in logs of each of the middleware software, the service providers and the service requesters.

16. The computer program product according to claim 11, and further comprising:

computer usable program code configured for sending the service request to a plurality of service acceptors for processing the request.

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

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

a sending unit 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

;

if 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

if 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.

18. The system according to claim 17, and further comprising:

a log associated 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.

19. The system according to claim 17, and further comprising a plurality of service requesters, each of said plurality of service requesters being in communication with one another, and further comprising:

wherein said plurality of service providers are in communication with one another.

20. The system according to claim 17, wherein the data processing system is implemented in a Service-Oriented Architecture.