The different components of the OData SDK are implemented as static runtime libraries and each component can be used independently.
The OData SDK is used for building native mobile applications. It consists of a
collection of runtime libraries and classes. The OData SDK supports Android, BlackBerry
and iOS platforms and it is based on the native device SDKs of the platforms. There is
an implementation for each platform. Native applications installed on the devices allow
the client application to leverage the support provided by the given platform, for example:
- Adapt to each device’s form factor (for example, automatic layout)
- Exploit different input methods (for example, touch screen, keyboard or
trackball)
- Cache data in native device data stores for better performance
- Tightly integrate with the features of the device
The general description of the SDK components follows. For detailed platform specific
descriptions, see the respective chapters on Android, BlackBerry and iOS.
Note: Before using SAP® Mobile Platform 2.2 SDK, the OData applications
built on 2.1 ESD # 3 or prior releases should to be explicitly migrated using the
migration procedures in the Developer Guide: Migrating to
SAP Mobile SDK guide for 2.2. When
you add the SAP Mobile Platform 2.2 OData SDK into your existing
application, the application will encounter compilation errors, that should be resolved.
This migration is not required for releases 2.2 and above.
The following components are included in the OData SDK. See the detailed
platform specific descriptions in the respective sections.
OData Parser
Parses and generates valid OData Protocol messages to/from native
objects. It eliminates the need for mobile developers to work with the low-level
details of the OData protocol directly. Functionalities supported by this component include:
- Parsing OData XML structures to native OData objects
- Validating OData XML during parsing by checking the
existence of mandatory fields and structures
- Providing easy access to all OData fields and structures via
the objects resulting from the parsing
- Building OData XML structures from native OData objects
Cache Management
The runtime cache is responsible for storing and accessing OData
related objects in the memory of the device for quick and easy access.
Functionalities supported by this component include:
- Storing/accessing OData objects in the memory (both metadata
and application data)
- Searching for OData entries in memory using their searchable
fields
- Managing the size of the cache
Persistence
Implements a convenient and secure storage of data on the device.
Mobile applications can access the locally stored data even when network connection
is unavailable. Functionalities supported by this component include:
- Storing objects and raw data on the physical storage of the
device
- Easy and quick access of the stored objects and raw
data
- Data encryption for sensitive data
Supportability
Implements standard SAP logging, tracing and error handling to enable
end-to-end supportability from client to back-end. Functionalities supported by this
component include:
- Common exception and error handling
- Event logging
- Tracing (SAP Passport)
Connectivity
This connectivity layer handles all connectivity related tasks,
hides the complexity of the communication at transport level, and provides an easy
to use API to the applications. Productive enterprise applications must use
SAP Mobile Platform for connectivity for all
enterprise use cases. For development and demo purposes, the SDK also provides a
possibility to use HTTP or HTTPS. Functionalities supported by this component include:
- Synchronous and asynchronous HTTP request handling
- Supported authentication are:
- X509 certification
- SSO token/cookie
- Basic authentication (user/password)
- Timeout handling
- Compressed payload handling
- Request types as supported by OData Protocol
- Connection pools for optimal performance