We have created our custom akamai flush agent, which should het triggered when we publish any page
http://localhost:4503/etc/replication/agents.publish/akamai-flush-agent.html
Test connection of akamai flush agent is successful but it is not getting triggered when we publish any page from author to publish instance.
Use Case - we need to get the page path in AkamaiTransportHandler.java in publisher instance which is getting replicated from author.
We have followed the documentation given in this https://aem.design/blog/2021/04/25/creating-akamai-flush-agent.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @SangramT ,
Please make sure you have dispatcher flush agent setup also along with Akamai flush set up. Akamai will pull content from dispatcher if its on top of dispatcher so in case flush set up is not done on dispatcher you will still see stale content.
Also when you do test connection check the post url where hit is going on Akamai and look for the correct access token provided by DevOps team.
THanks
Tarun
Hi @SangramT ,
Please make sure you have dispatcher flush agent setup also along with Akamai flush set up. Akamai will pull content from dispatcher if its on top of dispatcher so in case flush set up is not done on dispatcher you will still see stale content.
Also when you do test connection check the post url where hit is going on Akamai and look for the correct access token provided by DevOps team.
THanks
Tarun
@SangramT Follow below blog which will help you to clear CDN cache
https://javadoubts.com/event-purge-cache/
https://javadoubts.com/workflow-purge-cache/
Additionally, You can also try using AEM preprocessor to clear cache while replication.
Please find the below link for reference
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies