Shulou(Shulou.com)05/31 Report--

This article mainly explains how the Destination in the SAP WebIDE OData drop-down menu comes from. The explanation in the article is simple and clear and easy to learn and understand. Please follow the editor's train of thought to study and learn how the Destination in the SAP WebIDE OData drop-down menu comes from.

I had a problem with my development today:

I have a trial account and an official SAP Cloud Platform account:

The webIDE of the trial account is connected to the CloudFoundry of productive:

The WebIDE of the productive account is also connected to productive's CloudFoundry:

I found that when I created a new OData service, I couldn't select the Destination I created in the SAP cloud platform from the Service url drop-down menu.

How do you feel that the Destination taken by trial WebIDE is created by the trial neo environment?

The Destination in productive's WebIDE,system drop-down menu also comes from Destination in the productive Neo environment.

It seems that the Destination of the CloudFoundry environment is not considered at all.

Check the url of the webIDE I use again.

Trial:

Https:///

Then a github issue was discovered:

Create a Destination within the Cloud Foundry Environment Issue # 3398 SAPDocuments/Tutorials

When you learn that if you create UI5 applications in SAP WebIDE, you need to use Destination to connect to third-party services, you need to create Destination in the Neo environment, not in the CloudFoundry environment.

To verify, I created a Destination in the Neo environment again:

Then, sure enough, I saw this Destination created in the Neo environment in WebIDE.

The CloudFoundry endpoint maintained in WebIDE Preferences is only the destination for the deployment of developed UI5 applications.

So the question arises again, since the UI5 application is finally deployed in the CloudFoundry environment of the SAP cloud platform, what will the runtime do if the CloudFoundry environment does not have a corresponding Destination?

After my actual test, I found that I could not get the metadata of the OData service and reported a 500Internal Server Error error.

So I exported the Destination created in the Neo environment and poured it into the CloudFoundry environment, and this time I found that OData metadata finally successfully returned:

Thank you for your reading, the above is the "SAP WebIDE OData drop-down menu how to come from the Destination" content, after the study of this article, I believe you on the SAP WebIDE OData drop-down menu of Destination is how to come from this problem has a deeper understanding, the specific use of the need for you to practice and verify. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.