A system for the usage type MI consists of the following elements:
SAP NetWeaver Application Server with usage type MI contains AS JAVA and AS ABAP. It is responsible for the following tasks:
? It is responsible for the queuing and acknowledgment of synchronized data containers and for calling the application in the back-end system (AS ABAP).
? As part of data replication, it defines data packages for individual mobile devices (data allocation), determines the data to be newly replicated on the device (delta synchronization), finds and solves conflicts between the mobile device and the server application (conflict management) and provides a number of monitoring tools.
? It determines the exchange of data between the server and the mobile device and the deployment of applications on the mobile device. With the Software Deployment Manager, the standard tool from SAP NetWeaver is used for deployment.
? It provides functions in the SAP NetWeaver Mobile Administrator to manage the mobile devices and the mobile components (AS JAVA).
The client provides services on the mobile device for the mobile applications.
? UI programming model
The standard programming model for mobile applications is Java Server Pages (JSP). Alternatively, you can also use the Abstract Window Toolkit (AWT) as a pure Java programming model. The SAP ME 1.0 programming model microITS is still supported.
? Framework services
The framework services are provided to the mobile applications as Java APIs. The most important APIs are used for
0 Data synchronization
0 Data persistence
0 Reading and writing replicated data
0 Logging and tracing
0 Configuration of applications and framework
The back end of a mobile application comprises Customizing and repository objects. Both kinds of objects are transported using the standard mechanisms of the SAP Change & Transport System.