Data Orchestration Engine Middleware for CRM ERP Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current middleware solutions, such as CRM middleware, are inadequate for facilitating data exchange between field applications and third systems like ERP systems, lacking essential features like data replication, delta comparison, and key mapping, which are necessary for seamless data exchange in business transactions.
Innovation Solution
The implementation of a Data Orchestration Engine (DOE) middleware that bridges communication between disparate systems by converting backend communication protocols and enabling push-pull data replication, remote function calls, and key mapping services, allowing data exchange between CRM and ERP systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If CRM middleware is used for data exchange between field applications and servers, then communication between CRM server and field applications is enabled, but data exchange with third systems like ERP is not supported
Solution Approach 1:
The system is divided into two distinct middleware components: CRM middleware for handling field application communications and DOE middleware for managing third-system data exchange. This segmentation allows each middleware to specialize in its specific function, enabling the CRM middleware to maintain its existing reliable communication patterns while the DOE middleware provides the missing ERP integration capabilities through pull mechanisms, key mapping, and delta comparison.
Solution Approach 2:
The DOE middleware acts as an intermediary between the CRM middleware and third systems like ERP. It receives data exchange requests from the CRM middleware, performs the necessary data replication, key mapping, and delta comparison with the third system, then returns the processed data to the CRM middleware. This intermediary approach enables CRM applications to access third-system data without requiring the CRM middleware itself to have direct third-system integration capabilities.
2Ease of operation
If existing middleware is used, then simple data exchange between connected systems is possible, but advanced features like pull mechanism, key mapping, and delta comparison are missing
Solution Approach 1:
The DOE middleware combines multiple advanced data exchange functionalities into a single integrated system: pull mechanism for initiating data requests, key mapping for translating between different system data formats, delta comparison for identifying changes, and document handling for managing business transactions. This merging of functions allows the system to maintain operational simplicity while providing comprehensive advanced features that work together seamlessly.
3Adaptability or versatility
If middleware functionality is extended to support third systems, then data exchange capability improves, but system complexity increases
Solution Approach 1:
The architecture is segmented into two middleware layers with clearly defined responsibilities. The CRM middleware maintains its original simple design for field application communication, while the DOE middleware handles all complex third-system integration tasks. This segmentation prevents complexity from propagating to the CRM middleware, allowing it to remain easy to operate while the system as a whole gains enhanced adaptability through the DOE's specialized capabilities.
Data Source
AI summary
Methods, systems, and computer-readable medium storing instructions thereon for implementing methods are directed to facilitating data exchange, such as accessing and operating on data objects, between field applications, such as mobile clients, and dedicated servers by leveraging the features of middleware. An embodiment includes a first server providing a first set of services and data to a mobile client. A first communicating middleware is connected between the first server and the mobile client according to a first communication functionality. A second server provides a second set of services and data according to a second communication functionality that is different from the first communication functionality. A second middleware communicates with the second server according to the second communication functionality, and communicates with the first middleware according to the first communication functionality. The second middleware is connected to the second server and the first middleware.