Web service integration

• US 7,475,123 B2
• Filed: 11/12/2003
• Issued: 01/06/2009
• Est. Priority Date: 11/18/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Schwarze, Peter
• Primary Examiner(s): Barqadle; Yasin M
• Application Number:
  US10/712,759
• Publication Number:
  US 20040139154A1
• Time in Patent Office: 1,882 Days
• Field of Search: 709201-203, 709217-219, 709227-232, 709/238, 709/245, 705 26- 29
• US Class Current: 709/217
• CPC Class Codes: G06F 16/9562 Bookmark management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

An enterprise system may include a server including an integration module that enables applications at the server to integrate web services, e.g., by providing links to the external web service. Each application is associated with one or more business types in a table at the server. The integration module, which may be an API, sends a list of external web services of a type (or types) associated with an application when a user at a client computer in the enterprise system opens that application. The integration module may also generate a URL call and redirect the user'"'"'s browser to an external web service when the user selects that external web service.

Claims

1. A method comprising:

storing, at a server, an address for each of a plurality of web services and at least one of a plurality of parameters specific to each of the plurality of web services;

assigning each web service with one or more of a plurality of business types, the address including a uniform resource locator URL for each of the plurality of web services and the at least one parameter, the assignment stored at a table at the server;

associating one or more of said plurality of business types to an application;

in response to a client running the application, sending a list identifying one or more web services assigned with the one or more business types associated with the application;

and in response to the user selecting one of the one or more web services in the list, redirecting the client to the selected web service, by constructing, by the server, the URL for the selected web service from the address and the at least one parameter stored at the table at the server, wherein redirecting the client comprises generating a URL call with a format compliant with an Open Catalog Interface and an Open Partner Interface.

3. The method of claim 1, wherein each address is stored in an entry in a table.

4. The method of claim 3, wherein additional information relating to the service is stored in the service entry in the table.

5. The method of claim 1, wherein the URL call is in an Open Catalog Interface and Open Partner Interface compliant format comprising an outbound section including information from the table.

6. The method of claim 1, further comprising:

opening a new browser at the client for the selected service.

7. The method of claim 1, further comprising:

receiving an Open Catalog Interface and Open Partner Interface compliant response from the service.

8. The method of claim 1, further comprising:

in response to receiving the list at the client, displaying at the client an identifier for each of the one or more services in the list, the one or more services are assigned to enable customization.

2. A method comprising:

storing, at a server, an address for each of a plurality of web services and at least one of a plurality of parameters specific to each of the plurality of web services, the address including a URL (Uniform Resource Locator);

assigning, at the server, each of the web services with one of a plurality of business types, the address including the URL and the at least one parameter, the business types representing the type of information each web service provides, the assignment stored at a table at the server;

associating, at the table at the server, one or more of said plurality of business types to an application;

sending, by the server in response to a client running the application, a list identifying one or more web services assigned with the one or more business types associated with the application; and

redirecting, in response to the user selecting one of the one or more web services in the list, the client to the selected web service by constructing, by the server, the URL for the selected web service from the address and the at least one parameter stored at the table at the server, wherein redirecting the client comprises generating a URL call with a format compliant with an Open Catalog Interface and an Open Partner Interface.

9. A system comprising:

a server including

a plurality of applications, each application associated with one or more service types, and

a table including a number of entries, each entry including an address for an external web service and a service type assigned to the external web service;

a plurality of clients, each client including a browser;

a first networked communication system operative to enable communication between the server and the plurality of clients;

a second networked communication system operative to enable communication between the plurality of clients and external web services; and

an integration module operative to;

in response to a client opening one of the applications, sending a list identifying one or more external web services assigned with the one or more service types associated with the application; and

in response to the user selecting one of said external web services in the list, redirecting the client browser to the selected external web service by constructing, by the integration module, the address including a uniform resource locator (URL) for the selected external web service, wherein redirecting the client comprises generating a URL call with a format compliant with an Open Catalog Interface and an Open Partner Interface.

10. The system of claim 9, wherein the address is a URL (Uniform Resource Locator).

11. The system of claim 9, wherein the integration module is an API (Application Programming Interface).

12. The system of claim 9, wherein the first networked communication system is an enterprise portal.

13. The system of claim 9, wherein the second networked communication system is the World Wide Web.

15. The system of claim 9, wherein the integration module is operative to generate a URL call to the selected external web service from the entry in the table corresponding to the selected external web service.

16. The system of claim 9, wherein the integration module is operative to receive a response from the selected external web service in an Open Catalog Interface and Open Partner Interface compliant format comprising an outbound section including information from the table.

14. The system 9, wherein the each entry in the table includes additional information about the corresponding external web service.