Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session

AEM 6.1 | Can we configure replication from publish to publish ?

Avatar

Level 3

Dear All,


I'm working on AEM 6.1 and I had stored data in page properties and i want to data will be updated from aem publish 1 to aem publish 2.
Example : I stored data pageview properties in page "/content/geometrixx-outdoors/en" of aem publish 1 and i want to data of pageview properties will be synced to aem publish 2.

Can we configure replication from publish 1 to publish 2 in this case?

8 Replies

Avatar

Level 4

Replication is from Author to Publish. I have never read thst  pub to pub is supported. A very unusual requirement. 

Avatar

Level 10

Hi,

Even though, if you have multiple publish Instances in AEM, it is not possible to configure replication agents between publish instances.

Thanks,
Ratna Kumar.

Avatar

Level 9

Hi Ratna,

Thank you for your reply. 

Had a couple of doubts.

#1] It is correct that replication is ideally meant for author to publish communication and vice versa. However, my doubt was where exactly will conflict happen if we ever try to go for publish to publish replication. I mean the corresponding api's will not support or content will get corrupted etc. Basically was trying to understand more on why this issue occurs.

Avatar

Level 2

Yes it will work, You have to create a publish agent in your publish instance(localhost:4505) under /etc/replication/agents.publish/publish as like author instance (/etc/replication/agents.author/)

For author instance Replication agent will be configured under /etc/replication/agents.author/

For publish instance Replication agent shouldbe configured under /etc/replication/agents.publish/

Avatar

Employee

Hi,

when trying to synchronise changes across publish instances you would use reverse replication[0]. In previous versions of AEM this was used to synch user generated content, users and pages. Reverse replication is no longer used UGC or users from 6.1 onwards, but can still be used for cq:page nodes as per the documentation [0][1].

To understand you use case further, is the property updated on the publish instance?

Regards,

Opkar

 

[0]https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/replication.html#Configuring Reverse Replication

[1]https://helpx.adobe.com/experience-manager/kb/HowToUseReverseReplication.html

Avatar

Level 10

Hi,

Agents can be configured to replicated between publish instance. However, If we replicate only between publish instance then it would get overriden when there is a replication happens from author to publish instances. As reverse replication is deprecated, you shouldnt be replicating from publish to author.

Now, to understand more on your requirement, why would you want to change the page properties only on the publish instance ? what is the usecase ?? shouldnt the page properties be same across the instances (Author and Publish)

Avatar

Employee

bsloki wrote...

Hi,

Agents can be configured to replicated between publish instance. However, If we replicate only between publish instance then it would get overriden when there is a replication happens from author to publish instances. As reverse replication is deprecated, you shouldnt be replicating from publish to author.

Reverse replication has not been deprecated[0], it is still supported for cq:page nodes. It is no longer supported for synching UGC and for users, Sling Content Distribution should be used.

[0] https://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/replication.html

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

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

Avatar

Level 2

Hi, I have a requirement such as this:
1. I need User Groups and Users on AEM 6.1 Author only. This is precisely authors, reviewers and approvers who can publish content.

2. I DO NOT need these users on any Publish, as those users are not the end-users.

3. I am setting up my Cold Stand-By Author now. I have created Active Author to Stand-By Author replication agent which is triggered On Receive and On Modification and works for all content changes or code changes.

4. Problem is, if new users or user groups are created, how do I sync between Active and Stand-By for User Groups, Users and ACL for User Groups (we are not providing any ACL at user level, they are only at group level).

All I see on blogs is Author to Publish farms using OSGi service which needs publish farm configuration. How about author to author ?

Best Regards,

Som