Developer

MBO and OData Architectural Differences

There are a considerable number of architectural differences between SAP Mobile Platform versions 2.<x> and 3.<x>.

This table summarizes the differences between SAP Mobile Platform versions 2.<x> and 3.<x> architectures.
Version 3.<x> Version 2.<x> Description
No caching database Cache database In a typical SAP Mobile Platform 2.<x> production environment, separate hardware runs the cache database, which is used for differencing and replication-based MBO synchronizations.
Settings are stored in database and files Settings are stored in database and files In version 2.<x>, some settings are stored in the cluster database, but most settings are stored in files that must be synchronized across the cluster.
Runs in SAP Light Java Server Mix of x86 and Java runtime The version 2.<x> servers runs only on Windows-based machines. Because SAP Mobile Platform 3.<x> runs in SAP Light Java Server, you can install it on a range of Linux and Unix servers as well.
Service packages are managed by OSGi Custom service and package management Ease of middleware services management on an SAP Mobile Platform Server version 3.<x>. Administrators can also install custom service packages/features, allowing them to deploy services to mobile platforms.
HTTP/HTTPS Custom protocols SAP Mobile Platform3.<x> strives to standardize on network protocols
Support for standard reverse proxies Some support for reverse proxies, but SAP recommends Relay Server  
Integration services are deferred to NetWeaver Gateway or Integration Gateway Integration is part of MBO design