cancel
Showing results for 
Search instead for 
Did you mean: 

custom v2 service in mdk mobile connectivity destination throwing error

tirumala
Explorer
0 Kudos
248

here is my service : http://host:port/sap/opu/odata/SAP/ZDEMO_MDK_SRV/v2 in mobile connectivity dest...

i had checked in the logs the error will be :The host name http://host:port/sap/opu/odata/SAP/ZDEMO_MDK_SRV/$metadata is unknown 

how to resolve it when i try to create project in btp it was throwing error that : Error: Failed to access backend with error Request failed with status code 502, please check your destination in SAP Mobile Services cockpit

View Entire Topic
bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Have you verified that your cloud connector is properly connected and that your destination uses the correct location ID?

Your Mobile Services destination has a property Cloud Connector Location ID that must be set to the location ID value from the parenthesis (if set) for the cloud connector connection

Mobile Services Destination

MSdest.png

Cloud Connector Info from BTP cockpit

CloudConnector.png

I would also recommend clicking the Open in Browser button from the Mobile Services destination list in Mobile Connectivity to open the destination and pass authentication through to verify the connection.

OpenInBrowser.png

If the Open in Browser window opens to the service root you can replace the ?auth=uaa with /$metadata to verify you can access the metadata for the odata service.  If that works you should be ready to consume the destination.

tirumala
Explorer
0 Kudos

Hi @bill_froelich it is mandatory to provide the cloud connector id but did't see any thing like that in my mobile connectivity.

colud connector-1.png

and even i did not see any master instance in btp coockpit under connectivity cloud connectors

cloud connector-2.png

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos
If you backend system can be accessed directly fron the internet then you do not need a cloud connector. The Cloud Connector provides a secure path to access an internal system that that is not directly accessible. Based on your destination configuration you should be able to just put the full host name, port and path in your browser to test the connection
tirumala
Explorer
0 Kudos
Hi @bill_froelich i had connected to the cloud