connectivity with backend service failing

[ShravanReddy80]

Hi,

When I use the policy, I am getting a 'transient failure connecting to remote: services.odata.org:80: connection failed: no usable address for service 80' error. Please help me out with this.

Please find attached the screenshots and the logs.

---- The mainRoutingPolicy screenshots Begin -----

---- The mainRoutingPolicy screenshots End -----

----The APIM GW Request-Response screenshot and logs Begin -----

The logs::: req-resp.txt
The failure logs start at line number 644.

----The APIM GW Request-Response screenshot and logs End-----

----External REST client call to the service endpoint without the asterisk works Begin -----
When I called the odata service without the asterisk, the call worked and I got the below response.

----External REST client call to the service endpoint without the asterisk works End-----

[cwiechmann]

Can you please change the FE-API Path:
From
/V4/(S(bwlyi5zyfdifrulnwfpj2f4u))/TripPinServiceRW/Airlines*
to:
/V4/TripPinServiceRW/Airlines*

And let me know, if this solved the problem? Perhaps the script doing the OData-Routing has issues with that. I tested it with exactly this FE-API-Path.

[cwiechmann]

Note: I'm really wondering about these log-messages:

get connection to host services.odata.org port 80 scheme http
no address for name services.odata.org, port 80: Name or service not known
transient failure connecting to remote: services.odata.org:80: connection failed: no usable address for service 80

Because they are pretty standard and logged, when the API-Gateway subsystem can't resolve the given hostname. Could you please make sure, that the API-Gateway server operating system can really resolve to services.odata.org?

[cwiechmann]

@ShravanReddy80, I have updated the Scripting-Filter slightly, as I have realized, that the issue appears when using the Try-It function in API-Manager/API-Portal.
When calling the endpoints that way, the star is included in the HTTP-Request and forwarded to the OData-Service, which returns you an error.
Even that is not a typical OData-Request, I understand that Try-It should work, so I improved this by removing the star.

[ShravanReddy80]

@cwiechmann , I pulled in the new policy and added the proxy server configuration. Now I am getting a 404 response from the endpoint.

At this point, I believe this might be an issue with the endpoint and that the policy itself is working fine. However, I wanted to share the results with you so that you can also check them out and confirm.

The logs: reqRespWithFixes_2018-05-08.txt

[cwiechmann]

@ShravanReddy80, hmm. The issue is the * at the end of the request. I assume you are using the API-Manager Try-It function, because this is using the registered API as it is (including the *).
I have changed the policy in a way to remove this *, but it seems not to work on your side, because it's send to the OData-Service, but it shouldn't. Not sure why!

Can you please try a request using an external program like CURL or Postman?
curl -k https://:8065/V4/TripPinServiceRW/Airlines

On my side this one is working as well:
curl -k https://:8065/V4/TripPinServiceRW/Airlines*

[ShravanReddy80]

@cwiechmann , It seems to have been a case of my deployment being overridden by someone else's deployment. I tested it now and its working fine. Thank you so much for helping me out with this.