can we use IoT Application Enablement APIs in HCI OData service?

[former_member184876]

Hi Friends,

I am trying to use IoT Applicaton Enablement APIs as a Data Source in HCI OData service.

The first step is to load the EDMX file.

When loading the EDMX File, i am getting error.

===========================================

The attribute 'Name' must start with a letter, period, or an underscore and may contain letters, digits, periods, and underscores (but no spaces).

============================================

Even calling the IoT Application Enablement APIs using OData receiver adapter is having error.

After lot of analysis, it is identified that the reason for errors is Application Enablement API Name fields are having "." in them like below. OData adapter is not accepting "." in name field and throwing error.

Can you help me with any ideas how to overcome this scenario? is it possible to use IoT Application Enablement APIs using HCI OData Adapter?

Thank you very much in advance,

Example of field names:

<d:workcenter_basicdata.childworkcell>

<d:workcenter_basicdata.childworkcell.Timestamp>

<d:workcenter_basicdata.manufacturer_company>

<d:workcenter_basicdata.manufacturer_company.Timestamp>

Best Regards,
Venu

[marcus_behrens]

OData is not like SQL or DOM as different implementations of OData clients and servers might implement/require different subsets of the OData language to work well.

Our IoT AE analytical odata api has been show to work in a limited way (with workarounds for he authentication) with Lumira and with SAP Analytics Cloud.

One challenge is the authentication (only SAML or OAuth access tokens are supported) and the next one which kinds of queries the caller requires to be available. We for example do not support "inline-count" on our service as for a big data infrastructure this would be difficult to achieve without performance penalties.

Have you progressed further with your research? Would be greta if you could post your results here or in a blog.