reverse replication with distribution to multiple publisher

[ivanp2522110]

Dear AEM Community,

after reading the docs, I successfully configured normal replication from author to multiple publisher and also reverse replication from multiple publisher instances back to author. Now if I activate something on author, it goes to all the publisher and also if I trigger reverse replication on one of the publisher, the content gets copied to the author. Very nice

What I would like to do now is to make author propagate the new version, which it receives from one of the publishers to the rest of the publisher. So, whenever it gets something fresh from one of the publish server, it stores it locally and also distributes it among the other publish server.

What would be the smartest way to achieve this?

I was playing around with the 'On Modification' trigger of the replication agent. It actually did the job described above, but published instantly everything, even if the content is not activated (danger! danger!).

Thank you in advance!

Kind regards,

Ivan

[Lokesh_Shivalingaiah]

If you have set up publish agent to all publish instance from author, then author will automatically push all the changes to other publish instance once it receives update from one of the publish instance. Thats reverse replication.

However, reverse replication is kind of defferred from 6.x and recommended to use MongoDB in case you have any UGC.

[Jitendra_S_Toma]

Ivan,

You are looking for reverse replication and then replicating same content to other servers. May I know, What kind of content do you have?. Is it mostly UGC (User generated content) OR User's profile etc.

If it is related to UGC, As rightly pointed out by Lokesh, No more reverse replication for UGC. Though Adobe does provide other options (Like Cloud, MongoDB).

Jitendra

[Opkar_Gill · Accepted solution]

The recommended approach for UGC in AEM is to use the Communities capability[0] and the common store. You can't use the UGC storage capabilities of Cloud/Mongo without buying communities. 

For user profile distribution you can use Sling Content Distribution[2] as described here[1], however this functionality is OOTB in AEM.

Ivan, what is the use case you have that requires reverse replication?

Regards,

Opkar

[0]https://docs.adobe.com/content/docs/en/aem/6-1/administer/communities/srp.html

[1] https://docs.adobe.com/docs/en/aem/6-1/administer/communities/sync.html

[2] https://github.com/apache/sling/blob/trunk/contrib/extensions/distribution/README.md

[ivanp2522110]

Thank you kindly for the great answers. The content that needs replication is in fact UGC. We have some announcements created by visitors and they should be visible everywhere.

[Opkar_Gill]

You have to be very careful with using reverse replication, there have been issues with using this for UGC which is why it was removed in favour of the above options. Will you be enabling sticky connections on your LB, as the replication process will incur a delay while the content is replicated. For UGC as has already been mentioned, reverse replication is not recommended. 

Regards,

Opkar

[kimonp66895516]

Hi Opkar,

I realise it's been months since this post was active, so apologies in advance. :)

I was wondering what is the assumes solution for AEM 6.0. Currently, we have properly configure the reverse replication agents on both author and publishers and can see UGC reverse-replicated to the Author, but the same UGC is not "broadcasted" to all publishers. 

This means that if the UGC is found on Publisher1, then the same UGC is NOT found on Publisher2 (assuming you have 2 publishers in the scenario). Is this broadcasting assume to work out of the box or is there a suggested approach to tackle this (apart from upgrading to AEM 6.1/6.2, that is) ?

Best regards,

Kimon

[JK_Kendall]

Hi Kimon,

Looking at your 6.0 deployment, ensure you have the latest service pack (SP3 for the platform) and feature pack (1.5.171 for Communities, if you're using social communities components) and any other applicable hot fixes.

If you set up your publish farm correctly, then my understanding is, if you configure reverse replication properly, the main difference is the replication from publish to author.  Once reverse replicated to author, it should forward replicate to all publish instances as it does for all other content.

For example, if you create a page on author and publish it, check that the page appears on all publish instances.

You can try using the Geometrixx website and the replication setup out of the box to see, if that works (and it should), how it differs from your setup.

If you still have troubles, you could open a support ticket.  They would want as much detail as you can provide regarding your deployment, whether or not you're using a dispatcher, replication configuration (screen shots?), and any logs you have.

Hope that helps.

- JK