Skip to Content
0
Oct 18, 2005 at 04:24 PM

Grasping the SyncBo concept

19 Views

Hi there,

I am completely new in the area of SAP Mobile infrastructure ( but have sufficient background in other SAP/J2EE technologies ) and after reading the MDK 2.5 documentation I was wondering about the "SyncBo" technology which hopefully one of the experts here has some thoughts upon ...

If you would create a custom mobile application which uses some business objects from an SAP backend system and I want to achieve a smart synchronisation then I need to define "SyncBo" and write the necesary BAPI wrappers, etc ... all fine and understood.

I was actually wondering whether the web application would use the synchronised objects "as is" - meaning that you would query them to interact with the enduser OR would you actually let your web application use the peristence API to store custom objects and have a separate application convert the "SyncBO" objects towards your custom objects and storage mechanisme ...

I foresee that you use the persistance API to store configuration data, etc ... which is locally to the application BUT I am wondering about the "Business Objects" ...

What is confusing me probably is the fact that it seems that the application itself is apparently responsible for managing the (delta) synchronisation by using the SmartSync API classes and for example register itself upon the events ...

Would a typical more complicated application use a combination of both techniaques or would you end-up having 2 applications - 1 for handling the synchronisation and data conversion to local objects and 1 which is the "real" application which works entirely on local object?

My guts feeling says it should be option 1 ...

Any thoughts or feedback would be appreciated,

Regards,

S