Web services message broker architecture

• US 7,702,724 B1
• Filed: 05/27/2004
• Issued: 04/20/2010
• Est. Priority Date: 05/27/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Singh, Inderjeet, Brydon, Sean P.
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): SMARTH, GERALD A
• Application Number:
  US10/854,885
• Time in Patent Office: 2,154 Days
• Field of Search: 709/203, 709/206, 709/213, 709/219, 709/224, 709/230
• US Class Current: 709/203
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A web services message broker architecture. In one embodiment, a system may include a server system and a plurality of applications, each configured to implement one or more enterprise functions and to execute on the server system. The system may further include a web services message broker configured to execute on the server system and to present a central web services interface to the plurality of applications, through which a given one of the plurality of applications is configured to communicate with a web service. In one specific implementation of the system, the web services message broker may be further configured to receive an incoming web service request and to convey the incoming web service request to one of the plurality of applications.

Claims

1. A system, comprising:

a server system;

a plurality of applications, each configured to implement one or more enterprise functions and to execute on said server system; and

a web services message broker configured to execute on said server system and to present a central web services interface to said plurality of applications, wherein said central web services interface comprises a web services endpoint executable to provide a remotely addressable service name to calling applications external to said server system;

wherein said web services message broker is executable to receive an outgoing web services request from a given one of said plurality of applications on said server system, wherein said outgoing web services request does not specify an exact Uniform Resource Indicator (URI) of a corresponding requested web service and wherein said web services message broker is further executable to determine said exact URI of said requested web service and to dispatch said outgoing web services request to said requested web service via said exact URI; and

wherein said web services message broker is further executable to receive via said web services endpoint, an incoming web services request directed to said remotely addressable service name by a given one of said calling applications external to said server system, and wherein said web services message broker is further executable to dispatch said incoming web services request to a corresponding one or more of said applications on said server system dependent upon identifying information included in said incoming web services request.

2. The system as recited in claim 1, wherein to dispatch said outgoing web services request to said requested web service said web services message broker is further configured to exchange a message with a web service entity configured to execute on another server system.

3. The system as recited in claim 2, wherein said message comprises a document formatted according to a version of Extensible Markup Language (XML) format.

4. The system as recited in claim 2, wherein said message is formatted according to a version of Simple Object Access Protocol (SOAP).

5. The system as recited in claim 1, wherein said web services message broker is further configured to send and receive messages using Hypertext Transfer Protocol (HTTP).

6. The system as recited in claim 1, wherein said web services message broker is further configured to publish a description of said remotely addressable service name according to Web Services Description Language (WSDL) protocol.

7. The system as recited in claim 1, wherein said incoming web services request has an associated document type, wherein said web services message broker is configured to provide a generic interface through which to receive said incoming web services request, and wherein said web services message broker is further configured to receive said incoming web services request independently of said associated document type.

8. The system as recited in claim 1, wherein said web services message broker is further configured to split or duplicate said incoming web services request into multiple messages and to convey each of said multiple messages to one or more of said plurality of applications.

9. The system as recited in claim 8, wherein said web services message broker is further configured to insert a correlation identifier corresponding to said incoming web service request into each of said multiple messages.

10. The system as recited in claim 1, wherein said web services message broker is further configured to translate a first message format used by said given application to or from a second message format used by said requested web service.

11. The system as recited in claim 3, wherein said web services message broker is further configured to check said document according to an XML document schema map.

12. A method, comprising:

a plurality of applications executing on a server system, wherein each of said plurality of applications is configured to implement one or more enterprise functions;

a web services message broker executing on said server system;

said web services message broker presenting a central web services interface to said plurality of applications;

said web services message broker receiving an outgoing web services request from a given one of said plurality of applications, wherein said outgoing web services request does not specify an exact Uniform Resource Indicator (URI) of a corresponding requested web service;

said web services message broker determining said exact URI of said requested web service and dispatching said outgoing web services request to said requested web service via said exact URI;

said web services message broker receiving, via a web services endpoint providing a remotely addressable service name to calling applications external to said server system, an incoming web services request directed to said remotely addressable service name by a given one of said calling applications; and

said web services message broker dispatching said incoming web services request to a corresponding one or more of said applications dependent upon identifying information included in said incoming web services request.

