I wrote couple of blogs in the past
1. Qualities Required for a Successful Enterprise Mobile Solution
2. SAP Sybase Co-innovation Platform for Enterprise Mobility
In the second blog, I wrote a brief introduction to the responsibility separation between SAP and Sybase components so that power of enterprise and mobility are integrated seamlessly. There were few questions around multiple boxes and overlaps. In this blog I am trying to give the next level of details to explain the core problems solved by Data Orchestration Engine (Server component of NW Mobile 7.1) that is used in the SAP Sybase co-innovation platform.
Recap on Responsibilities
DOE Responsibilities
- Business data responsibility determination
- Business data integrity
- Business data synchronization with delta handling and multiple version handling
- Business information direct access (like opportunity lookup)
- Server side programming model and development/customizing environment
SUP Responsibilities
- Native application & application development infrastructure for client
- Messaging and connectivity to the device
- Device management
- PIM synchronization
Joint Responsibilities
- End-2-end lifecycle management for deployment, version control and trouble shooting
- End-2-end integrated application dev and customization programming model
Capabilities Provided by DOE
Table below provides the core problem solved by DOE in this SAP Sybase Co-innovation Platform for Enterprise Mobility. Essentially DOE helps in provisioning enterprise business information in the context of mobility world. Provisioned information is then utilized by the device centric world and embedded in the context of mobile usage. This component tackles mobile related technical challenges for accessing business information from a OLTP and OLAP systems.
Solution Quality (Information access relevant) | Required Capability (that is provided by DOE) |
Seamless offline / online | - Responsibility determination (who needs to get what based on rules and dependencies)
- Keep the device in sync with required data in near real time (Inserts, updates and deletes to remove unwanted data)
- Transparent connectivity for both asynchronous and synchronous access - Unified programming and configuration models
- Data integrity handling - Conflict detection and resolution, error compensation, Key mapping, referential integrity
|
Efficient bandwidth utilization support | - Solve the data integrity side effects created by local caching on the device (keep information in sync, conflicts, Asynchronous confirmation/rejections to local modifications, key mapping etc.,)
- Only relevant modified data (at field level) needs to be synchronized and needs to be push based (end to end event driven)è Maintains the inventory of who has received what, then only delta detection is feasible without adding load on backend
|
Flexibility: Model Reuse across multiple scenarios & customizable pattern based data push (Sample Scenarios) | - Flexible time window based distribution (E.g. Activities within the time window of 10 days before and 10 days after) - Critical for supporting small devices due to memory constraints and its usage pattern
- Flexibility in organizing the workforce (E.g. Switching from territory based sales force to product line based sales force should be flexible and fast) - Will result in realignment of data with relevant deletes and inserts (Otherwise impacts bandwidth utilization as well)
- Fast realignment of data in case of business process change - Needs to know who has got what data
- Model re-usage for different scenarios è Entity that is created once can be used in different applications without re-development with versioning support
|
Lifecycle management support for business data and process for enterprise mobility | - Support for rollout, recovery of data without putting load on backend
- Support for phased upgrade - Multiple version handling for messages and data
- End to end support for monitoring and troubleshooting
|