Techniques for managing interaction of web services and applications

• US 7,797,450 B2
• Filed: 08/26/2003
• Issued: 09/14/2010
• Est. Priority Date: 10/04/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Xie, Nan, Singh, Vebhhav
• Primary Examiner(s): Flynn; Nathan
• Assistant Examiner(s): Patel; Chirag R
• Application Number:
  US10/648,951
• Publication Number:
  US 20040068586A1
• Time in Patent Office: 2,576 Days
• Field of Search: 709/346, 709/246, 709/217
• US Class Current: 709/246
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A web service broker transforms, at runtime, output data from client applications to the input data form required by various web services. Such transformations are based on data and/or parameter mappings that are accessible to the broker. Further, the broker accesses and invokes particular web services in the manner required by the web services. Such invocations are based on information regarding the access style, such as RPC style of communication, and encoding, such as SOAP, associated with respective web services. The broker provides a generic framework in that it is capable of supporting transformation of different data and data forms from many different applications to respective data that many different respective web services can use.

Claims

1. A method for handling requests for web services, the method comprising the computer-implemented steps of:

receiving at a web services broker, from a particular instance of a client application, a request for information, wherein said request includes an identification of a particular web service from which said particular instance wants said requested information, the request having first input data, the first input data being in a form that cannot be used by said particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

in response to receiving said request, the web services broker

accessing, based on said identification of said particular web service,

transformation information that specifies,

how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and

how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

providing said second input data from said first input data, wherein providing the second input data includes supplementing the first input data with a first value for said first parameter required by the particular web service; and

invoking, in said manner required by said particular web service, said particular web service to obtain said requested information from said particular web service;

wherein said requested information is obtained from said particular web service by providing the first value to the particular web service as a value for said first parameter;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, further comprising the steps of:

receiving, from said particular web service, said requested information; and

transforming, based on said transformation information, said requested information to data that said client application can use.

3. The method of claim 1, wherein said transformation information includes a mapping of first input data from a first particular client application to second input data that a first web service can use, and a mapping of first input data from a second particular client application to said second input data that said first web service can use, and wherein said first input data from said first particular client application has a different form than said first input data from said second particular client application.

4. The method of claim 1, wherein said transformation information includes a mapping of first input data from a first client application to second input data that a first web service can use and to second input data that a second web service can use, and wherein said first web service is different than said second web service.

5. The method of claim 1, further comprising the computer-implemented steps of:

based on said transformation information, determining whether to use RPC style of communication or messaging style of communication to invoke said particular web service.

6. The method of claim 1, further comprising the computer-implemented steps of:

based on said transformation information, determining whether to use SOAP encoding to encode a communication for invoking said particular web service.

24. The method of claim 1,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein providing said second input data includes changing said second value, based on said transformation information, to create a changed value, wherein changing said second value includes performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

25. The method of claim 1, wherein said transformation information specifies how to transform a plurality of first data each from a respective source of a plurality of sources, to a plurality of second data each for a respective web service of a plurality of web services.

53. The method of claim 1,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.

7. A method for handling requests for web services, the method comprising the computer-implemented steps of:

receiving at a web services broker, from a particular instance of a client application, a request for information, wherein said request includes an identification of a particular instance of said client application, the request having first input data, the first input data being in a form that cannot be used by a particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

in response to receiving said request, based on said identification of said particular instance of said client application, the web services broker accessing transformation information;

wherein said transformation information includes a mapping between said identification of said particular instance of said client application and an identification of said particular web service, the mapping indicating that said particular instance prefers said particular web service to service requests from said particular instance for said requested information;

wherein said transformation information specifies how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

based on said transformation information, the web services broker providing said second input data from said first input data, wherein providing the second input data includes supplementing the first input data with a first value for said first parameter required by the particular web service;

the web services broker invoking, in said manner required by said particular web service, said particular web service to obtain said requested information from said particular web service;

wherein said requested information is obtained from said particular web service by the web services broker providing the first value to the particular web service as a value for said first parameter;

wherein the method is performed by one or more computing devices.

8. The method of claim 7, wherein said identification of a particular instance of said client application includes identification of a user of said client application.

