Web Service Configuration Domains for Consistent Runtime Settings

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Configuring web services and their consumer proxies in a service-oriented architecture is complex, requiring technical knowledge and often results in inconsistent and labor-intensive manual configurations, especially when system landscapes and business processes change.

Innovation Solution

Implementing a method to generate run-time configurations for web services and consumer proxies based on predefined policies, allowing for automatic and consistent configuration by grouping systems into domains with associated profiles, thereby reducing manual effort and ensuring transparency and consistency across configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual configuration of web services and consumer proxies is performed, then configuration can be customized for each service, but the configuration process becomes labor-intensive and inconsistent

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidconfiguration speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-defining configuration templates and policies that automatically generate run-time configurations for web services and consumer proxies. Instead of manually configuring each service individually, the system pre-establishes configuration rules and policies that are automatically applied when services are deployed, thereby ensuring consistency while improving productivity.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If individual web service configuration is performed, then specific service details can be customized, but technical knowledge of system landscape is required

Engineering Contradiction:
Improveservice customizationVSAvoidconfiguration simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary configuration management system that mediates between service providers and consumers. This intermediary automatically generates and manages run-time configurations based on predefined policies, eliminating the need for users to have deep technical knowledge of the system landscape while still allowing service customization through policy-based control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses copying by creating template-based configurations that can be replicated across multiple web services and consumer proxies. Instead of manually configuring each service from scratch, the system copies and adapts predefined configuration templates, making the process simpler while maintaining adaptability through parameter customization.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If detailed configuration parameters are managed manually, then configuration precision can be controlled, but the complexity of configuration management increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration management complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent merges multiple configuration parameters and policies into unified configuration templates and domain-wide policy sets. By combining related configuration elements into structured templates with inheritance hierarchies, the system maintains configuration accuracy while reducing management complexity through centralized control and automated generation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent applies segmentation by dividing configuration management into distinct layers: domain-level policies, service-level templates, and instance-level parameters. This hierarchical segmentation allows each layer to be managed independently with appropriate precision, while the overall system complexity is reduced through modular organization and automated propagation of configurations across layers.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9148488B2Configuration domains for the configuration of web services and consumer proxies
Publication Date: 2015.09.29 SAP SE
  • US9148488B2 patent drawing
  • US9148488B2 patent drawing
  • US9148488B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for configuration domains for the configuration of web services and consumer proxies. In general, data characterizing one or more web services to activate is received and run-time configurations are caused to be generated for each of the web services and each of consumer proxies for the web services. The web services are from a provider system in a group of systems having a profile having one or more policies to be adhered to by the systems. The systems may include a consumer system and the provider system. The consumer system may have one or more consumer proxies to call the web services. The run-time configurations may include one or more settings derived from the policies of the profile.