Dynamic Message Flow Parameter Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise systems, changing design parameters for data management between applications often requires redeployment of the message flow program, leading to application downtime and the need for significant knowledge of integration tools, especially when the number of interfaces and design parameters are large.
Innovation Solution
A system and method for dynamically loading user-modifiable data conversion descriptions, including input parameters, data formats, conversion routines, and output information, without restarting the data conversion flow, using an application programming interface (API) to manage data transfer between applications, allowing for configuration changes without affecting the message flow program's properties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the message flow program is redeployed to change design parameters for data management between applications, then the design parameters can be updated, but application downtime occurs and significant knowledge of integration tools is required
Solution Approach 1:
The patent implements dynamic parameter modification by allowing the message flow program to load and update conversion parameters from external files (XML, JSON, YAML) during runtime without requiring program redeployment. The system dynamically parses these files and applies parameter changes to active message conversion operations, enabling adaptability while maintaining continuous operation.
Solution Approach 2:
The patent separates the message flow program from the conversion parameters by storing parameters in external configurable files rather than hardcoding them in the program. This segmentation allows parameters to be modified independently from the program code, enabling parameter updates without full program redeployment and reducing downtime.
2Adaptability or versatility
If the message flow program is redeployed to change design parameters, then the parameters can be modified, but extensive knowledge of integration tools is required
Solution Approach 1:
The patent enables self-service parameter modification by providing external configuration files with documented schemas that can be edited by users without requiring deep knowledge of the integration tool's internal mechanisms. The system automatically parses these standard format files and applies the changes, making parameter modification accessible to users with basic knowledge.
Solution Approach 2:
The patent introduces configuration files in standard formats (XML, JSON, YAML) as an intermediary between users and the message flow program. Users interact with these familiar, documented formats rather than the program's internal parameter structures, reducing the knowledge barrier while maintaining full parameter control capability.
3Adaptability or versatility
If the message flow program is redeployed when the number of interfaces and design parameters are large, then all parameters can be updated, but the complexity and time required for redeployment increases
Solution Approach 1:
The patent segments the large number of parameters into individual configuration files organized by interface or functional module. Each file contains only the parameters relevant to that specific interface, allowing selective updates of subsets of parameters without requiring complete system redeployment, thereby reducing complexity.
Solution Approach 2:
The patent implements validation and parsing of configuration files before they are applied to the running system. This preliminary action ensures that parameter changes are verified for correctness before deployment, preventing errors and reducing the need for corrective redeployment operations on complex systems.
Data Source
AI summary
A computer-implemented method for deploying a plurality of data conversion flow between a first application in a first system to a second application in a second system, without restarting the plurality of data conversation flow, is provided. The computer-implemented method may further include providing a plurality of modifiable data conversation that identifies a plurality of input parameters, a plurality of data formats, a plurality of data description, a plurality of conversation routines, a plurality of paths of the conversion routines, and a plurality of output information that determines routes of converted data for the first application. The computer-implemented method may further include converting the plurality of modifiable data conversion to form a data input from the first application to the second application. The computer-implemented method may further include providing an application interface for transmitting the plurality of modifiable data to the second application, without restarting the data conversion flow.