Configuration of web services

• US 8,892,454 B2
• Filed: 09/27/2007
• Issued: 11/18/2014
• Est. Priority Date: 09/27/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Rabetge, Christian, Zubev, Alexander, Boehrer, Otto, Wiechers, Volker, Falter, Timm, Savchenko, Vladimir, Mehta, Harish, Kunz, Thomas
• Primary Examiner(s): Gart, Matthew
• Assistant Examiner(s): PARIKH, HARSHAD R
• Application Number:
  US11/863,029
• Publication Number:
  US 20090089109A1
• Time in Patent Office: 2,609 Days
• Field of Search: 705/7, 705/35
• 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 comprising a non-transitory computer-readable medium, the computer program product being operable to cause at least one processor to perform operations comprising:

receiving, at a consumer system during a business configuration phase of a deployment of a web services system, first data characterizing a web service call to a web service related to a business process implemented by a consumer application of the consumer system, the first data comprising a consumer proxy identifier to represent the web service call;

receiving, at the consumer system during the business configuration phase of the deployment of the web services system, second data characterizing a placeholder for the web service call, the second data comprising a name used to identify a system where the address of the system has not been determined prior to the business configuration phase, the system to be identified for the web service call during mapping of the system to the consumer proxy;

generating, at the consumer system during the business configuration phase of the deployment of the web services system, a configuration for the proxy identifier representing the web service call, the configuration comprising the address of the system instead of the name; and

calling, at a run-time phase of the deployment of a web services system, the system to provide the web service based on the configuration.

2. The product of claim 1, wherein the web service call is 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 comprising an underlying directory of systems in an enterprise.

4. The product of claim 1, wherein the receiving of the first data and the second data and the generating are performed during the business configuration phase and the operations further comprise, during a technical configuration phase of a system landscape of the deployment of the web services system, adding the system to the system landscape at a service 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 identifier, 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 identifier.

6. The product of claim 1, wherein the first data characterizing the web service call comprises the consumer proxy identifier.

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

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

searching for one or more systems that provide web services to respond to the web service call, 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, at a consumer system during a business configuration phase of a deployment of a web services system, first data characterizing a web service call to a web service related to a business process implemented by a consumer application of the consumer system, the first data comprising a consumer proxy identifier to represent the web service call, the consumer system comprising a programmable processer and a memory;

receiving, at the consumer system during the business configuration phase of the deployment of the web services system, second data characterizing a placeholder for the web service call, the second data comprising a name used to identify a system where the address of the system has not been determined prior to the business configuration phase, the system to be identified for the web service call during mapping of the system to the consumer proxy identifier

generating, automatically at the consumer system during the business configuration phase of the deployment of the web services system, a configuration for the proxy identifier representing the web service call, the configuration comprising the address of the system instead of the name; and

calling, at a run-time phase of the deployment of a web services system, the system to provide the web service based on the configuration.

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

10. The method of claim 8, wherein the receiving of the first data and the second data and the generating are performed during the business configuration phase and the method further comprises, during a technical configuration phase of a system landscape of the deployment of the web services system, 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 identifier, and

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

12. The method of claim 8, wherein the first data characterizing the web service call comprises a list of consumer proxy identifiers, the consumer proxy identifiers identifying which consumer proxies need to be configured, the consumer proxies identifying web services that are called by the consumer proxies.

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

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

searching for one or more systems that provide web services to respond to the web service call, 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 system comprising:

a processor; and

a memory, wherein the processor and the memory are configured to perform a method comprising;

receiving, at a consumer system during a business configuration phase of a deployment of a web services system, first data characterizing a web service call to a web service related to a business process implemented by a consumer application of the consumer system, the first data comprising a consumer proxy identifier to represent the web service call;

receiving, at the consumer system during the business configuration phase of the deployment of the web services system, second data characterizing a placeholder for the web service call, the second data comprising a name used to identify a system where the address of the system has not been determined prior to the business configuration phase, the system to be identified for the web service call during mapping of the system to the consumer proxy identifier;

generating, at the consumer system during the business configuration phase of the deployment of the web services system, a configuration for the proxy identifier representing the web service call, the configuration comprising the address of the system instead of the name; and

calling, at a run-time phase of the deployment of a web services system, the system to provide the web service based on the configuration.

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

16. The system of claim 14, wherein a second, larger application comprises the application as a component of the second application.

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

18. The system of claim 14, wherein the web service call is are in a group of web service calls having a common placeholder.

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

20. The system 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 identifier, and

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