Enabling Models as OData Services

The Toolkit for Integration Gateway allows you to expose OData services based on database tables by mapping the model definition to the corresponding tables. Define an OData model to match the table properties, then bind the OData model to a datasource using Toolkit for Integration Gateway. The resulting OData services can be consumed by any client of SAP Mobile Platform and makes the OData service available for consumption.

For information on developing mobile applications by using the OData services exposed by Integration Gateway, see:

For information on creating the security roles required to deploy projects to SAP Mobile Platform Server, see SAP Mobile Platform 3.0 > SAP Mobile Platform Server > Administrator > Security Administration > Security Profiles, Roles, and Authentication in SAP Mobile Platform > Role Mapping > Integration Gateway Roles.

Prerequisites

Enabling your data model as an OData service includes:

  1. Creating a service implementation project, which is an Eclipse project with a predefined project structure, which generates and stores all the artifacts needed for OData service provisioning. When you create the service implementation project, you can also define the OData model.

    See Creating a Service Implementation Project in the GWPA Developer Guide.

  2. Selecting the datasource to be configured with the service implementation project by specifying the OData references and the datasources to bind with the entity set.

    See Selecting a Datasource in the GWPA Developer Guide.

  3. (Optional) Mapping the source and target fields of non-matching structures for operations-based (SOAP) structures.

    See Working in the Mapping Editor in the GWPA Developer Guide.

  4. Generating the runtime artifacts and deploying the project to SAP Mobile Platform Server.

    See Generating and Deploying Service Implementation Project in the GWPA Developer Guide.