Universal Application Network Interface for Integration Portability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business processes developed for integration servers and applications require numerous versions to accommodate different integration servers and applications, leading to resource-intensive development and limited portability across platforms.
Innovation Solution
The Universal Application Network (UAN) provides a common service interface independent of integration servers and applications, allowing integration processes to be developed once and executed on any supporting server without modification, using translators and transforms to ensure compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If business processes are developed to support multiple integration servers and applications, then the number of business process versions increases exponentially, but development resources and maintenance complexity increase significantly
Solution Approach 1:
The patent segments the business process into two distinct layers: a platform-independent business logic layer and a platform-specific integration layer. The business process definition is separated from the integration server and application-specific implementations, allowing the core business logic to remain unchanged while adapting to different platforms through separate binding layers.
Solution Approach 2:
The patent creates a universal business process interface that can interact with multiple different integration servers and applications through a common abstraction layer. This universal interface enables a single business process version to serve multiple platforms by translating platform-specific variations through standardized service bindings.
2Adaptability or versatility
If multiple versions of business processes are developed to accommodate different integration servers and applications, then platform compatibility is improved, but development time and costs increase
Solution Approach 1:
The patent establishes platform bindings and integration server interfaces in advance, creating a predefined framework that accommodates different platforms. This preliminary setup allows business processes to be developed once against the standardized interface, with platform-specific adaptations already prepared through the binding layer configuration.
Solution Approach 2:
The patent introduces an intermediary binding layer that mediates between the universal business process interface and platform-specific integration servers. This intermediary translates and adapts communications without requiring modifications to the core business process logic, enabling seamless multi-platform support.
3Adaptability or versatility
If enterprises switch integration servers or applications, then access to new technology is enabled, but business process compatibility must be re-established
Solution Approach 1:
The universal business process interface designed in the patent can interact with multiple integration servers and applications through standardized bindings. When an enterprise switches integration servers, the same business process version can continue to function by leveraging the platform-independent interface and the binding layer's ability to adapt to different underlying systems.
Solution Approach 2:
The patent implements dynamic binding capabilities that allow the system to adapt to different integration servers at runtime. The binding layer can dynamically resolve and connect to different integration server implementations based on configuration, enabling seamless transitions without requiring static, hard-coded connections to specific platforms.
Data Source
AI summary
A method and system for providing an integration environment in which integration processes can be developed independent of integration servers and applications. The integration environment provides an application service interface for each application that is independent of the integration servers. An integration process that is developed to use the application service interface is compatible with any integration server that supports the applications that the integration process accesses. The integration environment provides a common service interface for each type of application. The common service interface is independent of the application that is providing the service and is also independent of the integration server. Thus, an integration process developed to use the common service interface is compatible with any application of the appropriate type and any integration server.