Enabling JPA models as OData services using Integration Gateway.
Integration Gateway allows you to expose OData services by using JPA models as input that is already in sync with the underlying database. Use OData Modeler to define an OData model which should match the JPA model properties. The OData JPA processor fetches data at runtime.For details of the tasks performed using OData Modeler, see the OData Modeler Documentation on https://help.hana.ondemand.com.
Integration Gateway provides Custom Processors, a plug-in mechanism to provide your own logic on top of the output generated by the API toolkit for SAP Mobile Platform to enhance / modify the content. See Defining Custom Code on https://help.hana.ondemand.com. The relevant content is located in .
|Delta token||Supported (via custom processor)|
|Tombstones||Supported (via custom processor)|
|System query options: $orderby, $skip, $top, $select, $inlinecount, $filter.
Note For JPA, when querying $select you should include the key property in the request URL along with the other property on which the query is based.
|$expand and $format||Not supported|
|Deep insert||Not supported|
|Custom query options||Not supported|
|Function imports||Not supported|
|Logical operators - all the logical operators are supported except for 'Not'.||Partially supported|
|Date functions||Not supported|
|Math functions||Not supported|
|Arithmetic operators||Not supported|
|Type functions||Not supported|
For details of the tasks performed in this step, see API toolkit for SAP Mobile Platform Documentation on https://help.hana.ondemand.com. The relevant topic to refer to is provided in the corresponding sub steps below.