Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Delivered
Workspace API Connect
Created by Guest
Created on Mar 27, 2019

Global Caching and Cache invalidation

Case ID: TS001976381

Tool : IBM API Connect

Topic : Global Caching and Cache invalidation

Use Case

Policy Name : Invoke
Parameter : CacheKey

Background:
In the current scenario since the backend service doesn't support caching, API connect layer is expected to perform the cache. The scenario expects Multiple APIs to share the same Cache Key and fetch value from it based on the Time to Live values. However in certain scearnios based on the input, we would like to invalidate the cache and make sure the API calls the backend to fetch a new value. Once the new cache value is reset we would like the same value to be shared across other APIs as well.

Query:
1) We are unable to find a way to invalidate a cache in API connect within its lifetime. Is there a way these cache can be invalidated?.
2) Is there a way by which cache key-value pair can be accessed across multiple APIs?
3) Can the Cache value be overriden before the cache lifetime expires?

this is possible in other API products see example: https://docs.apigee.com/api-platform/reference/policies/invalidate-cache-policy

Idea priority Urgent
RFE ID 131417
RFE URL
RFE Product IBM API Connect
  • Admin
    SWETHA SRIDHARAN
    Reply
    |
    Aug 10, 2022

    Hi, It's possible to invalidate a cache entry if you are an admin of the Datapower.

    We added more Datapower-level abilities to affect Doc Cache settings in APIGW in v10.

    Thanks.

  • Guest
    Reply
    |
    Mar 27, 2019

    Attachment (Use case): Use Case Diagram