9. The method of claim 7, further comprising the computer-implemented step of:

passing said second input data as input to said particular web service to service said request.

10. The method of claim 9,

wherein said transformation information specifies a mapping between said first input data output from said client application and data that said particular web service can use as input to determine said requested information;

and

wherein said step of passing includes passing said second input data, according to said transformation information, as input to said particular web service to determine said requested information.

11. The method of claim 10,

wherein said transformation information specifies a first manner in which said particular web service can be invoked to service requests for said requested information;

and

wherein said step of passing includes passing said second input data in said first manner, to invoke said particular web service to determine said requested information.

12. The method of claim 11,

wherein said transformation information specifies a second manner in which said second input data is characterized so that said particular web service can be invoked to service requests for said requested information;

and

wherein said step of passing includes passing, according to said first manner, said second input data that is characterized according to said second manner, to invoke said particular web service to determine said requested information.

13. The method of claim 12, wherein said second manner includes characterizing said second input data according to Simple Object Access Protocol.

14. The method of claim 9,

wherein said transformation information specifies a first manner in which said particular web service can be invoked to service requests for said requested information and a second manner in which said second input data is characterized in an invocation of said particular web service;

and

wherein said step of passing includes passing, according to said first manner, said second input data that is characterized according to said second manner, to invoke said particular web service to determine said requested information.

15. The method of claim 7, wherein said particular web service has characteristics that are described in Web Service Description Language.

16. The method of claim 15, wherein said particular web service has characteristics that are published in a Universal Description, Discovery, and Integration registry.

17. The method of claim 7, further comprising the steps of:

receiving, from said particular web service, said requested information; and

transforming, based on said transformation information, said requested information to data that said client application can use.

18. The method of claim 7, wherein said transformation information specifies how to transform a plurality of first input data each from a respective client application of a plurality of client applications, to a plurality of second input data each for a respective web service of a plurality of web services.

19. The method of claim 7, wherein said transformation information includes a mapping of first input data from a first particular client application to second input data that a first web service can use, and a mapping of first input data from a second particular client application to said second input data that said first web service can use, and wherein said first input data from said first particular client application has a different form than said first input data from said second particular client application.

20. The method of claim 7, wherein said transformation information includes a mapping of first input data from a first client application to second input data that a first web service can use and to second input data that a second web service can use, and wherein said first web service is different than said second web service.

21. The method of claim 20, wherein said first web service and said second web service can determine the same requested information, and wherein said second input data that said first web service can use is different from said second input data that said second web service can use.

51. The method of claim 7,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein providing said second input data includes changing said second value, based on said transformation information, to create a changed value, wherein changing said second value includes performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

54. The method of claim 7,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.

22. A system for handling requests for web services, the system comprising:

means for receiving at a web services broker, from a particular instance of a client application, a request for information from a particular web service, wherein said request includes an identification of a particular web service from which said particular instance wants said requested information, the request having first input data, the first input data being in a form that cannot be used by said particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

means for the web services broker accessing, in response to receiving said request, based on said identification of said particular web service, transformation information that specifies

how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and

how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

means for the web services broker providing, in response to receiving said request, based on said transformation information, said second input data from said first input data, wherein the means for providing the second input data includes means for supplementing the first input data with a first value for said first parameter required by the particular web service;

means for the web services broker invoking, in response to receiving said request, based on said transformation information, said particular web service in said manner required by said particular web service to obtain said requested information;

wherein the means for the web services broker invoking includes means for obtaining said requested information from said particular web service by providing the first value to the particular web service as a value for said first parameter.

49. The system of claim 22,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein the means for providing said second input data includes means for changing said second value, based on said transformation information, to create a changed value, wherein the means for changing said second value includes means for performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

55. The system of claim 22,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.

23. A system for handling requests for web services, the system comprising:

means for receiving at a web services broker, from a particular instance of said client application, a request for information, wherein said request includes an identification of a particular instance of said client application, the request having first input data, the first input data being in a form that cannot be used by a particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

means for the web services broker accessing transformation information in response to receiving said request and based on said identification of said particular instance of said client application;

