Integration Application Building Tool Automates Enterprise Adapter Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating disparate processing systems in enterprise systems often requires custom code, making it complex and expertise-dependent for developers to set up and manage communication through standard messaging systems.
Innovation Solution
The integration application building tools automatically build and deploy integration applications by receiving limited, installation-specific information from users and providing necessary data, simplifying the setup process by using an integration bus with adapter applications and a messaging system like JMS, enabling communication between various enterprise applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers write custom computer code to integrate processing systems with the messaging system, then the integration can be tailored to specific systems, but the complexity and expertise requirement increase significantly
Solution Approach 1:
The patent uses template copying to generate adapter applications. Instead of requiring developers to write custom code from scratch, the system copies predefined template code and automatically fills in system-specific details (like JMS provider names, message queue identifiers, and connection parameters). This produces customized integration code without requiring developers to create it manually, thus reducing complexity while maintaining adaptability to different processing systems.
Solution Approach 2:
The integration system performs self-configuration by automatically generating adapter applications based on template files and system parameters. The system serves itself by automatically creating the necessary integration code, configuring message queues, and setting up connections without requiring developer intervention in the actual code generation process. This self-service approach eliminates the need for complex manual coding while still allowing customization through template selection and parameter configuration.
2Reliability
If developers manually set up and manage integration applications, then they can ensure proper configuration, but the time required and expertise needed increase
Solution Approach 1:
The patent implements preliminary action by pre-configuring template files with predefined structures for adapter applications. These templates include pre-written code frameworks, configuration schemas, and error-handling logic that are prepared in advance. When an integration is needed, the system automatically instantiates the appropriate template with system-specific parameters, eliminating the need for developers to manually configure everything from scratch. This preliminary preparation ensures configuration accuracy while dramatically reducing setup time.
Solution Approach 2:
The patent replaces the mechanical process of manual code writing and configuration with an automated computational process. Instead of developers manually creating adapter applications and configuring message queues, the system uses computer-based template processing to automatically generate and deploy integration applications. This substitution of manual mechanical work with automated computational generation maintains configuration accuracy through template validation while reducing setup time from hours to minutes.
3Adaptability or versatility
If the integration system requires installation-specific information from users, then the integration can be customized to the specific environment, but the user expertise requirement increases
Solution Approach 1:
The patent introduces template files as intermediaries between the user and the complex integration configuration. These templates act as mediators that translate simple user inputs (like selecting a template type and providing basic connection information) into complex, customized adapter applications. The template intermediary handles the complexity of code generation and configuration translation, allowing users with minimal expertise to achieve installation-specific customization without needing to understand the underlying technical complexities.
Solution Approach 2:
The system uses parameter changes to customize integrations. Instead of requiring users to modify complex code structures, the system provides standardized templates and allows customization through parameter changes in configuration files or metadata. Users can specify installation-specific parameters such as server addresses, message queue names, and authentication credentials, and the system automatically adjusts the adapter application parameters accordingly. This parameter-based customization approach maintains adaptability to specific environments while keeping the user interface simple and expertise requirements low.
Data Source
AI summary
Systems, methods, and other embodiments associated with an integration application building tool are described. In one embodiment, a method includes providing data files including an adapter data file, a flow data file, and an environment data file. The adapter data file stores adapter data corresponding to a plurality of adapters for respective enterprise applications. An adapter for a given enterprise application enables the given enterprise application to exchange messages with a messaging system. The flow data file describes to a plurality of flows of messages, through the messaging system, between enterprise applications. The environment data file is configured to be populated with location data. The method includes, receiving an instance of location data and populating the environment data file. An adapter application comprising computer code is generated that, when executed, allows the enterprise application to exchange messages with the messaging system. The adapter application is deployed on integration bus hardware.