Best Practices for Migrating Applications

When you upgrade to the latest version of SAP Mobile Platform, client applications continue to run without migrating them. In some cases, adjustments are required to ensure the application runs correctly; and in cases where the client application is based on mobile business objects, the project needs to be started in the Mobile Application Diagram to automatically trigger project migration steps. But overall, the client application continues to run and can synchronize with its enterprise information system. Any exceptions are noted in the documentation.

A client application is compiled code that is based on its data model, and consists of a binary piece, and an SAP Mobile Server piece. This enables the application to execute on devices and in the server. Over time, features are added and improvements made to the SDK and SAP Mobile Server. To take advantage of these improvements, you need to upgrade your server, or implement a more recent SDK version.

If you rely only on in-place migration, after multiple server upgrades your client application may cease to work efficiently or at all. A best practice is to recompile your client application code after a major release, so that the binary and SAP Mobile Server versions are the latest. One strategy is to wait several weeks to ensure the upgraded environment is stable, and then recompile.