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.

Note: There is no data-transitioning solution. The data residing in the old device database is not used after the application is converted to RBS. The application users should submit all pending data to the Unwired Server using the existing MBS client application before the migration to the new 2.1 ESD #3 RBS application. See Migration Strategies for 2.1 ESD #3 in Migrating iOS Native Custom Applications After all the pending changes are synchronized to the Unwired Server, the application user needs to remove the old application and/or the older existing database on the device. If the old application is not removed from the device, the database for the old application will continue to reside on the device; this may double the space consumed on the device when the new application downloads records to the new database.

Start and test the client application:

Verify that no exceptions have been received from the code that subscribes to the database. If an exception has been received, check the connection profile.
If no exception has been received, you have successfully established the connection to the database.
Verify that no exceptions have been received from the code that performs initial synchronization. If an exception has been received, check for any server-side issues in the server log. Also ensure that there is no incompatibility in versions between the deployed package on the server and the generated code.
If no exception has been received, you have successfully performed an initial synchronization.
Verify that no exceptions have been received from the code that creates or updates a record. Also verify that you can view the update on the server.