Highlighted

AEM integration with Akamai Fast Purge API for Single/multiple urls | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

962

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

962

Correct Answer

1.1K
kautuk_sahni
Community Manager

28-06-2020

BlogImage.jpg

AEM integration with Akamai Fast Purge API for Single/multiple urls by Ravi Pampana

Abstract

In AEM we can clear dispatcher cache on page activation by adding dispatcher flush agent but if we have Akamai on top of dispatcher as CDN then we need to manually clear Akamai Cache by going to akamai console.

Akamai provides fast purge API and using that we can clear page cache using single URL, CPCode, multiple urls etc

We can integrate Akamai Fast Purge API with replication agent so that for every page activation akamai cache gets cleared.

To integrate with Akamai Fast Purge we need below details (Contact Akamai for details related to your account)
1) Access Token
2) Client Secret
3) Client Token
4) Akamai Host

Read Full Blog

AEM integration with Akamai Fast Purge API for Single/multiple urls

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager

Replies

Highlighted

Avatar

Avatar

Shashi_Mulugu

MVP

Avatar

Shashi_Mulugu

MVP

Shashi_Mulugu
MVP

29-06-2020

@kautuk_sahni @Ravi_Pampana Where can we create this Replication agent author or Publishers?

Highlighted

Avatar

Avatar

Ravi_Pampana

MVP

Avatar

Ravi_Pampana

MVP

Ravi_Pampana
MVP

29-06-2020

On Author instance. 

Highlighted

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

962

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

962

Correct Answer

1.1K
kautuk_sahni
Community Manager

30-06-2020

@Shashi_Mulugu 

Replication agents are central to Adobe Experience Manager (AEM) as the mechanism used to:

1. Publish (activate) content from an author to a publish environment.
2. Explicitly flush content from the Dispatcher cache.
3. Return user input (for example, form input) from the publish environment to the author's environment (under control of the author's environment).

 

Even if you have multiple publishers, multiple replication agents would be on the Author.