Migrating Hybrid Web Container Apps
If you upgrade SAP Mobile Platform version 2.3 to version 3.0, you can migrate your Hybrid Web Container (HWC) apps to Cordoba apps.
- Both are hybrid app solutions that use HTML for the UI; you can use any HTML UI library to develop a hybrid app.
- Both run on multiple devices, Android and iOS.
- You can update deployed hybrid apps; in SAP Mobile Platform 3.0, use the Kapsel AppUpdate plug-in.
- Containers can be password protected; in SAP Mobile Platform 3.0, the Kapsel Logon plug-in and the password policy provide the pass code screen.
The differences between HWC apps and Cordoba apps are described in the table, below:
|SAP Mobile Platform 2.3 HWC Apps||SAP Mobile Platform 3.0 Cordoba Apps|
|The Hybrid Web Container is proprietary and includes Cordova.||Kapsel plug-ins are standard Cordova plug-ins that you can add to a Cordova project.|
|HWCs host applications that communicate with SAP Mobile Platform Server via the Messaging-Based Synchronization protocol; requests and responses are in XML. Messages in a queue enable apps to run while devices are offline.|
|HWCs can host multiple apps.||A hybrid app is a single application; if you launch a hybrid app from the Fiori Launchpad, it appears as multiple applications.|
|An HWC has an inbox and calls appropriate apps for incoming messages; it handles simple workflows such as approving purchase orders, and native notification.||Hybrid apps handle native notifications via the Kapsel Push plug-in.|
|An SAP Mobile Platform 2.3 SP04 HWC supports Windows Mobile 6.x, BlackBerry 6 and 7, Android 3.0–4.4, and Apple iOS 5.0–7.0.||Kapsel plug-ins are supported on Android 4.0–4.4 and Apple iOS 6 and 7.|
|HWCs use Cordova 2.0.||SAP Mobile Platform 3.0 SP04 Kapsel plug-ins are compatible with Cordova 3.4.|
|Applications that you develop with Hybrid App Designer (HAD) for HWC use jQuery Mobile.||HAD is not available in version 3.0; SAP recommends using the SAPUI5 library; you can use the River Definition Environment to create SAPUI5 apps.|
|Use Eclipse tooling to create Mobile Business Objects for a layer of abstraction to access enterprise data sources such as JDBC, REST, and SAP JCo.||Use SAP Integration Gateway to enable JDBC and other enterprise sources such as OData services.|
|Offline use cases; for example, an offline device can submit a request, which is queued, then sent the next time the device has connectivity. An on-device cache saves results from read requests, and returns the results if the same request is made when the device is offline.||In SAP Mobile Platform 3.0 SP05, a Kapsel plug-in supports offline OData requests with full create, read, update, delete (CRUD) support.|
To see a sample implementation of an OData app that you can run in a browser, and how to run a similar app in SAP Mobile Platform versions 2.3 and 3.0, see http://scn.sap.com/docs/DOC-57873.