SAP HANA Developer Guide - Get a Free Blog

An empty service metadata document consists of one Schema containing an empty EntityContainer. The
name of the EntityContainer is the name of the .xsodata file, in this example "empty".
OData Namespace Definition
By default, as shown in the metadata file of an empty OData service, the namespace of the generated Schema is
created by concatenating the package name of the .xsodata file with the file name, and separating the
concatenated names with a dot. You can specify your own namespace by using the namespace keyword:
Service definition sample.odata:namespace.xsodata
service namespace "my.namespace" {}
The resulting service metadata document has the specified schema namespace:
http://localhost:8002/sample/odata/namespace.xsodata/$metadata
OData Object Exposure
There are two ways of exposing SAP HANA objects. You can either specify the repository design-time name or the
database-object runtime name (with database schema). Although both variants are supported, the preferred
method is the exposure via the repository design-time name. It has the advantage that the OData service is
automatically updated, if the underlying repository object changes. The support for database objects is mainly
intended for existing or replicated objects that do not have a related repository design-time object.
In the examples provided to illustrate object exposure, the following definition of a table applies:
SAP HANA Developer Guide
Defining Web-based Data Access
P U B L I C
© 2012 SAP AG. All rights reserved. 189