Client Application Recovery Examples

These scenarios provide example code that illustrate how the client application recovers from SAP Mobile Server failures in various client application states.

When the SAP Mobile Server is restored to a previous state the client might be in an inconsistent state with that of the server. For example:

Client synchronized with SAP Mobile Server after the time the database was backed up. The client cannot synchronize successfully with SAP Mobile Server once the database is restored.
Client registered with SAP Mobile Server after the time the database was backed up. Client registration was lost when the database was restored.

Client Application Registration Recovery Example
After SAP Mobile Server is restored, the client application connection information might be lost if the registration was created after the database was backed up.
Client Application RBS Synchronize Recovery Example
if SAP Mobile Server is restored to a point in time of previous application synchronization, the client synchronization gets Sybase.Persistence.SynchronizeException with error code SQLE_UPLOAD_FAILED_AT_SERVER. This error code indicates the need to recover the client database.
Client Application RBS BeginSynchronize Recovery Example
BeginSynchronize is an asynchronous pattern, requiring the user to override the onSynchronize method of the SUPDefaultCallbackHandler class to check for the SQLE_UPLOAD_FAILED_AT_SERVER error.
MBS for DOEC Client Application Recovery Example
MBS for DOEC clients can run on the iOS platform. The registration recovery is the same as RBS registration recovery. However, subscription recovery is different.

Parent topic: Recovering From SAP Mobile Server Failures