/etc folder content auto invalidate and update/publish to web server | Community
Skip to main content
mohanganesh
mohanganesh
Level 2
June 18, 2018
Solved

/etc folder content auto invalidate and update/publish to web server

  • June 18, 2018
  • 3 replies
  • 1232 views

The question is - when IT team updates either going in to JCR or through curl installation to publish an instance of AEM and this particular folder is also cached in web server through the dispatcher. what are the different automatic ways we can instruct AEM to auto delete or invalidate the cached content of this artifact from web server and server the new file/artifact?

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 joerghoh

No, the "on modification" trigger is only triggered by incoming replication events, but not by changes in the repository. If you manage to acticate content in /etc, then the "on modification" triggered replication agent will get active as well.

Jörg

3 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 19, 2018

On a publish instance you typically have the trigger "on modifcation" set. That means that on any change in the repo the respective location in the dispatcher cache is invalidated.

Another process I see often is the mandatory purge of the complete dispatcher on deployment. This helps also in the case that after deployment a component creates different markup than before. In that case the content itself hasn't changed, but the resulting page has changed.

mohanganesh
mohanganeshAuthor
Level 2
June 19, 2018

hey Jorg, I think i was the same path and after your response, i dug furthermore.  It seems like "on modification" works fine as long its "content" but its not triggering "Dispatcher Flush" for package installation or zip file which would have changed to /etc folder..

any further thoughts. how I can make AEM to indicate similar to "content" it should be able to flush and re-fetch the /etc folder artifacts aswell.

appreciate your response.

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
June 19, 2018

No, the "on modification" trigger is only triggered by incoming replication events, but not by changes in the repository. If you manage to acticate content in /etc, then the "on modification" triggered replication agent will get active as well.

Jörg

Terms & ConditionsAccessibility statement

Loading footer...