Alternate for Reverse replication

Forum|Forum|9 years ago
April 20, 2016
8 replies
3006 views

Hi All,

As per my knowledge on Reverse replication functionality has be removed in 6.1. Any alternate way to handle reverse replication. I hope programatic way ie by updating the last modified, last modifed by and cq:distribute true still holds good in 6.1 for reverse replication process.

Any detailed information on this would be helpful.

Thanks,

Sagar Kumar

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by kautuk_sahni

Hi

Please find below the reference link for replication from publish to author below:

Documentation link:- https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/replication.html#Replicating from Publish to Author

I hope this would be helpful to you.

Thanks and Regards

Kautuk Sahni

smacdonald2008

Level 10

Here are 6.1 Replication docs: https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/replication.html. It still mentions replucation from pub to author.

kautuk_sahni

Accepted solution

Community Manager

Hi

Please find below the reference link for replication from publish to author below:

Documentation link:- https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/replication.html#Replicating from Publish to Author

I hope this would be helpful to you.

Thanks and Regards

Kautuk Sahni

S

sagarkmr0915Author

Level 3

Will it still remain in AEM 6.2. Just curious.

smacdonald2008

Level 10

We cannot comment on 6.2 - its not released yet.

S

sagarkmr0915Author

Level 3

OK. Thank you.

O

ogill

Adobe Employee

Hi Sagar,

reverse replication has not been removed in AEM 6.1 as shown in the links from Kautuk, what you may have read and be referring to is that reverse replication is no longer supported for the specific use case of User Generated Content (UGC), in this case the approach supported is to use the AEM Communities common store (xSRP).

The other use case for reverse replication was for synchronising users across publish instances in a TarMK farm, which was done via reverse replication. In this case, the recommended approach is to use Sling Content Distribution, here the users are synched with the author acting as a co-ordinator, the user accounts are never actually created on the author, the content merely passes through the author instance and onto the other publish instances in the farm.

Regards,

Opkar