Migrating Mobile Application Projects

Migrate mobile application projects from version 1.5.5 of Unwired WorkSpace.

1. From WorkSpace Navigator, right-click the project and select Open in Diagram Editor.
   If the project needs to migrate to the current version of Unwired WorkSpace, a Migrate dialog appears.
2. Click Yes in the Migrate dialog.

   The migration status displays in the Migrating Results dialog, identifying the MBO and other relevant information, including any errors. Open the Problems view to isolate and correct any errors and warnings. If the migration does not complete successfully, you may need to run it again (by opening the project) after correcting any errors.

   Migration errors can occur if connection profile information changed. To view the connection profiles referenced by the migrated project, expand the Data Source References subfolder within the mobile application project folder.

   If a previous Unwired WorkSpace project version opens in the Mobile Application Diagram and you exit Unwired WorkSpace, the migration confirmation dialog appears the next time you open Unwired WorkSpace. For example:

   1. Locate an Unwired Workspace project.
   2. Right-click the project and select Open in diagram editor.
   3. In the migration dialog, click Yes to confirm migration, but do not select Do not show this dialog again. The project's connection profile is unavailable.
   4. Leave the project open in the Mobile Application Diagram and exit Unwired WorkSpace.
   5. Restart Unwired WorkSpace. The migration dialog appears when Unwired WorkSpace is in the process of opening. This is normal Eclipse behavior.

   Note: If you disable the Migrate dialog in Window > Preferences > Sybase, Inc > Mobile Development > Miscellaneous, migration occurs without prompting.
3. (Optional) If you wish to modify the MBO, redeploy the mobile application project.
   If earlier versions of the mobile application project are deployed to Unwired Server, redeploy the project and overwrite the existing project, making sure you map logical to physical roles and configure server connection mappings, since deployment profile settings are not retained after migration.
4. (Optional) If you wish to use new or enhanced methods in the Object API, generate code for device applications.
   Replace any previously generated Object API code in the mobile application project.

   For guidance in resolving issues that remain after migrating mobile application projects, see the "Migration Guidelines and Limitations" topic in the Installation Guide for Sybase Unwired Platform, version 1.5.2.