Transitioning MBS Applications to the Current Release (2.1 ESD #3 or Later)

(Not applicable to DOE based applications) iOS applications built with earlier versions of the SDK use messaging-based synchronization (MBS) for data delivery. Applications built using SDK version 2.1 ESD #3 or later use replication-based synchronization (RBS) for data delivery to reduce synchronization time.

This task flow shows you how to transition your messaging-based application to the current release as a replication-based application. The tasks include setting up the project, updating the application, and testing the application.

Note: The code samples in this task flow are from the SUP101 project from the Tutorial: iOS Object API Application Development.
  1. Migrating the Project and Generating Code
    Migrate the existing project to the current version of Sybase Mobile SDK, and generate new RBS object API code.
  2. Setting Up the Xcode Project
    Set up the Xcode project with the generated code and libraries required in SDK version 2.1 ESD #3.
  3. Making Changes to Application Registration
    This task is not required if your application is built with SDK version 2.1 ESD #2. Make changes to the application to allow it to register as required in 2.1 ESD #3.
  4. Making Changes to Application Initialization
    Make changes to the application to allow it to initialize as required in 2.1 ESD #3.
  5. Connecting Through a Relay Server
    An iOS RBS client that connects through a Relay Server needs two different farm IDs: one for a messaging client connection to register the application, and the RBS connection for database synchronization.
  6. Setting Up Callbacks
    Update your application to use callbacks from SDK version 2.1 ESD #3.
  7. Generating Change Logs
    Use the Change Log API to generate change logs that are sent to the client after the synchronization.
  8. Creating, Updating, or Deleting Records
    In SDK version 2.1 ESD #2 applications, after creating, updating or deleting records, you called the save method to save the change to the local database, and called submitPending to send the change to the server. In SDK version 2.1 ESD #3 applications, after updating or creating records, you call the save and submitPending methods, and call synchronize to send the changes to the server.
  9. Testing the Application
    After you have transitioned your application to SDK version 2.1 ESD #3, test the application to ensure that it can establish messaging and database connections to the Unwired Server, perform an initial synchronization, and update the database.
Parent topic: Migrating iOS Native Custom Applications