Hi 

I want to send few headers globally for every outgoing call from ibm api connect V10(notr for single api -for all outgoing calls from gateway to backends)

I have used datapower extensions when we were in 5.x version  .Now we are in v10 ,Any possible way to do it?

note; I don't want to publish apis to make it work and want to apply this globally

Thanks

------------------------------
phani juturi
------------------------------

Hi Phani,

You must have modified the webapi xml manager's user agent to inject headers in v5?  This capability doesn't exist in the v10 API Gateway.  I'd suggest you open a request for enhancement at https://integration-development.ideas.ibm.com/?project=APICONN.

Having said that, I will add that you can use a post-response global policy which you can do anything you wish for all API requests, including injecting whatever headers you wish to inject.  I believe this would be on a catalog basis, so not as nice as the overall service that the user agent gave you in v5 and that an RFE to add this to the API Gateway object would give you in v10, but still would be a helpful approach in the meantime.

Regards,
Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------

Steve, we have API Connect v10.0.5.2. We have a client that would like certain request headers passed downstream. Can this be done with some kind of a request policy at an API Product level?

Hi "EIS Developer",

The invoke policy allows you to specify an allow or block list of headers within message.headers when sending headers to your backend server.  I'm not aware of anything at a product level that would do this.

At a catalog level, you can configure a pre-request global policy where you are allowed to manipulate request headers that are inbound to all APIs in the catalog, but the question would be if you did setup the request headers to be only what your backend server wants to see, would any other headers you may have removed in this API preflow processing be required anywhere else in the APIs of that catalog?

Regards,
Steve