Mobile Back-End Tools¶
The mobile back-end tools is a set of tools that enable a developer to model an OData service and generate a Java EE web application to implement the OData service, along with automatic creation of the necessary database tables within a preexisting database schema.
You may use the software solely for the purpose of developing applications for use with 'SAP Mobile Services'; provided that for those SDK components that can be used in connection with or deployed on platforms other than mobile services, you may use those components other than with mobile services if you have obtained a production license to mobile services.
A developer defines the model by providing an OData CSDL (Common Schema Definition Language) XML file for version 2.0
or 4.0 of the OData specification. A CSDL graphical modeling tool (
CSDL Editor) is available in SAP Business Application Studio
to help create a model or modify an existing model.
To store OData entity sets, the generated OData service uses an in-memory database or SQL database. Use an in-memory database (for testing only) or use a SQL database that's available in SAP Business Technology Platform (e.g. SAP HANA) or from a hyperscaler (e.g. Azure SQL, PostgreSQL).
A number of other database products are supported, primarily for delta-enabling existing on-premise
SQL database back-ends to enable offline consumption. See Cache Databases
-bind option for more details.
Except for the in-memory database, installing, creating, and configuring SQL databases and schemas is outside the scope of these instructions. See the SAP Business Technology Platform Cockpit documentation set for additional information.
The generated OData service, when first started, automatically generates the tables and other SQL artifacts within your selected target database or schema. The configured database credentials must therefore be for a database user with suitable permissions for table/index creation.
Please take note that HDI container based HANA databases do not have suitable permissions for dynamic table/index creation. Therefore HANA databases must always be bound with schema access.
Tools are also provided to model and generate an OData service that exposes existing database tables, with or without OData change tracking. See Working with Existing Database Tables.