Unified Web Services Descriptor for Configuration Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current web services technologies face challenges in achieving interoperability and client-side flexibility due to convoluted relationships and mappings between standards, with conventional models lacking support for consumer-based outside-in approaches and inefficient resource usage from separate web services and client descriptors.

Innovation Solution

A container-based configuration and administration system is introduced, where a common meta model is generated to unify web services and web services client frameworks, eliminating the need for separate descriptors and tools, and allowing for both provider-oriented and consumer-oriented approaches through a single common descriptor placed in a container, enabling easier development, deployment, and configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate web services and web services client descriptors are used, then interoperability can be achieved through standard mappings, but device complexity and resource usage increase due to convoluted relationships and mappings between standards

Engineering Contradiction:

ImproveinteroperabilityVSAvoidcomplexity of relationships and mappings between standards

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the web services descriptor and web services client descriptor into a single unified descriptor that contains both design-time and runtime configurations. This eliminates the need for separate descriptors and complex mappings between them, while maintaining interoperability through the unified structure that incorporates necessary standard mappings.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified descriptor serves multiple functions simultaneously: it acts as both a web services descriptor and a web services client descriptor, contains both design-time and runtime configurations, and supports both provider-oriented and consumer-oriented approaches. This multi-functionality reduces the number of separate components needed.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate web services and web services client descriptors are maintained, then specific configurations can be managed independently, but resource waste occurs due to duplication and separate tool requirements

Engineering Contradiction:

Improveindependent configuration managementVSAvoidresource waste from separate descriptors and tools

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

By combining web services and client configurations into a single unified descriptor, the patent eliminates resource waste from maintaining separate descriptors and their associated tools. The unified descriptor can still manage specific configurations independently through its structured sections for design-time and runtime settings.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified descriptor is designed to be universally applicable for both web services and web services clients, eliminating the need for separate toolchains and reducing resource consumption. It provides a single source of truth that serves multiple purposes without duplication.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If conventional web services model with separate descriptors is used, then provider-oriented inside-out approach is supported, but consumer-based outside-in approach is not supported leading to usability deficiencies

Engineering Contradiction:

Improveprovider-oriented inside-out approach supportVSAvoidconsumer-based outside-in approach support

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The unified descriptor is designed to support both provider-oriented inside-out approaches and consumer-based outside-in approaches within a single structure. It contains configurable sections that can be populated and utilized according to either development paradigm, making the system versatile and user-friendly for different operational approaches.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of manufacture

If design-time and runtime configurations are separated into different descriptors, then each can be managed independently, but configuration and administration becomes more complex

Engineering Contradiction:

Improveindependent management of design-time and runtime configurationsVSAvoidcomplexity of configuration and administration

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent merges design-time configurations and runtime configurations into a single unified descriptor with clearly structured sections. This allows independent management of each configuration type within the same file, reducing administrative complexity while maintaining the ability to manage them separately when needed.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS7673028B2Method and system for container-managed configuration and administration

Publication Date: 2010.03.02 SAP SE

AI summary

A method and system for container-based configuration and administration. In one embodiment, a configuration file is created at a first location. The configuration file is duplicated into a duplicate configuration file, which is placed at a second location.