Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

What's the best way to have custom dispatcher replication and flush

Level 1
Level 1

I am working on a requirement that absolutely need custom dispatcher replication and flush. Below are my requirements:

  • I have 1 publisher that serves content to 10 dispatchers.
  • Each dispatcher reside on premise that has internet connectivity constraint (via satellite), which they are periodically disconnected from the internet.

I have a logic (java code) to handle content replication and cache flush from dispatcher based on the availability of the dispatcher.

What I don't know how to do is to:

  • Completely disable out-of-the-box feature that replicates content from publisher to dispatcher when content author publish/activate content on author instance.
  • Completely remove dispatcher flush agent on publisher (this, I believe I know how, but I still want to ask and see if the recommendation is inline with my idea)

P.S. the AEM environment is AEM 6.3.

Any recommendation/help will be greatly appreciated.



3 Replies
Community Advisor
Community Advisor

Dear Sothea,

It looks like you solved the hardest part, the remained is to simply disable replication agent via it's settings. When it's disabled then replication does not happen. See this on further info [0]

[0] Replication



Level 1
Level 1

Thanks. Just clarify. I would like to disable AEM PUBLISHER from sending these requests:

#1) sent. Response: 200 OK ------------------------------------------------ Sending message to >> POST /dispatcher/invalidate.cache HTTP/1.0 >> CQ-Action: Activate >> CQ-Handle: /path/to/my/content >> CQ-Path: /path/to/my/content >> Referer: about:blank >> Connection: close >> Content-Length: 0 >> Content-Type: application/octet-stream -- << HTTP/1.1 200 OK << Date: Wed, 19 Sep 2018 04:11:31 GMT << Server: Apache/2.4.29 (Unix) Communique/4.2.3 << X-Frame-Options: SAMEORIGIN << Vary: User-Agent << Content-Length: 13 << Connection: close << Content-Type: text/html; charset=UTF-8 << << Message sent. ------------------------------------------------ Replication (ACTIVATE) of /path/to/my/content successful. Job for agent dispatcher1OAAgent processed in 253ms. Ok. sent. Response: 200 OK ------------------------------------------------

#2) Sending GET request to {protocol}://{host:port}/dispatcher/invalidate.cache