cache
– In the context of OData applications: a memory system component responsible for storing and accessing OData related objects in the memory of the mobile device for quick access.
collection
– Resource that contains a set of entries which are structured according to the Data Object / Entity Type definition in the respective Data Model. In OData, a Collection is represented as an Atom Feed or an array of JSON objects.
delegate – A delegate is an object that usually responds to some event in another
object and/or can affect how anothe object behaves. The object which
contains the delegate typically sends the delegate a message when a
triggered event occurs, giving the delegate an opportunity to carry out its
specified task.
Etag – Entity tag is one of the several mechanisms provided by HTTP for web cache
validation and concurrency control.
JSON – JavaScript Object Notation, is a light-weight text-based open standard
designed for human-readable data interchange over a network connection.
mobile application – Applications that run on smartphones and other mobile devices. SUP Mobile applications make SAP content available outside the corporate firewall and connect users to SAP services that are more commonly accessed on desktop computers.
OData client – An application that makes use of the OData protocol to access information
from variety of sources including, but not limited torelational databases,
file systems, content management systems and traditional web sites.
OData metadata document
– OData metadata documents describe the Entity Data Model (EDM) for a given service, which is the underlying abstract data model used by OData services to formalize the description of the resources it exposes.
OData (Open Data Protocol)
– Web protocol for querying and updating data. It applies and builds upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications.
OData for SAP – 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 collections of similar entities and across (OpenSearch).
OData Parser – Parses and generates valid OData protocol messages to/from native
objects.
OData Schema – Defines the structure of the xml files in the OData service.
OData Service – A service which implements the OData protocol.
OData Service Document – A document that describes the location and capabilities of one or more Collections.
OData SDK – Offers a range of libraries and APIs using which you can create applications
for Online Data Proxy.
Online Data Proxy – A light-weight edition of the Sybase Unwired Platform that provides a robust mobile infrastructure for enterprise IT organizations to securely roll-out and manage the deployment of light-weight applications in a controlled and monitored approach.
SAP – SAP Business Suite applications (such as ERP, CRM, SRM, SCM, Industry Solutions and so on) consist of many technologies and components. Unless stated otherwise, the term “SAP” means a backend business application that is based on the SAP NetWeaver ABAP application server, for example ECC 6.0.
SAP NetWeaver Gateway – Enables people-centric applications to consume SAP Business Suite data through popular devices and platforms in an easy and standards-based fashion.
SAP Passport – Medium to transport technical data of a request from the client to the server. Used for collecting trace and reporting information for chains of requests (RFC, HTTP) across system borders.