Skip to Content

How to Troubleshoot XS ODATA registered to Gateway

In a previous question, I noted we have a requirement to use HANA XS Odata for a custom Fiori app on gateway. When the XS Odata is registered through SEGW or iwbep/oci_srv_gen, it loses the relationship between data properties. Meaning, there is no errors when registering the service, but when using a query - it cannot aggregate the data or display it properly, repeating line items and not making any sense. So we cannot use the service in this state, although it still works fine on original HANA server via browser (and we can still develop the app with proxy configured in eclipse). so we are still trying to figure out how to run the Fiori app deployed to ABAP repository with correct XS odata.

I am trying to figure out if we can troubleshoot the issue, since it registers without any errors, and does not create a dump when making a query, I am not sure how to fix this. Is there any techniques that are recommended when trying to register HANA XS Odata and only data response to query is having the issue? I see other articles that are similar, not exactly that the data properties are no longer maintained. Is there a way I can manually add new metadata to rebuild the relationships between the data?

I have also seen recommendations to create a reverse proxy to HANA XS through a live connection, but as we are attempting to complete this, its having more issues with HTTP vs HTTPS and SAML authorization and so on. So I am not sure that it is going to work in our scenario.

Any advice is greatly appreciated, thanks.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Nov 05, 2019 at 02:33 PM

    We did finally figure out this issue, for anyone who has a similar problem. Basis and DBA team configured web dispatcher to connect to the HANA system. But there was some CORS problem that persisted. So we had to go and edit the xs admin console and modify the allowed headers, as shown in this article:

    But now we are able to connect with the app so the issue is no longer there.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 14, 2019 at 04:19 PM

    In the time of Suite on HANA (SoH) SAP also had the architecture of mixed OData Service from ABAP and HANA XS. To solve the CORS problem the recommended architecture is the SAP WebDispatcher in front of the two Applicaiton Servers. Not sure how the user management was handled as normally the user is authenticated on the ABAP Stack using SAML as you mentioned. The same user must exist in HANA and you could configure SAP Logon Tickets (SSO2 Cookie) to pass the authentication to HANA.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.