How Replication works in AEM?



Replication from author to publish


Replication, to a publish instance or dispatcher, takes place in several steps:

  • 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.

  • 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.

  • the replication agent "packages" the content and places it in the replication queue.

  • the content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.

  • a servlet in the publish environment receives the request and publishes the received content; the default servlet is http://localhost:4503/bin/receive.

  • multiple author and publish environments can be configured.




Replication from publish to author


Some features allow users to enter data on a publish instance, like user comments in product review etc.

Reverse replication uses an agent in the publish environment which references the author environment. This agent places the data into an outbox. This outbox is matched with replication listeners in the author environment. The listeners poll the outboxes to collect any data entered and then distribute it as necessary. This ensures that the author environment controls all traffic.



16 views0 comments

Recent Posts

See All

More about clientlibs in AEM

Here we will talk more details about clientlibs Static Resources in clientlibs Static resources below the client library folder must be in a folder called resources. If you do not have the static reso

Debugging Clientlibs

In this article we will discuss about how we can debug the js and css file in development environment. Let's see what are the debugging tools available in AEM. To see the embedded files in clientlibs