SAP HANA Developer Guide - Get a Free Blog

8.1.4 OData Security Considerations
Enabling access to data by means of OData can create some security-related issues that you need to consider and
address, for example, the data you want to expose, who can start the OData service, and so on.
If you want to use OData to expose data to users and clients in SAP HANA application services, you need to bear
in mind the security considerations described in the following list:
● Data Access
Restrict user select authorization for tables/views exposed by the OData service
● OData Service
Restrict authorization rights to start the OData service
● OData Statistical content
Restrict access to the URL/Path used to expose OData content in the Web browser
8.1.5 Defining the Data an OData Service Exposes
An OData service exposes data stored in database tables or views as OData collections for analysis and display by
client applications. However, first of all, you need to ensure that the tables and views to expose as an OData
collection actually exist.
To define the data to expose using an OData service, you must perform at least the following tasks:
1. Create a database schema.
2. Create a simple database table to expose with an OData service.
3. Create a simple database view to expose with an OData service.
This step is optional; you can expose tables directly. In addition, you can create a repository view (for
example, Analytic, Attribute, Calculation).
4. Grant select privileges to the tables and views to be exposed with the OData service.
8.1.6 Creating an OData Service Definition
The OData service definition is a configuration file you use to specify which data (for example, views or tables) is
exposed as an OData collection for analysis and display by client applications.
An OData service for SAP HANA XS is defined in a text file with the file suffix .xsodata, for example,
OdataSrvDef.xsodata. The file resides in the package hierarchy of the OData application and must contain at
least the entry service {}, which would generate an operational OData service with an empty service catalog and
an empty metadata file.
Prerequisites for the creation of an OData service definition:
● SAP HANA studio/client installed and configured
● SAP HANA database user available with repository privileges (for example, to add packages)
● A SAP HANA development system added to (and available in) SAP HANA studio, for example, in either the
Navigator view or the SAP HANA Repositories view
● A working development environment including a repository workspace, a package structure for your OData
application, and a shared project to enable you to synchronize changes to the OData project files in the local
file system with the repository
SAP HANA Developer Guide
Defining Web-based Data Access
P U B L I C
© 2012 SAP AG. All rights reserved. 183