Hi Krishna,
Thanks for your answer. I'm still a bit confused about the central hub deployment.
In a central hub scenario, the service calls would be:
Fiori client --> web dispatcher --> front-end server --> backend server
My understanding is that the OData services would be deployed on the front-end server right? That would mean that the calls to the URL's/SICF services for the OData service would happen in the front-end server. When I have a look at the standard Fiori Track Sales Order Component below:
The UI5 app points to "/sap/opu/odata/sap/SRA018_SO_TRACKING_SRV/" as the service URL. Which would mean that it's pointing to the same host as where the UI5 app is deployed on(front-end server). Unless there is a config table somewhere that points the app to the correct Gateway Service server?
If the Fiori UI5 applications are deployed on the front-end server and the OData services on the backend server, how do we tell the app to fetch data from another host(back-end server)? Also, will we not run into CORS(cross origin resource sharing) issues?
Is it through this configuration table?
I thought the reason I was seeing RFC calls in the OData services of the standard Fiori apps were because in central hub scenarios a system alias will be maintained in the table above and the OData services would call the relevant functions in the backend system to read the data. I see alot of RFC_READ_TABLE calls and call function destination calls in the other Gateway Services so I thought this was the reason.
Thanks again for all your help.
Regards,
Alex