Schema-less Middleware Parser for Heterogeneous System Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprises face significant resource challenges in creating and maintaining custom middleware to interface and communicate between disparate computer systems and applications that use different languages and protocols, requiring extensive manual effort and leading to programming bugs and slow updates.

Innovation Solution

A schema-less middleware method and system, referred to as Polyglot, automatically generates and updates middleware code by parsing commands and responses without individualized logic, using a domain-specific language and Java code generator to unify API consumption and handle various response formats, reducing the need for custom code and minimizing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom middleware is manually created and maintained for each different system and application, then individualized interface logic can be provided, but resource consumption and development time increase significantly

Engineering Contradiction:
Improveindividualized interface logicVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs self-service by automatically generating middleware code through parsing system output objects and applying grammar rules, eliminating the need for manual programming of individualized interface logic while maintaining adaptability to different systems and applications

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention changes the parameter of middleware creation from manual programming to automated generation through parameter-driven parsing and grammar application, transforming the development process into a configurable rather than hard-coded approach

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If custom middleware is manually created and maintained for each different system and application, then individualized interface logic can be provided, but resource consumption increases

Engineering Contradiction:
Improveindividualized interface logicVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system performs self-service by automatically generating middleware code through parsing system output objects and applying grammar rules, eliminating the need for manual programming of individualized interface logic while maintaining adaptability to different systems and applications

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention uses copying by generating middleware code templates automatically from parsed system output objects, creating reusable interface logic that can be applied across multiple systems and applications without manual recreation

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If middleware is rewritten to accommodate software upgrades, then compatibility with new systems is achieved, but programming bugs are introduced and correction requires significant effort

Engineering Contradiction:
ImprovecompatibilityVSAvoidprogramming bugs
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs self-service by automatically regenerating middleware code through parsing updated system output objects, ensuring compatibility with new software versions while eliminating manual programming errors that introduce bugs

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention implements feedback by continuously parsing system output objects and using the parsed information to regenerate middleware code, creating a closed-loop system that automatically adapts to system changes and maintains reliability

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If extensive manual effort is used to create and maintain middleware, then individualized logic for each system can be implemented, but time and effort required increase

Engineering Contradiction:
Improveindividualized logicVSAvoidtime and effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically generating middleware code through parsing system output objects and applying grammar rules, eliminating the need for manual programming of individualized interface logic while maintaining adaptability to different systems and applications

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention uses copying by generating middleware code templates automatically from parsed system output objects, creating reusable interface logic that can be applied across multiple systems and applications without manual recreation

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9424003B1Schema-less system output object parser and code generator
Publication Date: 2016.08.23 EMC IP HLDG CO LLC
  • US9424003B1 patent drawing
  • US9424003B1 patent drawing
  • US9424003B1 patent drawing

AI summary

A schema-less system output object parser and code generation process analyzes an instance of a response object from a system, such as a storage array, having components of multiple different types, formats and communications protocols, and automatically generates middleware Java source code to translate and communicate requests and responses between the different components and client applications. Output response objects responding to application requests are annotated and parsed, and data structures are created and initialized with keys and key value variables to generate source code to handle live data.