How to distribute content in AEM across multiple publishers

The term “distribution” means the ability of picking one or more resources on a certain Sling instance in order to copy and persist them onto another Sling instance. The Sling Content Distribution module is able to distribute content by:

• “pushing” from Sling instance A to Sling instance B
• “pulling” from Sling instance B to Sling instance A
• “synchronising” Sling instances A and B via(third) coordinating instance C

In this blog, I am going to list down all the steps required for synchronising two sling instances.

Scenario in which synchronisation is useful:

Forums/End User interactions on the website

If your site allows your end users to add content to your website, then it becomes important for you to sync that content across different publishers.

This can be done by setting up Sync agents using Sling Content Distribution.In this set up, content which user adds on the site, gets created in one of the publish instance. Created content is then pulled by author instance and then published to another publish instance.

To enable Sync distribution, a few configurations needs to be done on both author and publish instances, which are listed below:

Configurations on Author Instance: