Hi Team,

I have a requirement to implement caching in IBM API Connect v10.0.5 to avoid backend calls for a specific duration. I attempted to use the Invoke policy by configuring the Time To Live (TTL) to 60 seconds, but it didn't work as expected.

Could you please confirm if any additional configuration is required at the DataPower level to enable caching functionality? Your assistance on this would be greatly appreciated.

Hi Team,

I have a requirement to implement caching in IBM API Connect v10.0.5 to avoid backend calls for a specific duration. I attempted to use the Invoke policy by configuring the Time To Live (TTL) to 60 seconds, but it didn't work as expected.

Could you please confirm if any additional configuration is required at the DataPower level to enable caching functionality? Your assistance on this would be greatly appreciated.

Hi,

A couple of tips:

• You need to add "cache-putpost-response: true" as property of the invoke (add it via the source of the API code in API Manager - Develop)
• The OAS does not allow the use of basic auth with caching (a username / password) in the Invoke parameters so ensure they are cleared.
• Caching for API Connect should only be controlled at an API level not at a DataPower level. Any DataPower side caching is managed with internally by publishing the APIs to DataPower.
• The Invoke spec: https://www.ibm.com/docs/en/api-connect/10.0.8_lts?topic=execute-invoke

Hi Team,

I have a requirement to implement caching in IBM API Connect v10.0.5 to avoid backend calls for a specific duration. I attempted to use the Invoke policy by configuring the Time To Live (TTL) to 60 seconds, but it didn't work as expected.

Could you please confirm if any additional configuration is required at the DataPower level to enable caching functionality? Your assistance on this would be greatly appreciated.

Hi Team,

I have a requirement to implement caching in IBM API Connect v10.0.5 to avoid backend calls for a specific duration. I attempted to use the Invoke policy by configuring the Time To Live (TTL) to 60 seconds, but it didn't work as expected.

Could you please confirm if any additional configuration is required at the DataPower level to enable caching functionality? Your assistance on this would be greatly appreciated.

hi Manideep,

You need to provide the cacheKey value inside invoke action. The same cacheKey value you can find inside the DataPower appliance, if you search for "API document status"

Hi Team,

I have a requirement to implement caching in IBM API Connect v10.0.5 to avoid backend calls for a specific duration. I attempted to use the Invoke policy by configuring the Time To Live (TTL) to 60 seconds, but it didn't work as expected.

Could you please confirm if any additional configuration is required at the DataPower level to enable caching functionality? Your assistance on this would be greatly appreciated.