SMP 2.3.x / 3.0.x MBO - updating / reinstalling app and user data

[former_member305582]

Dear gurus,

We've been developing with SMP MBO runtimes for a long time.

That's a great experience and so on, but one thing that still bother our development team is when an app update has to happen.

The real life:

1. Target devices: iOS 8.x onwards
2. We have a running, native, MBO based, online/off-line app, running sharp.
3. Backend is SAP, talking through RFC.
4. Users are registered and authenticated through LDAP. Works like a charm.
5. The customer asks a new feature, that demands either a new RFC/MBO or updating an existing structure.
6. The development team takes care of whatever is required. New or updated structures are maintained within the new app release.
7. Tests are done. Success!
8. Now... the pain --> the time to distribute the app over the air...

The issue: the database structure is not correctly adjusted after app update.

By the end of the day, we ask our end user to remove the app and reinstall it. Voilà!!!! After re-registering, the app comes back to work.

But all records (specially pending records) are gone forever and THIS is a severe issue.

But, come on... this is cumbersome to the end user. There has to be a better way to do that.

The question is... using the API, either iOS or SMP Native Object API for MBO runtime, how can we manage the app update procedure in a clever way, like common apps we find everyday in the app stores?

Any advice will be welcome!

Thank you,

Michel

[midhun_vp]

Hi Michel,

The answer is to use an MDM (mobile device management) solution like SAP Mobile Secure.

You could push the app updates over the air.

You could even have an internal app store (just like apple store) where you could upload apps. The end users downloads the app.

There are many other features:http://scn.sap.com/docs/DOC-62447

Regards, Midhun

SAP Technology RIG

[former_member305582]

Hi Midhun! Thanks for your prompt feedback.

Using any MDM as SAP Mobile Secure, Afaria or even 3rd party such as Air Watch doesn't change the game at all.

The issue is not about over-the-air provisioning as we already have it working well.

The issue lies within SMP, when an application gets an update and SMP is unable to adjust the underlying Mobilink DB (within the app) with the new or changed structures, forcing the user to remove the app and reinstall it, losing any data pending to sync.

Thanks,

Michel

[midhun_vp]

Hi Michel,

The question is... using the API, either iOS or SMP Native Object API for MBO runtime, how can we manage the app update procedure in a clever way, like common apps we find everyday in the app stores?

Okay, I thought your question is on updating the apps over the air.

May be you have to provide more details on the error you are getting in your device.

I assume that there should be something to do with your device code.

If this issue is critical you should raise a ticket to SAP. The support team should be able to help you.

Regards, Midhun

SAP Technology RIG

[former_member305582]

Hi Midhun!

Thanks for your reply.

As we couldn't find in the Object API's documentation anything regarding changing MBO structures while updating the app, we decided to change our approach.

We're trying to live with 2 DBs in-app - the original and a new one. Then, we're going to implement a new core logic that, after synchronization, moves the pending records to the new app DB. Of course, after that, the old DB is cleared.

Right now we're testing it and if successful, I'll share the info.

I'm still not fully happy with that approach but that might work.

Thanks,

Michel