Cross-Domain JavaScript Library for Mashup Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing approaches to establish communication channels between front-end applications and back-end data services in web-enabled scenarios are complex and inefficient, particularly due to issues like SSL certificate synchronization and lack of temporary business object support, which hinder effective handling of business application transaction use cases, especially with third-party services.
Innovation Solution
A cross-domain JavaScript library is deployed in the browser environment to facilitate bidirectional communications between mashup components and third-party services using socket channels, enabling the exposure and updating of business data objects and context changes across domains without requiring back-end connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If extensive integration and modification are performed to establish communication channels between front-end applications and back-end data services, then data operations can be properly handled, but device complexity and processing overhead increase significantly
Solution Approach 1:
The patent introduces a communication channel abstraction layer that acts as an intermediary between front-end applications and back-end data services. This intermediary layer provides standardized methods for data retrieval and updates, eliminating the need for extensive direct integration code in each application while maintaining proper data operation handling capabilities.
Solution Approach 2:
The communication channel is designed with universal methods that can handle multiple data operation types (retrieve, update, create, delete) through a single interface. This multi-functional approach reduces integration complexity by allowing one communication channel implementation to serve multiple purposes across different front-end applications.
2Reliability
If SSL certificate synchronization is performed between front-end applications and back-end data services, then secure communications are established, but processing overhead increases
Solution Approach 1:
The patent performs SSL certificate synchronization and security authentication in advance during the communication channel establishment phase, rather than continuously during data operations. This preliminary action ensures secure communications are established once, reducing processing overhead during subsequent data retrieval and update operations.
3Reliability
If temporary business object support is added before modifications are saved, then data consistency is improved, but device complexity increases
Solution Approach 1:
The patent creates temporary business object representations in the communication channel that copy the structure and methods of permanent business objects. These temporary objects allow data consistency handling during transmission and processing without requiring full permanent object support, reducing complexity while maintaining data consistency.
4Reliability
If existing approaches modify front-end applications or back-end services to handle transactions, then integration is achieved, but adaptability to third-party services is reduced
Solution Approach 1:
The patent segments the communication channel into independent components that can be separately configured and extended. This segmentation allows the core transaction handling mechanisms to remain stable while enabling flexible integration with third-party services through configurable adapters and protocols without modifying existing front-end or back-end applications.
Data Source
AI summary
Techniques and configurations for establishing cross-domain communications between a business application, a third party website or service, and mashup components of a mashup user interface are generally described herein. In one example embodiment, a scripting library which establishes socket connections between domains and between components of a common mashup user interface is included or referenced in a mashup component and in a third party component that are displayed in the common browser-based mashup user interface. A scripting library executing in the browser may be used to establish and control the socket connections that communicate changes to the business application data, transmitted from the third party webpage to the mashup. The changes to the business application data, communicated and received in front-end objects, then may be processed or further communicated for persistence at the business application.