Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

SAP Web IDE cloud connectivity requires project folder direct below root node “Workspace”

In the HANA Cloud Platform cockpit I’ve setup a connection to the demo Gateway system. Next, in SAP Web IDE I created a new App project folder. As I prefer a manageable overview of all Apps (to be) developed in Web IDE, I created that App Folder in a subfolder beneath the Workplace folder:

This however gives problems within Web IDE wrt setting up the cloud connectivity.

Issue 1

neo-app.json generation is not available; that is, the menu option (New / Cloud Connectivity Configuration) is disabled on the project folder level:

It is only enabled for folders that are direct below root node 'Workplace'.


This issue/shortcoming can be pragmatic resolved by generated the neo-app.json file on a temporary project folder that is direct located below 'Workplace', and copy + paste it in the 2nd level project folder.

Issue 2

At runtime, the destination to the consumed OData service is not correct resolved, and data cannot be consumed. Via F12 I observe an HTTP 503 error on connecting to the REST service destination:

I duplicated the project folder direct below 'workplace' (via Web IDE export + import commands), and without any code nor configuration changes ran the App from this location. And now the HANA dispatcher does handle the request, and the accessed Gateway service returns data:

I compared the urls generated from Web IDE to the service destination in the 2 situation. The only difference is in the 'webidetesting<number>' part. Apparently there is some "magic" in Web IDE that reserves a dispatching url in HCP for service destinations, and that 'magic' is dependent on the project folder located direct below 'workplace'.

I considered as workaround to modify the 2nd level project in manifest.json and have it use the absolute connecting url to service:

However, that setup runs into a cross-domain issue, and is thus neither working:

The only resolution for this is to comply to the 'implicit rule' of Web IDE, and place the project folder thus direct below root node "Workplace". With the drawback that you loose the option to structure and classify your projects / Apps folders, and all need to be administrated at the same level as sibling nodes. I would rather be able to make in Web IDE visual groups of project / Apps folders per customer and / or functionality, e.g. for HR, Finance, Marketing. Perhaps in a next version of Web IDE?


13 Comments
Labels in this area