CONFIGURATION OF WEB SERVICES

• US 20090089109A1
• Filed: 09/27/2007
• Published: 04/02/2009
• Est. Priority Date: 09/27/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Falter, Timm, Boehrer, Otto, Rabetge, Christian, Wiechers, Volker, Kunz, Thomas, Mehta, Harish, Zubev, Alexander, Savchenko, Vladimir
• Granted Patent: US 8,892,454 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis
• 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

Methods and apparatus, including computer program products, for configuration of web services. In general, data is received characterizing web service calls for an application, a placeholder destination for the web service calls, and an identification of a system to be mapped to the placeholder; and a configuration is generated for the web service calls, where the configuration maps the placeholder destination to the system. The configuration may be a configuration of proxy objects to make the web service calls. Mapping the placeholder destination to the system may include generating a configuration including the system in lieu of the placeholder destination. Systems may be included in domains, where a security policy may be applied to systems in a domain.

Claims

1. A computer program product, tangibly embodied in a computer-readable medium, the computer program product being operable to cause data processing apparatus to perform operations comprising:

receiving first data characterizing web service calls for an application and a placeholder destination for the web service calls, the placeholder destination being a placeholder for a system, the system to be identified for the web service calls during configuration of proxies for the web service calls, and the system not being identifiable during a design-time of the application;

receiving second data characterizing an identification of the system to be mapped to the placeholder; and

generating a configuration for proxy objects for the web service calls, the configuration comprising the system for their configuration instead of the placeholder destination.

2. The product of claim 1, wherein the web service calls are in a group of web service calls having a common placeholder destination.

3. The product of claim 1, wherein the system is addressed by an identifier from a system landscape directory.

4. The product of claim 1, wherein the receiving first and second data and the generating are performed during a business configuration phase of a system landscape and the operations further comprise, during a technical configuration phase of the system landscape, adding the system to the system landscape at a services registry of the system landscape.

5. The product of claim 1, wherein the generating the configuration comprises applying a first profile to generate a mapping of settings for the configuration and the operations further comprise:

receiving an indication of a second profile to apply to the configuration of the proxy objects, and

applying the second profile to generate an updated version of the configuration at a point in time where the configuration is not being used by the proxy objects.

6. The product of claim 1, wherein the first data characterizing web service calls comprises a list of consumer proxy identifiers.

7. The product of claim 1, wherein the operations further comprise:

receiving a selection of the application to be activated as part of a business process;

searching for one or more systems that provide web services to respond to the web service calls, the searching based at least in part on one or more of web service descriptions and web service classifications; and

providing a user interface to display the systems and allow for a selection of the system to be mapped to the placeholder, the systems being listed in response to the selection of the application to be activated.

8. A computer-implemented method comprising:

receiving first data characterizing web service calls for an application and a placeholder destination for the web service calls, the placeholder destination being a placeholder for a system, the system to be identified for the web service calls during configuration of proxies for the web service calls, and the system not being identifiable during a design-time of the application;

receiving second data characterizing an identification of the system to be mapped to the placeholder; and

generating a configuration for proxy objects for the web service calls, the configuration comprising the system for their configuration instead of the placeholder destination.

9. The method of claim 8, wherein the web service calls are in a group of web service calls having a common placeholder destination.

10. The method of claim 8, wherein the receiving first and second data and the generating are performed during a business configuration phase of a system landscape and the method further comprises, during a technical configuration phase of the system landscape, adding the system to the system landscape at a services registry of the system landscape.

11. The method of claim 8, wherein the generating the configuration comprises applying a first profile to generate a mapping of settings for the configuration and the method further comprises:

receiving an indication of a second profile to apply to the configuration of the proxy objects, and

applying the second profile to generate an updated version of the configuration if the configuration is not being used by the proxy objects.

12. The method of claim 8, wherein the first data characterizing web service calls comprises a list of consumer proxy identifiers.

13. The method of claim 8, wherein the method further comprises:

receiving a selection of the application to be activated as part of a business process;

searching for one or more systems that provide web services to respond to the web service calls, the searching based at least in part on one or more of web service descriptions and web service classifications; and

providing a user interface to display the systems and allow for a selection of the system to be mapped to the placeholder, the systems listed in response to the selection of the application to be activated.

14. A computer program product, tangibly embodied in a computer-readable medium, the computer program product being operable to cause data processing apparatus to perform operations comprising:

receiving first data characterizing web service calls for an application and a placeholder destination for the web service calls;

receiving second data characterizing an identification of a system to be mapped to the placeholder; and

generating a configuration for proxy objects for the web service calls, the configuration comprising the system for their configuration instead of the placeholder destination.

15. The product of claim 14, wherein the system is a system of a system landscape directory.

16. The product of claim 14, wherein the application is a component of a larger application.

17. The product of claim 14, wherein the placeholder destination is a placeholder for a destination not being uniquely identifiable during design-time of the application.

18. The product of claim 14, wherein the web service calls are in a group of web service calls having a common placeholder destination.

19. The product of claim 14, wherein the receiving first and second data and the generating are performed during a business configuration phase of a system landscape and the operations further comprise, during a technical configuration phase of the system landscape, adding the system to the system landscape at a services registry of the system landscape.

20. The product of claim 14, wherein the generating the configuration comprises applying a first profile to generate a mapping of settings for the configuration and the operations further comprise:

receiving an indication of a second profile to apply to the configuration of the proxy objects, and

applying the second profile to generate an updated version of the configuration if the configuration is not being used by the proxy objects.