Skip to main content
T
ts10
New Participant
April 22, 2022

Clear dispatcher cache programmatically from publisher in AEM 6.x

  • April 22, 2022
  • 3 replies
  • 2342 views


Hello Community.
First time here 🙂
We have a requirement in which we need to clear dispatcher cache without publishing the page. We tried flush service options but it is not working for us. Looking for solution options to achieve this.

Thank you

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

arunpatidar
arunpatidar
New Participant
April 25, 2022

Hi,

If you are using ACS common then use https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-ui/index.html for clearing cache.

Arun Patidar
    T
    ts10Author
    New Participant
    April 25, 2022

    Thanks a lot. I will try this.

      Ravi_Pampana
      Ravi_Pampana
      New Participant
      April 22, 2022

      Hi,

       

      You can set dispatcher to have a ttl, check the below link

       

      https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-ttl/index.html

       

        T
        ts10Author
        New Participant
        April 25, 2022

        Thank you for the feedback. We will try to se what works best.

          DEBAL_DAS
          DEBAL_DAS
          New Participant
          April 22, 2022

          When do you want to clear the cache programmatically? Please brief us about the event in publish instance based on that you want to clear the cache programmatically.

            T
            ts10Author
            New Participant
            April 22, 2022

            The solution is supposed to work by updating the cache often with  json-ld markup. These updates happen very dynamically and often too. Because of this, it is not feasible to publish the page manually so often. 
            So, it is important that we are able to invalidate the dispatcher cache for content dynamically generated by our AEM connector. 
            Did I explain clearly?

              Terms & ConditionsAccessibility statement

              Loading footer...