Automated Web Service Generation for Application Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing application platforms developed before the emergence of web services lack interoperability, requiring manual creation of web service shells to expose application logic, which is time-consuming and requires additional expertise, limiting the reuse of components across different platforms.

Innovation Solution

Automated generation of web service classes for each business application class, with separate web service methods that call interface web service methods stored on a web server, allowing for compilation and storage on the web server, enabling interoperability and simplifying the process of exposing application logic as web services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual web service shells are written for each application method, then application logic can be exposed to remote code, but the process becomes time-consuming and requires additional web services expertise

Engineering Contradiction:

ImproveinteroperabilityVSAvoidtime to create web service shells

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating web service shell code based on existing application method definitions. The generation module pre creates the necessary web service infrastructure, including SOAP envelopes, parameter mappings, and communication protocols, eliminating the need for manual writing of these repetitive structures.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The application platform performs self-service by automatically exposing its own methods as web services through the generation module. The system uses its existing method definitions and metadata to self-generate the corresponding web service implementations, reducing dependency on external web services expertise.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If manual web service shells are written for each application method, then application logic can be exposed to remote code, but additional expertise in web services formation is required

Engineering Contradiction:

ImproveinteroperabilityVSAvoidcomplexity of web service creation process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The generation module acts as an intermediary between the existing application platform and the web services infrastructure. It translates internal method definitions into standard web service formats, handling the complexity of protocol translation and infrastructure integration without requiring programmers to directly engage with web services formation.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If separate web service methods are written for each application method, then remote code can invoke application logic, but the number of web service methods increases

Engineering Contradiction:

Improveremote invocation capabilityVSAvoidnumber of web service methods

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The generation module implements a universal approach by creating a standardized web service method template that can serve multiple application methods. Rather than crafting unique web service implementations for each application method, the system uses a unified generation process that handles parameter mapping, data type conversion, and protocol formatting consistently across all methods.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system manages complexity through parameter changes by dynamically adjusting method signatures, data types, and parameter mappings based on the underlying application method definitions. The generation module automatically adapts the web service interface parameters to match the application layer parameters, handling type conversions and protocol-specific requirements without manual intervention.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS7904880B2Generating and binding web services to application components

Publication Date: 2011.03.08 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

For each of a set of business application classes on an application server, a web service class consisting of a separate web service method for each of a set of actions is generated. Each web service method contains a call to an interface web service method stored on a web server. The interface web service method is capable of calling a method on the application server. Once generated, the web service classes are compiled into an assembly and are stored on the web server.