Schema Validation Proxy for Web Service Message Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for validating messages according to their schemas in web services do not automatically verify syntax and require manual upload or triggering of schema definition files, leading to inefficiencies in computing resource usage and error analysis.

Innovation Solution

A schema validation proxy system that automatically downloads schema definition files, performs schema validation on request and response messages, and creates consolidated log files, reducing the need for manual intervention and enhancing error analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual upload or triggering of schema definition files is required, then system complexity is reduced, but productivity and ease of operation deteriorate

Engineering Contradiction:
Improveschema validation efficiencyVSAvoidvalidation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The validation proxy automatically downloads schema definition files without requiring manual intervention. The system serves itself by autonomously retrieving schemas from configured locations and triggering validation processes automatically when messages arrive, eliminating the need for manual schema upload or triggering while maintaining manageable complexity through automated configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Schema definition files are pre-configured in the validation proxy with their locations and identification criteria established beforehand. When validation is needed, the system already has the necessary schemas ready or can immediately retrieve them, eliminating manual upload steps and improving productivity through preparedness.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If schema validation is performed automatically, then productivity improves, but device complexity increases

Engineering Contradiction:
Improvemessage validation throughputVSAvoidvalidation proxy complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The validation proxy acts as an intermediary component between message senders and receivers. It automatically performs schema validation on messages passing through it, improving validation throughput without requiring the main application systems to implement complex validation logic. The proxy handles the complexity centrally while maintaining simplicity at the application level.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If manual error analysis is required, then system complexity is reduced, but loss of time and productivity worsen

Engineering Contradiction:
Improveerror analysis timeVSAvoidlogging system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The validation proxy provides automated feedback by creating consolidated log files that automatically capture validation results, errors, and warnings. These logs are generated and maintained automatically during the validation process, eliminating manual error analysis while the structured logging approach keeps complexity manageable through standardized output formats.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Multiple validation results, error messages, and log entries are merged into consolidated log files. This combining approach reduces the time needed for error analysis by providing a single unified view of validation status rather than requiring manual aggregation of separate validation outputs from different sources.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9374437B2Schema validation proxy
Publication Date: 2016.06.21 SAP SE
  • US9374437B2 patent drawing
  • US9374437B2 patent drawing
  • US9374437B2 patent drawing

AI summary

Systems and methods to provide a schema validation proxy to capture and validate messages against their schemas are discussed. The messages are part of web services being called from a client system at a server system. In example embodiments, a request message is received from a client system at a proxy system. Upon receipt of the request message, an automatic download of a schema definition file is triggered. The request message is validated against one or more schemas from the downloaded schema definition file. The request message is forwarded to the server system and the proxy system waits for the response. The corresponding response message is received by the proxy system and is validated against its schema. One or more log files are created to record results of the validating. The log files include a consolidated log file providing an overview of the results during a session.