Partially solved: VS Code App generator fails on premise

[patrick_weber11]

Hello,
I try to use Fiori Generator to connect to an oData service provided by an SAP ECC System which runs on premise.

After setting everything in generator like this

But Generator fails with this error message
{"message":"@sap/fiori:app generator failed - process.on(uncaughtException) process.on(uncaughtException) Cannot read property 'edmx' of undefined","stack":"TypeError: Cannot read property 'edmx' of undefined\n\tat default_1.prompting (C:\\Users\\myuser\\AppData\\Roaming\\npm\\node_modules\\@sap\\generator-fiori\\generators\\fiori-elements\\app\\index.js:1:117676)\n\tat processTicksAndRejections (internal/process/task_queues.js:93:5)"}

VS Code 1.62.3
SAP Fiori Tools Extension Pack 1.4.3
node.js 16.13.1

What's wrong here?

EDIT: I was able to create an app by connecting to Nothwind service https://services.odata.org/V2/Northwind/Northwind.svc/. So it seems to be caused by some way connecting to local ECC system. Are there any ICF services necessary (between the oData services itself obviously)?

Patrick

[IanQuigley]

Hello Patrick,

Sorry to hear you are having trouble with the generator. Can you please confirm that the service you have selected is successfully configured? That error shouldn't occur in the generator, but it means that it tried to parse the oData response from the chosen service and it didn't succeed. Are there any other services on that system that you could try, just to validate if its that specific service that has the issue.

Thanks,

Ian

[patrick_weber11]

Hello Ian,

im past, we used WebIDE to develop also on-premise and I want to try it with VS Code. So the service I want to connect to is already in use by our company. I'm also able to gather metadata of this service in browser which presents a valid document describing all entities and keys. So I think it is correctly available.

I tried different ways to connect to the service. As it is an ECC System, we run a dedicated Gateway system in front.

- if I try to connect to oData service using frontend URL (connect to an oData Service in VS Code), I get this error: "A connection error occurred, please ensure the target host is available on the network: "http code: UNABLE_TO_VERIFY_LEAF_SIGNATURE
This error I don't understand. Certificate chain is trustful and all certificates, root cert etc. are installed correctly
- if I try to connect to frontend server as an ABAP System, I get an error: "URI not found". Here I use the same server name, domain and port as I do when calling metadata in browser

- if I try to connect to backend system instead as ABAP Connection, I'm able to read the list of available services but the error shown in first post occurs

[patrick_weber11 · Accepted solution]

Hello,

after spending hours into this issue it finally works with some limitations. Our System landscape consists of a SAP ECC System (Backend) and a standalone Fiori Gateway system (frontend).

I'm not able to connect to frontend system (Option "Connect to a system"). For some reason, it always return "URI invalid", which is not true

I'm not able to connect to frontend system (Option "Connect to oData Service"). This gets caused as the system is configured to use SAML Authentication, which fails here. It is possible to also use basic authentication, but Yeoman generator doesn't provide this option.

But I'm able to connect to backend system (Option "Connect to oData Service"). After authentication, it provides a list of all known services (/ifwnd/maint_service). Read carefully, it provides a list of all KNOWN services, which means, it also shows services which are known but corresponding ICF node is inactive. You can't distinct if the service is really active or configured but inactive. If you choose a service which is inactive, the error I've posted as initial question occurs. Because we use this service in production (registered and active on frontend system) I didn't check if it also runs on backend system.

This just as reference, if someone else run into this issue.

[patrick_weber11]

I did some additional tests using Postman to verify the service I want to connect to.
We use some identity provider (SAML) which does authentication. So when I call an URL, an implicit redirect occurs to authenticate.

This doesn't work correct in postman which makes me think might me also true for VS Code generator. But when I provide credentials as basic auth in postman, the service metadata gets retrieved correctly without any further error.

So when I connect to the service as oData service instead ABAP on-premise, how can I provide credentials? I don't see any fields where I can enter credentials but they're necessary to connect successfully