MI Client API  |  Mobile Solution Descriptor  |  Generic Synchronization  |  Smart Synchronization

 

Developing Mobile Solutions with SAP Mobile Infrastructure

Introduction

Mobile applications based on SAP Mobile Infrastructure always consist of a client- and a server-part. For both parts, MI offers certain base services and well-defined APIs and defines certain standards that applications need to conform with.

The Mobile Solution Descriptor (MSD) contains all information required to describe the different parts that form your mobile solution.

Client-side development

The client-side of a mobile application is developed in Java and uses the framework services offered by the MI Client API. The application is entirely controlled by the MI framework throughout its lifecycle: MI cares for installation, upgrade and de installation with its deployment strategy for mobile applications. MI also controls the initialization, display, hiding and destroying of a mobile application. The application itself is therefore living in a 'sand-box' furnished by MI.

The details of this approach are described in the JSP tutorials and the JSP and AWT chapters.

  • For any Java project, it is good practice to define project-wide coding conventions (for an example, see java.sun.com/docs/codeconv/).
  • The Eclipse IDE Java allows you to define code formatting rules for your project. See Window -> Preferences -> Java -> Code Formatter

Server-side development

Server-side development differs depending on which synchronization method you use: