OData SDK

New or changed features for OData SDK include refactored OData SDK APIs, DataVault classes for iOS, Android, and BlackBerry, standalone Afaria libraries, native notification, streaming support for large objects, and end-to-end tracing for iOS and Android.

OData for SAP products provide SAP extensions to the OData protocol that enable users to build user interfaces for accessing the data published via OData. The interfaces require human-readable, language-dependent labels for all properties, and free-text search within and across collections of similar entities (OpenSearch).

OData services include:

The OData SDK API supports online request-response style applications. This development archetype implements messaging-based synchronization and HTTP channel, and capitalizes on security enhancements and architectural modifications to provide fast and secure service-enabled applications. You can configure push notification properties for an application through Sybase Control Center. You can develop applications so they can be monitored through Sybase Control Center.

New OData SDK APIs

The OData SDM Parser SDK has been enhanced to improve performance. Two new APIs are added to the SDM Parser for Android and BlackBerry for enabling the performance data points for parser. One new API is added in Android to support complex datatype for POST request method.

  • Support for complex types (Android) – developers can use new API for Android parser to support complex types.
  • Enable performance logs (Android) – developers can use new API for Android parser to enable performance logs.
  • Enable performance logs (BlackBerry) – developers can use new API for BlackBerry parser to enable performance logs.
Documented in:
  • Developer Guide: OData SDK, see OData SDK Components and APIs > SDMParser > SDMParser Public APIs in the Android section.
  • Developer Guide: OData SDK, see OData SDK Components and APIs > SDMParser in the BlackBerry section.

Refactored OData SDK APIs

The OData SDK API has been refactored significantly in Unwired Platform 2.2. Applications developed with earlier versions of the OData SDK API continue to work after upgrade. Before using Sybase Mobile SDK 2.2, OData applications built on 2.1 ESD # 3 or earlier releases should be explicitly migrated to 2.2. The OData SDK APIs in Unwired Platform release 2.2 are refined and enhanced for better usage. When you add the Unwired Platform 2.2 OData SDK into your existing application, the application will encounter compilation errors, that should be resolved. For more information about the enhanced APIs and migration procedures, see Developer Guide: Migrating to Sybase Mobile SDK, the Migrate OData SDK Applications section.

DataVault

A DataVault class is available for iOS, Android, and BlackBerry (in addition to the current Private DataVault class for Android). Additional password policy control has been added to the DataVault, making it easier to populate the password policy and enforce enterprise password policies in device applications. The new DataVault API enables you to work with password policy settings, check for default passwords, change passwords, delete data from the data vault, and iterate through data.

Documented in: Developer Guide: OData SDK, see DataVault in the iOS, Android, and BlackBerry sections.

Standalone Afaria Libraries

Standalone Afaria libraries are now used with Sybase Mobile SDK.

Documented in Afaria documentation, available at http://frontline.sybase.com/support/downloads.aspx (registration required).

Native Notification

You can configure native notification (sometimes called push) properties for an application through Sybase Control Center. If enabled, any newly created application should be immediately available via messaging-based synchronization or HTTP channel without further configuration.

Documented in: Developer Guide: OData SDK, see:
  • Enabling Apple Push Notifications (iOS)
  • Apple Push Notification Service Configuration (iOS)
  • Registering Listeners for Push Notifications (Android)
  • Registering Listeners for Push Notifications (BlackBerry)

Streaming Support for Large Data

Streaming handles large data sent device-to-server and vice-versa. Streaming of response data obtained from the server on a client is the ability to receive data of unlimited size via a stream. The stream is processed as the data arrives and needs not be stored in device memory at any point in time. Streaming can take place in both synchronous and asynchronous invocations of the client; it has no impact on the server.

A large attribute class enables you to send large objects and handle them efficiently on the client. Clients can also access or modify a large attribute without reading the entire attribute into memory. In addition, clients can execute queries without having large attribute values automatically filled in the returned MBO lists or result sets.

Applications developed in earlier versions of Online Data Proxy (ODP) had limitations on the size of the data to be uploaded from device to server. Also, only a limited amount of data could be downloaded on the device. This limitation has been addressed by the availability of device-to-server and server-to-device streaming functionality on ODP. Now applications can provide the path of the file containing the huge data, and data from this file is streamed to the server in chunks.

Documented in: Developer Guide: OData SDK:
  • SDMConnectivity (Android)
  • SDMConnectivity (BlackBerry)
  • Enabling Data Streaming (iOS)

End to End Trace

End-to-end trace functionality is now supported for Android and iOS.

Documented in:
  • Developer Guide: OData SDK, see End to End Tracing (Android and iOS sections)
  • System Administration, see Using End to End Tracing to Troubleshoot and Diagnose Problems