Mobile Business Object

You may encounter some issues when migrating mobile business objects (MBOs) to Unwired Platform version 2.1 ESD #3.

• Updating the Database Connection Profile
  Due to JDBC driver location changes, beginning in Sybase Unwired Platform version 2.1. ESD #3, the existing database connection profile may fail to ping/connect with this exception: java.lang.ClassNotFoundException: com.sybase.jdbc3.jdbc.SybDriver.
• Ensure that Normal MBOs Have Primary Keys
  Normal MBOs that have no primary key defined generate a warning message when migrating earlier versions of mobile application projects to Unwired Platform version 2.1 ESD #3. To ensure optimum performance, make sure that normal MBOs have a primary key.
• Eliminate Composite Orphans in Native Object API Applications
  A composite orphan is an MBO child entity within a composite relationship without a parent entity. For native Object API applications, the upgrade process silently deletes composite orphans from the server cache. Check all your MBOs to ensure that applications run properly after the upgrade.
• Redeploying Projects That Contain Composite Relationships
  After migration if you have mobile application projects that contain composite relationships and the child MBO load operation has no parameter dependencies on its parent, you must redeploy the package from Unwired WorkSpace using Update mode to generate the correct loadGroups for the deployed package.