Balancing load requests and failovers using a UDDI proxy

• US 20050283539A1
• Filed: 05/19/2005
• Published: 12/22/2005
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Betts, Christopher, Rogers, Tony
• Granted Patent: US 8,548,976 B2
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1019 Random or heuristic server selection
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• 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

Abstract

A method for connecting to a web service includes selecting a web service, selecting a server among one or more servers capable of running the selected web service, determining a real address for the selected web service running on the selected server and connecting to the selected web service running on the selected server using the determined real address.

Claims

1. A method for connecting to a web service, the method comprising:

selecting a web service;

selecting a server among one or more servers capable of running the selected web service;

determining a real address for the selected web service running on the selected server; and

connecting to the selected web service running on the selected server using the determined real address.

2. The method of claim 1, wherein selecting a web service comprises searching a directory of web services.

3. The method of claim 2, wherein said directory of web services is a UDDI repository.

4. The method of claim 1, wherein selecting a web service comprises providing a public address.

5. The method of claim 1, wherein selecting a server among one or more servers capable of running the selected web service comprises performing a distributed scheduling algorithm.

6. The method of claim 5, wherein the distributed scheduling algorithm is a static algorithm.

7. The method of claim 5, wherein the distributed scheduling algorithm is a dynamic algorithm.

8. The method of claim 5, wherein the distributed scheduling algorithm is a preemptive algorithm.

9. The method of claim 1, wherein selecting a server among one or more servers capable of running the selected web service comprises:

becoming aware of the status of a primary server of the one or more servers capable of running the selected web service;

selecting the primary server when the primary server has a status of functional; and

selecting a secondary server of the one or more servers capable of running the selected web service when the primary server has a status of non-functional.

10. The method of claim 1, wherein determining a real address for the selected web service running on the selected server comprises looking up the real address for the selected web service running on the selected server in a directory of web services.

11. The method of claim 10, wherein said directory of web services is a UDDI repository.

12. The method of claim 1, wherein connecting to the selected web service running on the selected server comprises:

establishing a connection between a requesting party and a proxy;

establishing a connection between the proxy and the selected web service running on the selected server using the determined real address;

allowing the requesting party to connect to the selected web service running on the selected server through the established connection between the requesting party and the proxy and the established connection between the proxy and the selected web service running on the selected server.

13. The method of claim 1, wherein said connecting to the selected web service running on the selected server comprises:

providing a requesting party with the real address for the selected web service running on the selected server, and

establishing a connection between the requesting party and the selected web service running on the selected server using the determined real address.

14. A system for connecting to a web service comprising:

a web service-selecting unit for selecting a web service;

a server-selecting unit for selecting a server among one or more servers capable of running the selected web service;

a determining unit for determining a real address for the selected web service running on the selected server; and

a connecting unit for connecting to the selected web service running on the selected server using the determined real address.

15. The system of claim 14, wherein selecting a web service comprises searching a directory of web services.

16. The system of claim 15, wherein said directory of web services is a UDDI repository.

17. The system of claim 14, wherein selecting a web service comprises providing a public address.

18. The system of claim 14, wherein selecting a server among one or more servers capable of running the selected web service comprises performing a distributed scheduling algorithm.

19. The system of claim 18, wherein the distributed scheduling algorithm is a static algorithm.

20. The system of claim 18, wherein the distributed scheduling algorithm is a dynamic algorithm.

21. The system of claim 18, wherein the distributed scheduling algorithm is a preemptive algorithm.

22. The system of claim 14, wherein selecting a server among one or more servers capable of running the selected web service comprises:

becoming aware of the status of a primary server of the one or more servers capable of running the selected web service;

selecting the primary server when the primary server has a status of functional; and

selecting a secondary server of the one or more servers capable of running the selected web service when the primary server has a status of non-functional.

23. The system of claim 14, wherein determining a real address for the selected web service running on the selected server comprises looking up the real address for the selected web service running on the selected server in a directory of web services.

24. The system of claim 23, wherein said directory of web services is a UDDI repository.

25. The system of claim 14, wherein said connecting to the selected web service running on the selected server comprises:

establishing a connection between a requesting party and a proxy;

establishing a connection between the proxy and the selected web service running on the selected server using the determined real address;

allowing the requesting party to connect to the selected web service running on the selected server through the established connection between the requesting party and the proxy and the established connection between the proxy and the selected web service running on the selected server.

26. The system of claim 14, wherein said connecting to the selected web service running on the selected server comprises:

providing a requesting party with the real address for the selected web service running on the selected server, and

establishing a connection between the requesting party and the selected web service running on the selected server using the determined real address.

27. A computer system comprising:

a processor; and

a computer recording medium including computer executable code executable by the processor for connecting to a web service, the computer executable code comprising;

code for selecting a web service;

code for selecting a server among one or more servers capable of running the selected web service;

code for determining a real address for the selected web service running on the selected server; and

code for connecting to the selected web service running on the selected server using the determined real address.

28. The computer system of claim 27, wherein selecting a web service comprises searching a directory of web services.

29. The computer system of claim 28, wherein said directory of web services is a UDDI repository.

30. The computer system of claim 27, wherein selecting a web service comprises providing a public address.

31. The computer system of claim 27, wherein selecting a server among one or more servers capable of running the selected web service comprises performing a distributed scheduling algorithm.

32. The computer system of claim 31, wherein the distributed scheduling algorithm is a static algorithm.

33. The computer system of claim 31, wherein the distributed scheduling algorithm is a dynamic algorithm.

34. The computer system of claim 31, wherein the distributed scheduling algorithm is a preemptive algorithm.

35. The computer system of claim 27, wherein the code for selecting a server among one or more servers capable of running the selected web service comprises:

code for becoming aware of the status of a primary server of the one or more servers capable of running the selected web service;

code for selecting the primary server when the primary server has a status of functional; and

code for selecting a secondary server of the one or more servers capable of running the selected web service when the primary server has a status of non-functional.

36. The computer system of claim 27, wherein the code for determining a real address for the selected web service running on the selected server comprises code for looking up the real address for the selected web service running on the selected server in a directory of web services.

37. The computer system of claim 36, wherein said directory of web services is a UDDI repository.

38. The computer system of claim 27, wherein said code for connecting to the selected web service running on the selected server comprises:

code for establishing a connection between a requesting party and a proxy;

code for establishing a connection between the proxy and the selected web service running on the selected server using the determined real address;

code for allowing the requesting party to connect to the selected web service running on the selected server through the established connection between the requesting party and the proxy and the established connection between the proxy and the selected web service running on the selected server.

39. The computer system of claim 27, wherein said code for connecting to the selected server comprises:

code for providing a requesting party with the real address for the selected web service running on the selected server, and

code for establishing a connection between the requesting party and the selected web service running on the selected server using the determined real address.

40. A computer recording medium including computer executable code for connecting to a web service, the computer executable code comprising:

code for selecting a web service;

code for selecting a server among one or more servers capable of running the selected web service;

code for determining a real address for the selected web service running on the selected server; and

code for connecting to the selected web service running on the selected server using the determined real address.