Augmenting Middleware Communication Services for Enterprise Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integration of enterprise application functionality and data with middleware platforms is challenging due to fragility of objects and services, and the distinct nature of development teams for enterprise applications, middleware platforms, and mobile applications, leading to negative impacts on middleware and mobile application performance when changes are made.
Innovation Solution
Implementing augmenting middleware communication services that provide generic communication capabilities between enterprise applications and middleware platforms, allowing for standardized data and functionality access by mobile applications, thereby minimizing the need for specific integration coding and ensuring changes do not affect middleware or mobile application performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If direct integration between enterprise application and middleware platform is implemented, then access to enterprise data and functionality is enabled, but the system becomes fragile and easily broken when changes are made
Solution Approach 1:
The patent introduces configuration data as an intermediary layer between the enterprise application and middleware platform. This configuration data stores identifiers of data items and application services that are enabled for utilization, acting as a buffer that absorbs changes in the enterprise application without directly impacting the middleware platform. The services refer to this configuration data before transmitting information, ensuring stable integration while maintaining adaptability.
Solution Approach 2:
The patent segments the integration architecture by separating the enterprise application layer, the configuration data layer, and the middleware platform layer. This segmentation allows each layer to be modified independently - changes in the enterprise application do not directly affect the middleware platform, as long as the configuration data is properly updated. This resolves the contradiction by enabling adaptability at the configuration level while maintaining reliability at the platform level.
2Productivity
If tight coupling between enterprise application and middleware platform is used, then functionality access is direct, but changes in enterprise application negatively affect middleware platform services
Solution Approach 1:
The configuration data serves as a mediator that decouples the enterprise application from the middleware platform. Services can efficiently access functionality through this intermediary by referring to the configuration data that identifies enabled data items and services. This maintains productivity while improving adaptability, as changes in the enterprise application only require updates to the configuration data rather than direct modifications to the middleware platform.
3Manufacturing precision
If specific integration coding is required for each enterprise application, then precise control is achieved, but development and maintenance complexity increases
Solution Approach 1:
The patent implements a universal configuration data structure that can accommodate multiple enterprise applications and middleware objects. This configuration data stores identifiers of data items and application services in a standardized format, allowing the same integration mechanism to serve multiple purposes. This reduces integration complexity while maintaining precise control, as the universal configuration approach eliminates the need for application-specific integration code for each new enterprise application.
Data Source
AI summary
Various embodiments herein include one or more of systems, methods, and software providing augmenting middleware communication services. Embodiments generally include services executable to provide communication capabilities between a middleware platform and an application, such as an enterprise-class application, to facilitate access to data and functionality of the application by mobile applications that access application functionality and data via the middleware platform. Some embodiments include augmenting the application with at least one service to receive a call from a middleware object requesting data and to identify data to be included in a response to the request. The identified data may then be retrieved and returned to the calling middleware object. The call of the middleware object is typically received from a mobile device application and the middleware object provides data received in response to the request to the mobile application.