Hi,
as JK asked, what is the use case for using Reverse Replication? Previously it was used for synching of Users and User Generated Content.
We now do not support reverse replication of UGC, instead you should use xSRP( requires AEM Communities licence). For users and groups you should use Sling Content Distribution (SCD), which as a part of Sling requires no licence above your AEM licence.
So essentially the only use case left for reverse replication is for cq:page nodes. So if you do have a valid use case, from the documentation, reverse replication is a two step process:
As the publish environment is usually in the DMZ, to get content back to the author environment the connection must be initiated from the author instance. This is done with:
- an outbox in the publish environment where the content is placed.
- an agent (publish) in the author environment which periodically polls the outbox for new content.
So you have to enable two agents. But the docs do not give complete details on the setup, as you also need to get content into the reverse replication outbox on the publish instance. You could do this by using a launcher that listens for events relating to pages and adds them to the agent, this would be the better approach as you would not want to use on modification as you could end up in a an infinite loop. You also need to handle pushing content out from the author instance back to the publish instances. So there is a lot of work involved to get reverse replication working, so again it comes down to what is your use case?
Regards,
Opkar
[0] https://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/replication.html#Configuring Reverse Replication