System and method for providing a routing service in distributed computing environment

• US 7,707,594 B1
• Filed: 08/20/2002
• Issued: 04/27/2010
• Est. Priority Date: 08/20/2002
• Status: Active Grant

• Current Assignee: Shopify Incorporated
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Foster, David B., Holden, Larry K.
• Primary Examiner(s): Ho; Andy
• Application Number:
  US10/223,359
• Time in Patent Office: 2,807 Days
• Field of Search: 709/328, 709/242, 709/243, 709/238, 709/201, 709/203, 709/219, 719/330
• US Class Current: 719/330
• CPC Class Codes: G06F 2209/5015 Service provider selection
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

A system for providing a routing service that enables a client to locate a target service in distributed computing environment that supports multiple communications protocols. The system includes a main database and a routing mechanism. The main database has routing information. The routing mechanism can be distributed in multiple instances. The routing mechanism includes a local database. The local database stores an extract of the main database. The routing mechanism uses the local database to make routing decisions. To locate the target service, the client first obtains a reference to the routing mechanism. The client then sends a request with input parameters to the routing mechanism. The routing mechanism then returns output parameters to the client. The output parameters contains a reference and/or associated properties of the target service depending on the type of the target service. The client analyzes the returned output parameters and locates the target service.

Claims

1. A system for providing a routing service that enables a client to locate a target service in a distributed computing environment supporting multiple communications protocols, comprising:

a main database having routing information; and

a routing device including

a local database that has an extract of the main database and an identifier of the target service, wherein the routing device uses the local database to locate the identifier of the target service, and

a routing table, wherein the routing device uses the identifier from the local database to look up additional properties in the routing table to add to the identifier of the target service for locating the target service.

2. The system of claim 1, wherein the routing device is distributed in a plurality of instances.

3. The system of claim 2, wherein the plurality of instances of the routing device are running simultaneously.

4. The system of claim 1, wherein the routing device further includes a code defined in Interface Definition Language (IDL), wherein the code receives input parameters including property name and value of the target service and returns output parameters containing location information of the target service, wherein the output parameters include one of a queue name and a channel name.

5. The system of claim 4, wherein the input parameters include a type of the target service.

6. The system of claim 5, wherein the type of the target service includes a distributed object system.

7. The system of claim 4, wherein the output parameters include a reference of the target service and associated properties.

8. The system of claim 4, wherein the output parameters includes a logical name of a distributed object system service.

9. The system of claim 8, wherein the logical name is used to obtain an object reference of the distributed object system service.

10. The system of claim 4, wherein the location information includes a server Universal Resource Locator (URL) or a Java Naming and Directory Interface name.

11. A method for a client to locate a target service using a routing mechanism that enables distributed applications to locate distributed service provider applications in distributed computing environment supporting multiple communications protocols comprising the steps of:

providing content based input parameters from the client;

obtaining a reference to the routing mechanism by the client, wherein the routing mechanism includes an extract of a main database having routing information and an identifier of the target service;

sending a request to the routing mechanism from the client including at least a content based routing key, wherein the key is utilized in mapping to the target service and wherein the routing mechanism is co-located with the client;

receiving output parameters from the routing mechanism by the client;

analyzing the output parameters by the client to obtain one or more references to the target service; and

locating the target service by the client.

12. The method of claim 11, wherein the method further comprises the step of compiling a first IDL for the routing mechanism and a second IDL for the target service on the client.

13. The method of claim 11, wherein the reference to the routing mechanism is obtained from a distributed object system name service.

14. The method of claim 11, wherein the input parameters include a type and property name and value pair of the target service.

15. The method of claim 14, wherein the type of the target service includes a distributed object system.

16. The method of claim 11, wherein the routing mechanism is distributed in a plurality of instances.

17. The method of claim 16, wherein the plurality of instances of the routing mechanism are running simultaneously.

18. The method of claim 11, wherein the output parameters include a name for a distributed object system service and a logical name for a distributed object system service.

19. The method of claim 18, wherein the method further includes obtaining an object reference to the target service with the logical name using a distributed object system name service.

20. The method of claim 11, wherein the routing mechanism includes a database including routing information.

21. The method of claim 20, wherein the routing mechanism uses the routing information in the database to make a routing decision.

22. The method of claim 20, wherein the database provides identifiers of the target service.

23. The method of claim 22, wherein the routing mechanism further includes a routing table receiving the identifiers from the database and providing additional properties of the target service.

24. The method of claim 23, wherein the routing table is in XML format.

25. The method of claim 11, wherein the routing mechanism further includes a code defined in IDL for receiving the input parameters.

26. A system for providing a routing service in distributed computing environment supporting multiple communications protocols, comprising:

a main database including routing information; and

a device for providing the routing service, distributed in a plurality of instances, wherein the includes a local database storing an extract of the main database and providing identifiers of a target service, a code providing input parameters for searching the local database wherein the input parameters comprise at least a telephone number and wherein the code receives a property name and value of the target service and returns output parameters containing location information of the target service, wherein the output parameters include one of a queue name and a channel name, and a routing table for receiving the identifiers of the target service from the local database and providing additional properties of the target service, wherein the device enables distributed applications to locate distributed service provider applications.

27. A routing server in a distributed computing environment supporting multiple communications protocols, comprising:

a local database, wherein the local database includes routing rules and provides at least one identifier for a target service and;

a routing table, wherein the routing server receives input parameters from a client specifying a desired target service, wherein the routing server is co-located with the client and wherein further the routing server uses the identifier from the local database to look up additional properties in the routing table to add to the identifier of the target service for locating the target service.

28. The system of claim 27, wherein the routing information is extracted from a main database.

29. The system of claim 27, wherein the routing server further includes a code defined in IDL.