Automated Custom Connector Generation from Swagger API Specifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software development and deployment models deliver generic software applications that require extensive configuration and customization by users or programmers, leading to time-consuming and costly processes for integrating diverse software applications and systems within and across enterprises.
Innovation Solution
A system and method for automated generation of custom connector visual elements using Swagger-compliant APIs, allowing users to model integration processes without writing code, by parsing API instructions to identify data locations, actions, and data elements, and generating a custom connector code set for execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If generic software applications are used, then software deployment is simplified, but extensive configuration and customization are required leading to time-consuming and costly integration processes
Solution Approach 1:
The system enables self-service automated generation of integration elements by parsing Swagger API specifications automatically. The generator creates custom connector visual elements without requiring manual configuration by users or programmers, allowing the system to serve itself in creating integration components.
Solution Approach 2:
The system performs preliminary action by pre-generating integration elements from API specifications before actual integration is needed. By parsing the Swagger specification in advance and creating ready-to-use visual elements, the system eliminates the need for time-consuming on-demand configuration and customization.
2Adaptability or versatility
If manual configuration and programming are used for integration, then customization is achieved, but the process becomes time-consuming and costly
Solution Approach 1:
The system replaces the mechanical process of manual configuration and programming with an automated computational system. The generator automatically parses Swagger API specifications and generates custom connector visual elements, substituting human manual work with automated code analysis and generation.
Solution Approach 2:
The system introduces an intermediary automated generator that acts as a mediator between the Swagger API specification and the integration elements. This intermediary automatically translates API specifications into usable integration components, eliminating the need for direct manual programming while maintaining full customization capability.
3Productivity
If custom integration elements are generated automatically, then integration efficiency is improved, but complexity in parsing and generating code increases
Solution Approach 1:
The system achieves universality by creating a multi-functional generator that can handle multiple Swagger API specifications and generate various types of integration elements through a single unified system. The generator parses different API formats and produces appropriate visual elements, reducing the need for multiple specialized tools.
Data Source
AI summary
An information handling system a processor receiving an open-standard format file describing code instructions of a Swagger custom API, the processor parsing the file to identify a first Swagger parameter object whose location is defined by a first Swagger path object, a memory for storing a first Swagger operation object and for storing a customized software integration application enabling electronic data exchange comprising a plurality of connector code sets, each of the connector code sets being associated with an integration modeling element selected to generate a customized integration flow model of the specific integration process, wherein the integration modeling element selected is a custom connector integration element associated with a custom connector code sets including the first Swagger operation object acting on the first Swagger parameter object, and the processor transmitting an executable run-time engine and the custom connector code set for execution at an execution location.


