There are a considerable number of architectural differences between SAP Mobile Platform versions 2.x and 3.x.
| Version 3.0 | Version 2.x | Notes |
|---|---|---|
| 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 | 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. Note: SAP Mobile Platform 3.0
does not provide cluster support.
|
| 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.0 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 | This is also a great differentiator making it much easier to manage the middleware services on an SAP Mobile Platform 3.0 server. You can also install custom service packages, allowing you to deploy services to mobile platforms. These packages are referred to as features within the platform, and administrators can manage them. |
| HTTP/HTTPS | Custom protocols | One goal of SAP Mobile Platform3 is 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 Gateway For Java | Integration is part of MBO design |