13. The method as recited in claim 12, wherein said web services message broker dispatching said outgoing web services request to said requested web service comprises exchanging a message with a web service entity configured to execute on another server system.

14. The method as recited in claim 13, wherein said message comprises a document formatted according to a version of Extensible Markup Language (XML) format.

15. The method as recited in claim 13, wherein said message is formatted according to a version of Simple Object Access Protocol (SOAP).

16. The method as recited in claim 12, further comprising said web services message broker sending and receiving messages using Hypertext Transfer Protocol (HTTP).

17. The method as recited in claim 12, further comprising:

said web services message broker publishing a description of said remotely addressable service name according to Web Services Description Language (WSDL) protocol.

18. The method as recited in claim 12, wherein said incoming web services request has an associated document type, the method further comprising said web services message broker receiving said incoming web service request via a generic interface independently of said associated document type.

19. The method as recited in claim 12, further comprising:

said web services message broker splitting or duplicating said incoming web services request into multiple messages; and

said web services message broker conveying each of said multiple messages to one or more of said plurality of applications.

20. The method as recited in claim 19, further comprising said web services message broker inserting a correlation identifier corresponding to said incoming web service request into each of said multiple messages.

21. The method as recited in claim 12, further comprising said web services message broker translating a first message format used by said given application to or from a second message format used by said requested web service.

22. The method as recited in claim 14, further comprising said web services message broker checking said document according to an XML document schema map.

23. A computer-accessible storage medium storing program instructions, wherein the program instructions are executable to implement:

a plurality of applications executing on a server system, wherein each of said plurality of applications is configured to implement one or more enterprise functions;

a web services message broker executing on said server system;

said web services message broker presenting a central web services interface to said plurality of applications;

said web services message broker receiving an outgoing web services request from a given one of said plurality of applications, wherein said outgoing web services request does not specify an exact Uniform Resource Indicator (URI) of a corresponding requested web service;

said web services message broker determining said exact URI of said requested web service and dispatching said outgoing web services request to said requested web service via said exact URI;

said web services message broker receiving, via a web services endpoint providing a remotely addressable service name to calling applications external to said server system, an incoming web services request directed to said remotely addressable service name by a given one of said calling applications; and

said web services message broker dispatching said incoming web services request to a corresponding one or more of said applications dependent upon identifying information included in said incoming web services request.

24. The computer-accessible storage medium as recited in claim 23, wherein said web services message broker dispatching said outgoing web services request to said requested web service comprises exchanging a message with a web service entity configured to execute on another server system.

25. The computer-accessible storage medium as recited in claim 24, wherein said message comprises a document formatted according to a version of Extensible Markup Language (XML) format.

26. The computer-accessible storage medium as recited in claim 24, wherein said message is formatted according to a version of Simple Object Access Protocol (SOAP).

27. The computer-accessible storage medium as recited in claim 23, wherein said program instructions are further executable to implement said web services message broker sending and receiving messages using Hypertext Transfer Protocol (HTTP).

28. The computer-accessible storage medium as recited in claim 23, wherein said program instructions are further executable to implement:

said web services message broker publishing a description of said remotely addressable service name according to Web Services Description Language (WSDL) protocol.

29. The computer-accessible storage medium as recited in claim 23, wherein said incoming web service request has an associated document type, and wherein said program instructions are further executable to implement said web services message broker receiving said incoming web services request via a generic interface independently of said associated document type.

30. The computer-accessible storage medium as recited in claim 23, wherein said program instructions are further executable to implement:

said web services message broker splitting or duplicating said incoming web services request into multiple messages; and

said web services message broker conveying each of said multiple messages to one or more of said plurality of applications.

31. The computer-accessible storage medium as recited in claim 30, wherein said program instructions are further executable to implement said web services message broker inserting a correlation identifier corresponding to said incoming web service request into each of said multiple messages.

32. The computer-accessible storage medium as recited in claim 23, wherein said program instructions are further executable to implement said web services message broker translating a first message format used by said given application to or from a second message format used by said requested web service.

33. The computer-accessible storage medium as recited in claim 25, wherein said program instructions are further executable to implement said web services message broker checking said document according to an XML document schema map.