Skip to Content
avatar image
Former Member

Sap Enterprise Portal :Calling OData Service

Hi ,

I have successfully deployed sapui5 app from webide to Portal 7.5.but when am running the app as a tile from launch pad ,its thorwing error.So i debugged and found that the Odata service now point to Portal server instead of gateway.

How to resovle this?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Jan 10, 2017 at 01:10 PM

    Hi Muhammed Safel .

    Actually you have developed the application like that only , considering the default server as your host for the services. But if you use other server services like directly using the gateway host names in the webservice URLs you will get the CORS issue which you can solve by creating destinations in Portal server. Check out this : https://blogs.sap.com/2013/10/09/how-to-consume-an-odata-service-using-odata-services-consumption-and-integration-osci/

    thanks

    Viplove

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 11, 2017 at 05:07 AM

    Thank you for the response. But its not the case.I am using the above System alias concept but the call from Portal is not successful.I think ,call has to be redirected to gateway service. but dont know how!

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 11, 2017 at 11:12 AM

    - http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> /IWFND/CM_MGW/001 The RFC call was not successful because of communication failure 'Illegal destination type 'G'.' - -

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 11, 2017 at 07:13 PM

    if you deploy to portal server, then normally your app can only call portal odata service, not abap server one.

    google same origin policy

    you need to put web dispatcher in place, if you want your scenario to work.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 11, 2017 at 11:10 PM

    Hi,

    I have same scenario, where UI5 app is running on portal which is on 7.4 and connecting to backend system through OData which is a R/3 system through web dispatcher(apache). That way you don't face same origin policy issue. Use a relative path for OData and write a rewrite run in apache to forward the request to your backend system(SAP R/3) for all your OData calls.

    Thanks,

    Dheeram

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 15, 2017 at 08:54 AM

    ThanksLet me try.I will keep you posted.

    Add comment
    10|10000 characters needed characters exceeded