Start of Content Area

Function documentation Synchronization Locate the document in its SAP Library structure

Use

Synchronization ensures a safe and compressed transfer of data between the mobile device and the back end. Modified data is transferred from the mobile device to the back end and vice versa, so that both the mobile device and the back end have the most up-to-date data.

Features

     Secure Data Transfer

Synchronization uses the HyperText Transfer Protocol (HTTP) for the data transfer, where the Secure Sockets Layer (HTTPS) can be optionally activated.

To transfer data in this way, you require a TCP/IP connection between the mobile device and the SAP MI Server Component.

All standard connection types, such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Local Area Network (LAN), Wireless LAN and Cradles are supported.

     Compressed Data Transfer

When data compression is activated, the data transferred from the mobile device to the SAP MI Server Component and in reverse is automatically compressed. The compression uses the GZIP standard algorithm with level five.

     Data Packaging

The synchronization layer of the SAP MI Client Component stores all the data to be synchronized in a queue. Data packaging divides the queues into smaller data packages. The data packages are transferred one after the other. This ensures optimal transmission of your data, even if the quality of the connection is not good. For more information, see Parameters for Data Packaging.

     Optimal Behavior if the Connection Breaks

All existing data packages are transferred during synchronization. The SAP MI package manager makes sure that no data packages are lost if the connection breaks. Only those data packages that were not yet sent are transferred during the next synchronization. For more information, see Parameters for Repetitive Synchronization.

     Synchronous and Asynchronous Processing of Transferred Data

The data transferred from the mobile device to the SAP MI Server Component and in the reverse direction can be processed either synchronously or asynchronously.

     With synchronous processing, the data is posted during synchronization. The data returned from the posting is transferred to the mobile device in the same synchronization step and is immediately available to the mobile application.

     With asynchronous processing, the data posting is started by a background job. The data returned from the posting is transferred to the mobile device during the next synchronization. Since the data is not posted during synchronization, you can expect a short synchronization time.

     Synchronization By Data Carrier

You can synchronize with the back-end data from the mobile device that either you or the end user stored on data carriers. The synchronized back-end data is returned in a file and is used as input for the mobile device. The input file is imported to the mobile device from the data carrier. For more information, see Parameters for Data Carrier Synchronization.

     Automatic Synchronization

SAP MI can be set so that synchronization is automatically started in the background at defined time intervals.

     Support of Multiple Back-End Systems (SAP and External Systems)

When the data packages are transferred, the SAP MI Server Component automatically defines which data package is posted to which back-end system. SAP Systems with any release can be addressed with RFC connections. The SAP Business Connector is used to connect to external systems.

 

End of Content Area