Highlighted

Replication agents are central to Adobe Experience Manager (AEM) | AEM Community Discussion

kautuk_sahni

Community Manager

10-05-2020

BlogImage.jpg

Replication agents are central to Adobe Experience Manager (AEM) by Adobe Docs

Abstract

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 environment (under control of the author environment).

Requests are queued to the appropriate agent for processing.

Replicating from Author to Publish
Replication, to a publish instance or dispatcher, takes place in several steps:
1. the author requests that certain content be published (activated); this can be initiated by a manual request, or by automatic triggers which have been preconfigured.
2. the request is passed to the appropriate default replication agent; an environment can have several default agents which will always be selected for such actions.
3. the replication agent "packages" the content and places it in the replication queue.
4. in the Websites tab the colored status indicator is set for the individual pages.
5. the content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.
6. a servlet in the publish environment receives the request and publishes the received content; the default servlet is https://localhost:4503/bin/receive .
7. multiple author and publish environments can be configured.

Read Full Blog

Replication agents are central to Adobe Experience Manager (AEM)

Q&A

Please use this thread to ask the related questions.

AEM AEMIBlogSeeding Experience Manager