Hi
Can I have some clarifications with respect to how Synchronization is implemented in Convertigo Platform. Will try to ask my questions in terms of two scenarios. Assuming that there is an SQL Database in an enterprise server to which we connect from our mobilizer project.

1. Pull Based Synchronization: Suppose there is a new row added to one of the tables in the SQL DB. In this case can we implement a pull based synchronization mechanism when we do the development in the mobilizer project. The intention is with this mechanism when user starts the mobilizer app the app should start pulling the new row from the enterprise SQL DB by sending a request to the convertigo server. And inturn the Convertigo Server connects to the SQL DB and gets the new row and passes it to the mobile device

2. Push Based Synchronization:Suppose there is a new row added to one of the tables in the SQL DB. In this case can we implement a push based synchronization mechanism in the server when we do the development in the mobilizer project. The intention is with this mechanism the server should keep polling the SQL DB, get the latest addition from the SQL DB and keeps updating its cache in the Convertigo Server. Then at a point when the server gets a connection notification from the mobile app it just pushes the latest DB information to the mobile handset.

3. The other question is whether the syncronization mechanism is exposed in form of an SDK or some Library? Or is it tightly coupled with the development of the mobilizer.

Hello

Although Convertigo MEAP supports SQL connection to the back end, synchronization is not the preferred process to use with Convertigo. The primary goal of the Convertigo is to provide transactional web service methods on back end application (Including of course SQL).

Nevertheless, If you would like to do synchro, this is completely possible using the web services interfaces.

For scenario1 (Pull), just write a getNewLines sequence/transaction returning all the new lines you have in you sql database. On the Sencha Client side just insert in the localdatabase all the new lines you receive when you call a the getNewLines sequence. To insert in the localdatbase you can use Sencha's localStorage store.

For Scenario 2(Push), This is also possible. Convertigo server can automatically launch sequences/transactions using it's integrated scheduler. see www.convertigo.com/en/product-overview/c...tration-console.html

The polling using this sequence ends up with a SQL call to the database and the data returned can be inserted in Convertigo Cache.

When a Mobile device connects it can execute the same Sequence and the data would be returned from Convertigo Cache instead of the SQL data base. Again , you can use Sencha's localStorage to update the local database on the mobile.


These synchronization mechanisms are to be implemented by the Mobilizer programmer. there is no standard SDK/library for that but this would not be a bad idea : )

Convertigo Mobilizer is OpenSource we would be glad to add a type of "Synchronizer" project in our project Library.

By the way, (Not critical )you posted in the "announcement" section of the forum. Cloud you please post in the appropriate section?

Thank you

Hope this Helps
Convertigo Support team.

Hello,
Thank you so much for the detailed answer. I am quite clear now how sync is implemented in the Convertigo Server. I have a few more questions here:

Push Mechanism: I understood that the Server cache can be updated with the enterprise data with the help of a the sequences/transaction which can be launced from the scheduler. When a Mobile device connects it can execute the same Sequence and the data would be returned from Convertigo Cache instead of the SQL data base. Again , you can use Sencha's localStorage to update the local database on the mobile.
Q1: Can the Server push this updated cache data to the device when it receives a connection request from the device. In my opinion it should not do it this way because if it can does this it would be an overhead on the server side to analyse the client app first and check whether it should do a local datastore update for this app. Where as if the device datastore update request originates from the client then this logic need not be implemented in the server.


Q2: One more question is when it gets a request from a device does the convertigo server do a validation that the request has come from a valid device. i.e. a device which is registered in the name of an employee. I think this is device management and should not be part of the MEAP server like convertigo. It should be part of an MDM which can be integrated with convertigo.

Q3: How can we integrate a MDM with Convertigo server to do device management functionalities like remote wiping of applications etc.

Regards
Tapas Dixit

Hello,

For Q1: The server never pushes data to a mobile. It is always the mobile that call the server and in return the server brings back some data. There is no "connection request" as is, but what you call a "connection request" could be the "Login" method of the web service. And in this case, yes the server would authenticate the user and if ok, would return the updated data to the mobile device for it to update its local database.

For Q2: Normally the device can be any device. What authenticates an employee is not the device itself but more the credentials he will provide in the connection request. Most of enterprise now use BYOD (Bring your Own Device) so authenticating by device seems not to be the most interesting solution. Now, it is completely possible that the mobile sends to Convertigo server some device specific data such as an UUID retrieved with PhoneGap and have the convertigo server to call a Web Service authorizing or not this specific device.

Yes, Convertigo is not a MDM and any MDM could be integrated with Convertigo.

For Q3: MDM is out of the scope of Convertigo MEAP, but it would be very easy to interface such MDM with Convertigo as Convertigo can call any of the MDM's web service and take business decisions according to the MDM responses.