wherein said transformation information includes a mapping between said identification of said particular instance of said client application and an identification of said particular web service, the mapping indicating that said particular instance prefers said particular web service to service requests from said particular instance for said requested information;

wherein said transformation information specifies how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

means for the web services broker providing said second input data from said first input data based on said transformation information, wherein the means for providing the second input data includes means for supplementing the first input data with a first value for said first parameter required by the particular web service;

means for the web services broker invoking, in response to receiving said request, based on said transformation information, said particular web service in said manner required by said particular web service to obtain said requested information;

wherein the means for the web services broker invoking includes means for obtaining said requested information from said particular web service by providing the first value to the particular web service as a value for said first parameter.

50. The system of claim 23,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein the means for providing said second input data includes means for changing said second value, based on said transformation information, to create a changed value, wherein the means for changing said second value includes means for performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

56. The system of claim 23,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.

26. A non-transitory computer-readable medium storing instructions for handling requests for web services, the instructions, when executed by one or more computing devices, cause the one or more computing devices to perform the computer-implemented steps of:

receiving at a web services broker, from a particular instance of a client application, a request for information, wherein said request includes an identification of a particular web service from which said particular instance wants said requested information, the request having first input data, the first input data being in a form that cannot be used by said particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

in response to receiving said request, the web services broker

accessing, based on said identification of said particular web service,

transformation information that specifies,

how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and

how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

providing said second input data from said first input data, wherein providing the second input data includes supplementing the first input data with a first value for said first parameter required by the particular web service; and

invoking, in said manner required by said particular web service, said particular web service to obtain said requested information from said particular web service;

wherein said requested information is obtained from said particular web service by providing the first value to the particular web service as a value for said first parameter.

27. The non-transitory computer-readable medium of claim 26, further comprising instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform the steps of:

receiving, from said particular web service, said requested information; and

transforming, based on said transformation information, said requested information to data that said client application can use.

28. The non-transitory computer-readable medium of claim 26, wherein said transformation information includes a mapping of first input data from a first particular client application to second input data that a first web service can use, and a mapping of first input data from a second particular client application to said second input data that said first web service can use, and wherein said first input data from said first particular client application has a different form than said first input data from said second particular client application.

29. The non-transitory computer-readable medium of claim 26, wherein said transformation information includes a mapping of first input data from a first client application to second input data that a first web service can use and to second input data that a second web service can use, and wherein said first web service is different than said second web service.

30. The non-transitory computer-readable medium of claim 26, further comprising instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform the computer-implemented steps of:

based on said transformation information, determining whether to use RPC style of communication or messaging style of communication to invoke said particular web service.

31. The non-transitory computer-readable medium of claim 26, further comprising instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform the computer-implemented steps of:

based on said transformation information, determining whether to use SOAP encoding to encode a communication for invoking said particular web service.

47. The non-transitory computer-readable medium of claim 26,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein providing said second input data includes changing said second value, based on said transformation information, to create a changed value, wherein changing said second value includes performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

48. The non-transitory computer-readable medium of claim 26, wherein said transformation information specifies how to transform a plurality of first data each from a respective source of a plurality of sources, to a plurality of second data each for a respective web service of a plurality of web services.

57. The non-transitory computer-readable medium of claim 26,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.

32. A non-transitory computer-readable medium storing instructions for handling requests for web services, the instructions, when executed by one or more computing devices, cause the one or more computing devices to perform the computer-implemented steps of:

receiving at a web services broker, from a particular instance of a client application, a request for information, wherein said request includes an identification of a particular instance of said client application, the request having first input data, the first input data being in a form that cannot be used by a particular web service to service requests for said information at least in part because said first input data does not include any value for a first parameter required by the particular web service;

in response to receiving said request, based on said identification of said particular instance of said client application, the web services broker accessing transformation information;

wherein said transformation information includes a mapping between said identification of said particular instance of said client application and an identification of said particular web service, the mapping indicating that said particular instance prefers said particular web service to service requests from said particular instance for said requested information;

