Shulou(Shulou.com)06/01 Report--

How to access the url and Destination of OData metadata by SAP UI5 application, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Create a new Fiori application in SAP WebIDE and access an OData service:

Run the Fiori application locally in WebIDE, and copy down the url of the metadata request in the Chrome developer tool:

Url is as follows:

Https:///sap/opu/odata/iwbep/GWSAMPLE_BASIC/$metadata?sap-language=EN

> if you post it directly to the browser, you can also see the returned metadata, but interestingly, the Destination that the Fiori application needs to use to retrieve the OData service is not reflected in the url caught by the local runtime in the WebIDE.

In the manifest.json file of the Fiori application, the datasources area maintains the endpoint of the OData:

"dataSources": {

"mainService": {

"uri": "/ sap/opu/odata/iwbep/GWSAMPLE_BASIC/"

"type": "OData"

"settings": {

"odataVersion": "2.0"

"localUri": "localService/metadata.xml"

}

}

}

There is also the models area, which indicates that the dataSource used by the OData model is mainService:

However, in the neo-app.json file (my Fiori application is created by selecting Neo environment in WebIDE), you can still see that the name of Destination is ES5_Trial_Neo:

This is the answer to the question about how SAP UI5 applications access OData metadata's url and Destination. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.