Semantic Element Mapping for Application Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating applications with an enterprise system is complex due to differing characteristics and requirements, leading to increased time, cost, and difficulty in maintaining and scaling integrations, as well as limitations in collaboration, synchronization, and review processes.
Innovation Solution
A system comprising processors, a definition module, a data store, and a workflow module that determines and maps semantic elements between application interfaces, integrates these interfaces with an enterprise service bus, and provides visualization and approval mechanisms to manage the integration process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If applications are integrated with enterprise systems using traditional methods, then integration functionality is achieved, but integration complexity and time requirements increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-defining semantic elements and their mappings in a centralized repository before actual integration occurs. Interface control documents and semantic element definitions are prepared in advance, allowing integration to proceed by simply referencing pre-established mappings rather than creating them during integration execution.
Solution Approach 2:
The patent uses copying by creating and storing template definitions of semantic elements, interface control documents, and mapping relationships in a centralized repository. These templates can be reused across multiple integrations, allowing the system to copy proven mappings and interface definitions rather than recreating them each time.
2Manufacturing precision
If detailed semantic mappings are created for application integration, then integration accuracy improves, but the complexity of defining and maintaining mappings increases
Solution Approach 1:
The patent applies universality by creating a centralized repository that serves multiple functions: storing semantic element definitions, maintaining mapping relationships, providing visualization tools, and supporting collaboration workflows. This single multi-functional system replaces multiple separate tools and processes that would otherwise be needed.
Solution Approach 2:
The patent uses an intermediary approach by introducing a centralized repository as a mediator between application interfaces and enterprise systems. The repository stores and manages semantic element mappings, acting as an intermediary layer that simplifies the integration process by handling the complexity of mapping management centrally rather than at each integration point.
3Adaptability or versatility
If traditional integration methods are used, then basic integration functionality is achieved, but collaboration and synchronization capabilities are limited
Solution Approach 1:
The patent applies merging by combining multiple previously separate functions into a single integrated system: semantic element definition, mapping creation and management, interface control document storage, visualization, and collaboration workflows are all merged into one centralized repository system, enabling enhanced collaboration without requiring multiple separate tools.
Data Source
AI summary
An example implementation includes a system having one or more processors, a definition module, a data store, and a workflow module. The definition module is executable by the one or more processors to determine a first semantic element for a first operation included in a first application interface representing a first service and a second semantic element for a second operation included in a second application interface representing a second service, such as an enterprise service bus. The definition module may further determine a mapping of the first semantic element with the second sematic element. The data store is configured to store the mapping of the first semantic element with the second sematic element by the definition module. The workflow module is executable by the one or more processors to integrate the first application interface with the second service based on the mapping.