API Connect

Hi,

I hope you want to create a proxy for the backend Api. By using invoke policy in API Connect V10.0.5.x you can create the REST proxy. 

Hello Nirmalan,

Yes I wanted to create proxy for the backend API . But we have APIC as a Internal system and our network don't allow apic to connect with External client url. So that we need proxy similarly like we have in DataPower - user agent settings . 

Hi Kumar,

This was covered last year in the forum.  See https://community.ibm.com/community/user/integration/discussion/pushing-proxy-policies-via-cloud-manager-console#bm54b99f94-7142-4c78-8afb-06e1700fbf63.
Regards,
Steve

Hi Steve ,

Thank you, I will go through it.

Hi Steve,

I configured proxy details in API Gateway and Published API. I haven't tested the API , Since we are not able to connect to proxy yet. 

But configuring connection policies in API Gateway with proxy details wouldn't it be a proper approach rather than creating UDP for proxy?

Hi Kumar,
The proper approach would be to update the API Gateway object which would be best done with a Gateway Extension.  Please see https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=gateway-extensions-manifest and specifically the type gwd-extension.  Follow the links for that type to see the json file that would be referenced that would modify your API Gateway object on all the DataPower Gateways in your service.  The examples only show an update of something simple such as summary command (the object description), but the JSON object contains an array of strings where each string would be a CLI command line as was discussed in the previous post.  Using the Gateway Extension would then apply the configuration rules across all APIs for any invoke policy url that matches that would be sent via the proxy server.

I suppose anything is possible with a UDP, the old saying being it's just a simple matter of programming or a SMOP, but that would be code written and tested by you in XSLT or GatewayScript, most probably doing a url-open to your proxy server, and handling all of the different headers yourself whereas the API Gateway object would do that automatically and I'm sure much faster without any coding on your part.
Regards,
Steve