I'm new to SAP Mobility, and I have just started exploring about it. I know you can develop apps in different ways using SUP. Now I read at many places that Hybrid App's cannot be a complete offline App at the same time it is stated that they can do synchronization by storing events in a queue.
Can some one tell me what this means? What is a complete offline app? why cant it be build as a Hybrid app?
Thanks and Regards,
you can use a Offline App without a connection to the internet. So this means that you have to load (e.g. if you have a connection) and store your data on the device.
As the name "Online App" says, this kind of app needs a connection to the internet.
A Hybrid App is limited in using the device hardware. So, it is also limited in storing your data on the device, which is needed for an complete offline szenario.
Thanks a Lot for your reply. So does that mean that I should not use Hybrid App if its an offline scenario?
I have another doubt, is data stored in SUP's cache or Device Memory? If it can be stored in Device Memory why do we need SUP CDB???
Sorry If the question is silly, Im trying to learn this but currently I dont have a system access, so its a bit difficult to understand these things.
Hybrid application is not for offline scenario.
Data will get stored in both Device memory and SUP's CDB. CDB will have the copy of data which is available in the EIS(Enterprise Information System) simply your backend. Whenever a device is subscribing for required information from CDB, CDB will get the data from the backend and will update the device. So by this time data will be available in both CDB and Device. CDB will contain data of all the subscribers and device memory will have its own data. for more information you can refer sybase infocenter.
The Logic it works is likes as follows,
I think your aware about BAPI's in SAP and MBO's in SUP.
So, by consuming the BAPI which are getting exposed from SAP backend, we will create a MBO. MBO is a table which contains the parameters from BAPI. and some CRUD functions to work on it. After creating an MBO we will deploy it into SUP (Brand change happened now: SAP Mobile Platform)
server. This will create a table in our CDB, with the schema of the particular MBO. Now we can control the data loading into CDB, by doing a MBO property configuration and data loading in device also.
Data loading between CDB and EIS is known as "Data Refresh"
Data loading between CDB and Device is known as "Data Synchronization".
Hybrid App's cannot be a complete offline App. They can do synchronization by storing events in a queue.
Check this thread Native App vs Hybrid App.
HWC applications are meant only for developing small scale applications(like approval scenarios) so they cannot be a complete offline app.
where Native applications are meant for Large scale applications.
SUP 2.2 version allows us to store data on device cache in HWC apps as shown in blog
For Caching refer SUP Caching By Example - Webinar Slides
This may help you.
If your willing to put some work into it, there is the possibility of using RBS in the Hybrid Container to obtain full offline sync.