Unwired Server manages synchronization in a transactional loops: the device and Unwired Server exchange, and Unwired Server and data source exchange. However mediating both transaction loops is the consolidated database.
The interaction among the Unwired Server, consolidated database, data source repository, and compact remote databases used by a device application can best be illustrated as follows:
Data operations from the device managed by business objects and the Unwired Server
Transactions performed between Unwired Server and devices are meant to perform the operations programmed in the mobile business object (MBO). Data reconciliation only occurs if the developer has incorporated the appropriate validation logic in the operation code itself. In a typical deployment:
- Unwired Server downloads data from one or more device application to the consolidated database.
- If multiple changes occur more or less concurrently, changes are reconciled and aggregated in the consolidated database until Unwired Server can synchronize changes back into the EIS data source on the corporate network.
Data distribution between Unwired Server and the data source
Transactions performed between the data source and Unwired Server is to keep data current and fresh in both the data source repository and the consolidated database:
- Based on the data refresh schedule created by the administrator, the Unwired Server compares data in the consolidated database with data source repository.
- If changes are detected changes in the data source are uploaded, and changes from the consolidated database are downloaded to the client database via synchronization.