You can migrate SAP® Mobile Platform 2.x Agentry applications, MBO applications, and OData applications to SAP Mobile Platform 3.0.
Although there are compelling reasons to upgrade to SAP Mobile Platform, version 3.0, and take advantage of the new features, migrating your applications may not always be the correct solution. If you want to migrate, you can choose between three high-level strategies: redeploy, redevelop, or redesign.
You can deploy a number of application types to SAP Mobile Platform Server version 3.0: Agentry, Mobiliser, and SAP Mobile Platform version 2.3. Agentry and Mobiliser applications are intrinsically supported in the main platform runtime.
No built-in upgrade support exists to migrate applications from version 2.x to version 3.0, so you must set up parallel infrastructure for a production environment, with a scheduled switchover. This may require you to redeploy application clients.
You may need to redevelop SAP Mobile Platform 2.x Mobile Business Object (MBO) applications, both native offline-able applications, and hybrid Web container applications using online MBOs. You may also need to redevelop applications that use HTTP and on-device portal (ODP).
The general theme of this approach is to keep certain aspects of an application, such as the existing client user interface and services, and replace the underlying communication and mobile-enabling services with the new SAP Mobile Platform 3.0 SDKs and services.
Sometimes when taking into consideration the cost-benefit analysis, with respect to applying migration strategies, it may be more cost effective to start from the beginning. In such cases, you need only consider migrating back-end services to be OData centric services, with Delta Token capabilities to support message-based delta synchronization