Enterprise Information Management
Page tree
Skip to end of metadata
Go to start of metadata

The ODataAdapter is the only Smart Data Integration adapter that does not use a data provisioning agent. Instead the adapter runs in the HANA tenant's dpserver, and is disabled by default. The adapter does not have real time data capture capabilities, so creating a remote subscription based on an ODataAdapter virtual table will fail by design.

The remote source is configured at a broad service level, and virtual tables are created for individual entity sets or collections described by that OData service. Insert/update/delete/select statements on these HANA virtual tables are translated to POST/PUT/DELETE/GET requests and sent over HTTP/S. As of HANA SPS06, the adapter supports OData V2 and V4 protocols.

For official ODataAdapter documentation, see the following links and read through the subcategories to get a better understanding of the features and capabilities of this adapter.

Common Questions or Problems

  1. If the ODataAdapter does not appear in the list of available adapters while creating a remote source:
    1. Activate the adapter in the dpserver with the following SQL (requires System Privilege - ADAPTER ADMIN): CREATE ADAPTER "ODataAdapter" PROPERTIES 'display_name=OData Adapter;description=OData Adapter' AT LOCATION DPSERVER;
  2. After creating the remote source, no remote objects can be seen in the metadata browser.
    1. First confirm that a connection test succeeds.
    2. If the connection is working but no remote metadata is found, confirm the remote source URL refers to the broad service level URL. You can verify you are entering a URL that can be understood by SDI by opening the URL in your web browser. The URL should be the "Service root URL", take for example https://services.odata.org/V4/Northwind/Northwind.svc. When opening the URL, you should see a list of collections for your specific service. In the following example from Northwind V4, the service has many collections including Customers and Employees, which can later be represented as virtual tables.

      1. ...<collection href="Customers"><atom:title type="text">Customers</atom:title></collection>

      2. <collection href="Employees"><atom:title type="text">Employees</atom:title></collection>...

  3. Do you want to show navigation properties ($expand), which reveal relationships between entity sets in the OData service ?
    1. If yes, then set "Show Navigation Properties"= True for remote source configuration.
    2. SDI can only work with keys for Navigation Properties, other navigation field won't be displayed when creating virtual table.
  4. What authentication methods are supported with SDI ODataAdapter?
    1. For HANA SPS06 and SAP HANA Cloud, there are additional authentication options.
    2. doesn't support SAML, if you want to use SDI to connect to ODATA provider that enable SAML, you need to put in the "Extra Connection Parameters" in remote source connection with value "saml2=disabled"
  5. Tips for accessing SuccessFactors OData through SDI:
    1. It is highly recommended to apply a server-side paging method, and include historical data control parameters for your SuccessFactors virtual tables.
      1. Paging:
        1. Snapshot: This method has the best performance for large queries and fully supports filters.
        2. Cursor: Use this paging method if snapshot performance is poor and you don't require the use of filters or sorting in your query.
      2. Historical parameters:
        1. asOfDate: Select a single date historical version of the data.
        2. fromDate: Set the earliest date for a range of historical data that will be returned by the request.
        3. toDate: Set the latest date for a range of historical data that will be returned by the request.
  6. If you are connecting to an HTTPS secured OData services, please check the help document for detail steps.
  7. If all the configuration has been done and still there is error for remote source connection, please enabled the traces and gather the recommended information for efficient support.