Updating page on dispatcher instance with changed content fragment | Community
Skip to main content
W
wei_lyu
Level 2
December 8, 2022
Solved

Updating page on dispatcher instance with changed content fragment

  • December 8, 2022
  • 4 replies
  • 1418 views

Our app has an author instance, a publish instance and a dispatcher, all running on the same EC2 instance. We have a page containing a content fragment list component and when we publish a new content fragment or change an existing one, the page on the publish instance gets updated immediately but the page on the dispatcher doesn't. It seems like we need to republish the page every time we change something, but is there a way to configure it so that we only need to publish the content fragment and have the page on the dispatcher update automatically?

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

hi @wei_lyu ,

 

Unfortunately, this is not possible straight away. Similar issue will even happen with experience fragment as highlighted in the below thread.

 

Solved: Experience Fragment issue in Dispatcher - Adobe Experience League Community - 260332

 

Hope this helps.

 

Thanks,

Nikita Garg

4 replies

N
Adobe Employee
Nikita___GargAdobe EmployeeAccepted solution
Adobe Employee
December 8, 2022

hi @wei_lyu ,

 

Unfortunately, this is not possible straight away. Similar issue will even happen with experience fragment as highlighted in the below thread.

 

Solved: Experience Fragment issue in Dispatcher - Adobe Experience League Community - 260332

 

Hope this helps.

 

Thanks,

Nikita Garg

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    December 8, 2022

    You can use TTLs, so that the content refreshes regularly.

    For details, please refer to https://github.com/adobe/aem-dispatcher-experiments/blob/main/experiments/enableTTL/README.md

     

    If possible, avoid setting up low values on statfileslevel, it would affect dispatcher performance. Since, the cache would be refreshed too often

    Aanchal Sikka
      krati_garg
      Adobe Employee
      krati_gargAdobe Employee
      Adobe Employee
      December 8, 2022

      @wei_lyu 

      I believe such usecase is an ideal candidate for ACS Commons Dispatcher Flush, but on the official ACS Commons Page this tool is incompatible with AEMaaCS.

       

      However, on another thread, it is still possible, if you follow the OSGI Configuration via AEM SDK. Check this out -https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2798

       

      You can give it a try and validate

       

        W
        wei_lyuAuthor
        Level 2
        December 12, 2022

        I have tried configuring the publish instance for our content fragments, but it still does not seem to be working. Our team has decided to manually publish the page whenever a content fragment is updated.

        I do not think it is practical to add a flush rule every time we have a new page that references content fragments. I believe the automatic republishing of pages when content fragments are updated should be a default behavior. I hope Adobe can consider implementing this feature in future updates.

          arunpatidar
          Community Advisor
          arunpatidarCommunity Advisor
          Community Advisor
          December 9, 2022

          You can try

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

          Arun Patidar
            Terms & ConditionsAccessibility statement

            Loading footer...