WebIDE deploys into ERP backend rather than Gateway server

[mkoch_wu]

I use WebIDE to develop and test UI5 apps using Cloud Connector, which links to our external on-prem Gateway server.

I now want to enhance a standard Fiori app (HCM My Timesheet Version 2), which is deployed and working on our Gateway server. To do this, I've tried to create an Extension Project in WebIDE.

However, when I select New ->Extension Project-> SAPUI5 ABAP Repository, I am presented with the (BSP) Repository from our ERP Development system, not our Gateway server. The external Gateway server works perfectly as our Frontend server and redirects oData calls to our ERP ABAP Dev backend without any problems.

Is there a setting which we have missed out to stop the "redirect" of ABAP Repository calls to the ERP backend?

Any hints and tips welcome!

M

[mkoch_wu · Accepted solution]

I have managed to find the answer myself by thinking the problem through: if my deployment goes to the "wrong" system (ie the ERP Development backend) rather than to the external Gateway system, then surely the service call to Gateway which derives the UI5 apps has to use some kind of wrong parameter.

In our Gateway system, I checked /IWFND/MAINT_SERVICE and looked at the Customising settings for the ADT (ABAP Dev Tools) Gateway service, which has been published from our ERP Development system. This is the service that WebIDE calls to derive all UI5 apps in the linked system (this service also does lots of other things, but lets leave this aside).

Low and behold, the customising settings for service ADT pointed to the SAP System Alias of our ERP Dev system! This meant that all calls were not pointing to the Gateway ABAP system. I created a new setting entry and set the SAP System Alias to "Local" and ticked the "Default" box, eh presto!, WebIDE started selecting and deploying to the correct ABAP system.

[thomasalexander_ritter]

Hi Michael,

I am glad you could figure this out by yourself. Just want to confirm that what you wrote is correct.

regards

Thomas (ABAP Dev Tools Team)