Data Orchestration Engine

The Data Orchestration Engine (DOE) allows data exchange between the back-end systems and mobile devices. It primarily consists of the following components: Design Time You need to define the required DOE metadata to stage data from the back-end system and subsequently distribute this data to mobile devices. The design time component provides tools that allow you to define this metadata. After you have defined the metadata, the metadata definition completely governs the processing of data within the DOE completely. Runtime This is core engine that performs the data consolidation and data distribution to and from back-end systems and mobile devices. The runtime primarily comprises the flow controller, inbound and outbound handlers, and core DOE services. Administration and Monitoring In a mobile scenario, the number of mobile devices is in multiple of thousands. The system administrator must set up these devices, define data distribution rules, monitor the processing within the DOE, and handle errors wherever required. The administration and monitoring components allow the administrator to efficiently manage the entire system landscape. Back-End Adapter This component allows integration between the DOE and the back-end systems both at design time and runtime. The following figure displays the architecture of the DOE.

.

Client doesn't hold the entire data which is present in the backend system. It will contain the data which is required (Distributed by DOE as per distribution rules) by the user. . So.Data Staging: CDS replicates the data which is present in backend system. CDS always refers to backend system to verify the correctness of the data.

Sign up to vote on this title
UsefulNot useful