Dynamic Web Services Invocation Model for Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional web services modeling applications and tools face challenges in achieving interoperability and client-side flexibility due to limitations in web services metadata and the conventional separation of standards, models, and entities, leading to convoluted relationships and mappings between relevant standards, which are not evolving fast enough to meet the increasing demand for web services.

Innovation Solution

A dynamic web services invocation model is generated by extracting and inspecting metadata from a Web Service Definition Language (WSDL) file, allowing for the invocation of web services without the need for generating proxy classes, using a dynamic web services proxy that provides a common API independent of specific web services APIs, and utilizing metadata structures to describe web services interfaces, methods, and data types, enabling the building of user interfaces and client applications that are independent of web services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional web services modeling applications and tools are used, then interoperability is achieved to some extent, but client-side flexibility is insufficient due to convoluted relationships and mappings between standards

Engineering Contradiction:
ImproveinteroperabilityVSAvoidclient-side flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a dynamic web services invocation model as an intermediary layer between the WSDL metadata and the client application. This model acts as a mediator that translates web service operations into dynamic invocations, eliminating the need for direct mapping between conventional standards and client code. The dynamic model receives metadata from WSDL and provides flexible client-side access without requiring proxy classes or direct standard mappings.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent employs a dynamic invocation model that can adapt to different web service interfaces at runtime. Instead of using static proxy classes generated from WSDL, the system creates dynamic invocations that can flexibly handle various web service operations. This dynamic approach allows the client to adapt to changing service interfaces without requiring reconfiguration of the client application, thereby improving both interoperability and client-side flexibility.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If proxy classes are generated for each web service, then web service invocation is straightforward, but device complexity and development time increase

Engineering Contradiction:
Improveweb service invocationVSAvoidproxy class generation
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the proxy class generation step from the web service client development process. Instead of generating and managing proxy classes for each web service, the system extracts only the essential metadata from WSDL and uses it to create dynamic invocations. This extraction eliminates the complexity of proxy class management while maintaining ease of web service invocation through a simplified dynamic model.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses a simplified copying approach where instead of copying entire proxy classes for each web service, only the necessary operational interface is copied and adapted dynamically. The dynamic invocation model creates lightweight representations of web service operations based on metadata, avoiding the need for full proxy class copies and reducing overall system complexity.

Inventive Principle:
Principle #26Copying

3Reliability

If metadata structures are used to describe web services, then interoperability is improved, but the metadata is not evolving fast enough to meet increasing demand for flexibility

Engineering Contradiction:
ImproveinteroperabilityVSAvoidmetadata evolution speed
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a dynamic layer on top of the static metadata structures. The dynamic invocation model receives conventional WSDL metadata and transforms it into flexible runtime invocations. This dynamic layer allows the system to adapt to new web service requirements without modifying the underlying metadata structures, effectively decoupling the evolution speed of metadata from the adaptability of the client application.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary extraction and inspection of metadata from WSDL files before web service invocation. By pre-processing and analyzing the metadata structures in advance, the system prepares dynamic invocation models that can quickly adapt to different web service interfaces. This preliminary action allows the system to respond faster to changing requirements without needing to evolve the core metadata standards.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7587425B2Method and system for generating and employing a dynamic web services invocation model
Publication Date: 2009.09.08 SAP SE
  • US7587425B2 patent drawing
  • US7587425B2 patent drawing
  • US7587425B2 patent drawing

AI summary

A system and method are provided to generate a dynamic web services invocation model. In one embodiment, a first metadata and a second metadata are extracted from description content of a Web Service Definition Language (WSDL) file. The first metadata and the second metadata are inspected. A web service is invoked via a dynamic web services invocation model.