AEM Communities Publisher Configuration effects

Avatar

Avatar

alinac41432981

Avatar

alinac41432981

alinac41432981

12-11-2019

Hi,

According to the Adobe docs on Communities Deploying Communities​, "When the deployment chosen is a publish farm, then one AEM publish instance must be identified as the primary publisher".

What is the implication of disabling the default enabled checkbox on a production publisher? We have for instance several scheduled jobs running. Is there any risk?

Best,

Alina

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

aemmarc

Employee

Avatar

aemmarc

Employee

aemmarc
Employee

13-11-2019

The point of identifying a primary publisher is to have a single Publisher handler things like sending notifications to users or analytics info to Adobe Analytics (if used).

For example : if you leave all publish instances as primary and a community member sends another community member an inbox notification then when SCD sync's the data between publish instances each publish will send a notification. This isn't really desirable so you assign a single Publish to handle these tasks.

In regards to the implication of disabling this, you should. If you have 4 aem publish instances synchronizing data via sling content distribution you only want a single one of those publishes enabled as primary, the other 3 should have that property unchecked

hope that helps

Answers (3)

Answers (3)

Avatar

Avatar

aemmarc

Employee

Avatar

aemmarc

Employee

aemmarc
Employee

13-11-2019

That is correct.

Avatar

Avatar

alinac41432981

Avatar

alinac41432981

alinac41432981

13-11-2019

Hi @aemmarc, thanks for your reply.

Just to confirm understanding correctly, disabling this option won't have any effect outside communities functionality for that publisher?

Best

Avatar

Avatar

alinac41432981

Avatar

alinac41432981

alinac41432981

13-11-2019

Is there any update on this request?