wherein said transformation information specifies how to provide, from said first input data associated with said request, second input data that said particular web service can use to service requests for said requested information, and how to invoke said particular web service in a manner required by said particular web service, to obtain said requested information from said particular web service;

based on said transformation information, the web services broker providing said second input data from said first input data, wherein providing the second input data includes supplementing the first input data with a first value for said first parameter required by the particular web service;

the web services broker invoking, in said manner required by said particular web service, said particular web service to obtain said requested information from said particular web service;

wherein said requested information is obtained from said particular web service by the web services broker providing the first value to the particular web service as a value for said first parameter.

33. The non-transitory computer-readable medium of claim 32, wherein said identification of a particular instance of said client application includes identification of a user of said client application.

34. The non-transitory computer-readable medium of claim 32, further comprising instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform the computer-implemented step of:

passing said second input data as input to said particular web service to service said request.

35. The non-transitory computer-readable medium of claim 34,

wherein said transformation information specifies a mapping between said first input data output from said client application and data that said particular web service can use as input to determine said requested information;

and

wherein said step of passing includes passing said second input data, according to said transformation information, as input to said particular web service to determine said requested information.

36. The non-transitory computer-readable medium of claim 35,

wherein said transformation information specifies a first manner in which said particular web service can be invoked to service requests for said requested information;

and

wherein said step of passing includes passing said second input data in said first manner, to invoke said particular web service to determine said requested information.

37. The non-transitory computer-readable medium of claim 36,

wherein said transformation information specifies a second manner in which said second input data is characterized so that said particular web service can be invoked to service requests for said requested information;

and

wherein said step of passing includes passing, according to said first manner, said second input data that is characterized according to said second manner, to invoke said particular web service to determine said requested information.

38. The non-transitory computer-readable medium of claim 37, wherein said second manner includes characterizing said second input data according to Simple Object Access Protocol.

39. The non-transitory computer-readable medium of claim 34,

wherein said transformation information specifies a first manner in which said particular web service can be invoked to service requests for said requested information and a second manner in which said second input data is characterized in an invocation of said particular web service;

and

wherein said step of passing includes passing, according to said first manner, said second input data that is characterized according to said second manner, to invoke said particular web service to determine said requested information.

40. The non-transitory computer-readable medium of claim 32, wherein said particular web service has characteristics that are described in Web Service Description Language.

41. The non-transitory computer-readable medium of claim 40, wherein said particular web service has characteristics that are published in a Universal Description, Discovery, and Integration registry.

42. The non-transitory computer-readable medium of claim 32, further comprising instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform the steps of:

receiving, from said particular web service, said requested information; and

transforming, based on said transformation information, said requested information to data that said client application can use.

43. The non-transitory computer-readable medium of claim 32, wherein said transformation information specifies how to transform a plurality of first input data each from a respective client application of a plurality of client applications, to a plurality of second input data each for a respective web service of a plurality of web services.

44. The non-transitory computer-readable medium of claim 32, wherein said transformation information includes a mapping of first input data from a first particular client application to second input data that a first web service can use, and a mapping of first input data from a second particular client application to said second input data that said first web service can use, and wherein said first input data from said first particular client application has a different form than said first input data from said second particular client application.

45. The non-transitory computer-readable medium of claim 32, wherein said transformation information includes a mapping of first input data from a first client application to second input data that a first web service can use and to second input data that a second web service can use, and wherein said first web service is different than said second web service.

46. The non-transitory computer-readable medium of claim 45, wherein said first web service and said second web service can determine the same requested information, and wherein said second input data that said first web service can use is different from said second input data that said second web service can use.

52. The non-transitory computer-readable medium of claim 32,

wherein the first input data includes a second value that corresponds to a second parameter required by the particular web service;

wherein providing said second input data includes changing said second value, based on said transformation information, to create a changed value, wherein changing said second value includes performing a lookup operation, based on said second value, to identify the changed value; and

wherein said requested information is obtained from said particular web service by providing the changed value to the particular web service as a value for said second parameter.

58. The non-transitory computer-readable medium of claim 32,

wherein the particular web service serves as the source of said requested information, and is separate from the web services broker;

and

wherein the particular instance of said client application is separate from the web services broker.