WebIDE generated project and Service Metadata HTTP 404 not found error

[dianab]

Hi!

I have a problem with my generated webIDE project. I have the following constellation:

- OData Service in Netweaver Gateway Client works fine

- Clound Connector is installed centrally by our technology dep. (I did not change it)

- Connection to the backend system works, I was able to select and generate my project

- I did not change the neo-app.js file

- I have used WebIDE Full-Stack, SAP UI5 1.60 and NEO

- When I test my project, I get an HTTP 404 response at the first metadata service call

For me the first issue seems to be that I am not asked for my backed system username and password.

What do you think? Could this be related to the Cloud Connector?

[mariusobert]

Can you share the definition of the OData service in the manifest.json and the destination you created in the Cloud Cockpit?

[dianab]

Hi mariusobert

I attached a screenshot from the manifest file, where I cropped our namespace and the name of dev the system.

What also bothers me a little is the fact that the following link works and the metadata is returned:

https://webidecp-[...].dispatcher.hana.ondemand.com/destinations/[...]/sap/opu/odata/luneh/AP_GW_REGDATA_MAINT_SRV/$metadata?sap-language=DE

and the test from the WebIDE does not work:

https://webidetesting5985657-[...].dispatcher.hana.ondemand.com/[...]/sap/opu/odata/luneh/AP_GW_REGDATA_MAINT_SRV/$metadata?sap-language=DE

Any ideas?

Thanks!

Diana

[mariusobert · Accepted solution]

It's interesting that the https://webidecp-. links work, but the https://webidetesting5985657- links won't. So the destination and the Cloud Connector seem to work fine.

I'd assume this is a "routing" issue. E.g. it's related to the neo-app.json file.

In a sample app the manifest would define the data source like this:

"dataSources": {
	"mainService": {
		"uri": "/SAP_Gateway/sap/opu/odata/sap/SEPMRA_PO_APV/",
		"type": "OData",
		"settings": {
			"odataVersion": "2.0",
			"localUri": "localService/metadata.xml"
		}
	}
},

and the corresponding neo-app.json file should map the URI to the destination:

{
  "path": "/SAP_Gateway",
  "target": {
    "type": "destination",
    "name": "SAP_Gateway"
  },
  "description": "SAP Gateway ES5"
}

Does your neo-app.json file specifiy your individual path?

[...]/sap/opu/odata/luneh/ (or a subpath of this?)

[dianab · Accepted solution]

Hi mariusobert

It was indeed an error in my manifest file. I managed to correct it:

the URI must be exactly like in the SICF transaction.

Thanks!

[satya-dev]

Hi mariusobert i am facing similar issue but it is a mta app, deployed in Cloud Foundry.

 https://abcdd-sdk-xx-sdfd-approuter.cfapps.eu10.hana.ondemand.com/comsatyaapp/~220621184701+0000~/OD...  
Error: 404

but if i remove the /comsatyaapp/~220621184701+0000~ from the url, then it working
https://abcdd-sdk-xx-sdfd-approuter.cfapps.eu10.hana.ondemand.com/ODATA_1/sap/opu/odata/NS1/myservic...

xsapp.json:-

 {
        "source": "^/ODATA_1/(.*)$",
        "target": "$1",
        "destination": "ODATA_1",
        "authenticationType": "none"
    },

manifest.jsone:

"dataSources": {
   "mainservice": {
   "uri": "/ODATA_1/sap/opu/odata/NS1/myservice_SRV/",
   "type": "OData",
    "settings": {
         "odataVersion": "2.0",
         "localUri": "localService/metadata.xml"
     }
   }
},

I have created a destination in BTP.

Description= odata 100
Type=HTTP
Authentication=BasicAuthentication
WebIDEUsage=odata_abap,dev_abap,ui5_execute_abap,odata_gen,odata_xs
Name=ODATA_1
WebIDEEnabled=true
CloudConnectorLocationId=XXXXXXXXXXXXXXXXX
ProxyType=OnPremise
URL=http\://xxxxxx.abcdsed.yyy.zzzzz\:8000
sap-client=100
User=dsdsfdsfsd
WebIDESystem=XXX

Regards,

Satya

[former_member710882]

Did you find a solution to this? I am also getting a 404 when trying to fetch the metadata at -

https://xxxxxtrial.launchpad.cfapps.eu10.hana.ondemand.com/aggregation_admin_service.aggregationadmi...

But if I remove the timestamp it works -

https://xxxxxtrial.launchpad.cfapps.eu10.hana.ondemand.com/aggregation_admin_service.aggregationadmi...

[satya-dev]

Hi chall618,

Yes, i have found a solution, add data source in manifest.json as below:-

add ../.. before your service url,

	"dataSources": {
			"my_SRV": {
				"uri": "../../s4/sap/opu/odata/sap/my_SRV/",
				"type": "OData",
				"settings": {
					"odataVersion": "2.0",
					"localUri": "localService/metadata.xml"
				}
			},

Regards,

Satya