Documentation Issues and Updates for Sybase Mobile SDK 2.1 ESD #3

Duplication linking issues in Sybase Control Center for Sybase Unwired Platform

Close parentheses missing from linker flags

In the Importing Libraries and Code topic in Developer Guide: iOS Object API Applications step 11 should include close parentheses after EFFECTIVE_PLATFORM_NAME:

$(SRCROOT)/$(PRODUCT_NAME)/libs/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/libMO.a
$(SRCROOT)/$(PRODUCT_NAME)/libs/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/libSUPObj.a

Corrected code for setting up a database connection

The code in Connecting Through a Relay Server was updated to cover two situations: whether the connection template on SCC is configured with all the required Relay Server information or not.

On-demand cache policy with a small coherence window, not large

In the Cache Group Considerations topic in Mobile Data Models: Using Mobile Business Objects 2.1 ESD #3, the second sentence should read: "...for transactional data that has little tolerance for EIS data that is stale, an On-demand cache policy with a small coherence window is a more appropriate cache solution than an hourly schedule-based refresh."

The following note was omitted from the prerequisites in the Unwired Platform version 2.1 ESD #3 Tutorials:

Do not try to compile and run the tutorial example projects posted in the SAP® Community Network: http://scn.sap.com/docs/DOC-8803. They are meant only as code examples.

Updates to the Datavault documentation for Android were made.

A new topic was added in Developer Guide: Android Object API Applications > Client Object API Usage > Security APIs > SUPDataVault DataVault to document the init method. Developer Guide: Android Object API Applications > Client Object API Usage > Security APIs > SUPDataVault DataVault > Code Sample is also updated to include the init method.

Changes in the directory structure for the Sybase Mobile SDK installation in this version were not updated in the documentation.

Beginning with Unwired Platform version 2.1 ESD #3, Sybase Mobile SDK installs in a directory structure that allows multiple versions of Mobile SDK to coexist on the same system. The SDK top level directory now includes the version and some directories that were peers to the SDK top level directory are now located below it.

Refer to Path Corrections for Backward Compatibility when you encounter a path specifying the location of any Mobile SDK files.

This also applies to Developer Guide: Mobile Workflow Packages > Mobile Workflow Development > Hybrid Web Container Customization > Android Hybrid Web Container Customization > Android Customization Touch Points > Default Behavior Customization for the Android Hybrid Web Container > Removing the PIN Screen.

In Developer Guide: iOS Object API Applications 2.1 ESD #3 > Customizing the Application Using the Object API > Initializing an Application > Initially Starting an Application > Modifying Synchronization Parameters, when modifying synchronization parameters, you must re-get the sync parameter instance and save again.

<MBO>SynchronizationParameters *params = [<MBO> getSynchronizationParameters];
[params delete];
params = [<MBO> getSynchronizationParameters]; //must re-get the sync parameter instance
params.Param1 = @value1; //set new sync parameter value
params.Param2 = @value2; //set new sync parameter value
[params save];
[SUP101SUP101DB synchronize];

Use submitPendingOperations and cancelPendingOperations only when there are multiple pending entities on the same MBO type.

submitPendingOperations and cancelPendingOperations do a select on the MBO table to find the pending MBO instances. If the MBO instance is available in memory, using the MBO instance's submitPending or cancelPending is more efficient.

Topic no longer applicable in the BlackBerry developer guide

The HTTP Push Gateway topic in Developer Guide: BlackBerry Object API Applications > Client Object API Usage > Synchronization APIs > Push Synchronization Applications is not applicable in Unwired Platform version 2.1 ESD #3.

The topic Object API Changes in SDK Version 2.1 ESD #3 in New Features 2.1 ESD #3 > New Features for Sybase Mobile SDK > Object API Development requires clarification.

The sentence "Consequently, messaging-based synchronization has been removed from the 2.1 ESD #3 SDK." should be changed to:

"Consequently, messaging-based synchronization has been removed from the 2.1 ESD #3 SDK for data delivery. The messaging channel continues to be used for communications such as application registration."

The types of communications the messaging channel sends are listed in DeveloperGuide: iOS Object API Applications > Getting Started with iOS Development > Best USes for Object API Applications > Client Runtime Architecture > Mobile Channel Interfaces.

Startup of an application always gets http callback errors.

During initialization, the client may try several URLs in an attempt to discover the correct path to the Unwired Platform server. During these attempts, 404 errors (Page Not Found) may occur and will be reported to the OnHttpCommunicationError callback. This is expected behavior and you can safely ignore these initial 404 errors.

If the 404 errors continue to occur after successful registration of the application or if registration never succeeds, double check the UrlSuffix setting of the application's ConnectionProperties object.

Return code is unexpected through onHttpCommunicationError with disabled user.

In an environment configured for SiteMinder authentication, the expectation is that onHttpCommunicationError will be called back for error condition 302. This condition is not fulfilled currently by the Windows and Windows Mobile platforms; instead, they return 404 errors.

Search Sybase Unwired Platform documentation for the topic Output Mappings for more information.

In the Developer Guide: iOS Object API Applications > Client Object API Usage > Callback and Listener APIs, there is additional information to note:

References to sp.Synchronize() should be SUP101DB.Synchronize().

iOS client files for 2.1.3 are in <Install-Root>\MobileSDK213\ObjectAPI\iOS\RBS and <Install-Root>\MobileSDK213\ObjectAPI\iOS\MBS.

After importing the MBO example project, connect to Unwired Server and deploy the project. See Tutorial: Mobile Business Object Development > Deploying the Database Mobile Business Objects for details.

The data vault security feature has been enhanced to allow administrators to create a password policy for data vault logins. Developers must create data vault code that performs policy enforcement.

Use the datavault class to create a datavault that enforces a password policy. This class provides encrypted storage of occasionally used, small pieces of data, and is documented in the SUPDataVault or DataVault topic in the corresponding  Developer Guide for your application type.

See the generated API reference information provided with the Mobile SDK for a complete list of methods in the ConnectionPropertyType class.

The Apple Push Notification Service Configuration topic in the OData SDK Developer Guide and the iOS Object API Applications Developer Guide incorrectly states that APNS cannot be used with iPad devices.