Data Collectors for Mobile Clients 

Use

Data collectors are internal data recipients. In a Data Collector, data is not processed but is simply collected. Typically, BDoc messages are collected for a mobile client.

Normally, synchronization services place all messages immediately in the queue of the respective recipient. If a large quantity of update messages need to be processed in a short time, this results in a very large data volume because a message must be sent for each update.

You can avoid this by using Data Collectors. The data collector collects all BDoc messages of a particular object type. The data is then extracted periodically in consolidated bulk messages. This substantially reduces the data volume in the outbound queue for the mobile client. This applies particularly to object type instances that are updated frequently.

Using Data Collectors also means that BDoc messages for the mobile client are no longer available as soon as they have been processed. The messages become available again after the next extraction job.

If you want to use Data Collectors, you must create them earlier in the Administration Console for the different object types. Periodic extraction jobs are used to extract data. Ideally, these jobs are called once daily before the mobile client user logs on to retrieve data.