Solved

Reverse replication issue -- Unable to enable the outbox agent

Forum|Forum|9 years ago
June 27, 2016
17 replies
8448 views

Hi Dear Community,

We're in the process of setting up reverse replication ( Pub to Auth). We have a single author instance publishing to 2 publisher agents.

We're failing to enable the outbox agent on publisher instance the "view Log" only results in "no such agent: outbox". We're using AEM version 6.1.0.20150507.

Could you guys point to any configuration steps we're overlooking.

Best,

John M

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 ogill

Hi,

as JK asked, what is the use case for using Reverse Replication? Previously it was used for synching of Users and User Generated Content.

We now do not support reverse replication of UGC, instead you should use xSRP( requires AEM Communities licence). For users and groups you should use Sling Content Distribution (SCD), which as a part of Sling requires no licence above your AEM licence.

So essentially the only use case left for reverse replication is for cq:page nodes. So if you do have a valid use case, from the documentation, reverse replication is a two step process:

As the publish environment is usually in the DMZ, to get content back to the author environment the connection must be initiated from the author instance. This is done with:

an outbox in the publish environment where the content is placed.
an agent (publish) in the author environment which periodically polls the outbox for new content.

So you have to enable two agents. But the docs do not give complete details on the setup, as you also need to get content into the reverse replication outbox on the publish instance. You could do this by using a launcher that listens for events relating to pages and adds them to the agent, this would be the better approach as you would not want to use on modification as you could end up in a an infinite loop. You also need to handle pushing content out from the author instance back to the publish instances. So there is a lot of work involved to get reverse replication working, so again it comes down to what is your use case?

Regards,

Opkar

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

Show previous replies

JK_Kendall

Level 9

Hi,

Perhaps you need to edit/configure the author agent.

Attached are screenshots of the author agent for AEM 6.0 when Communities used reverse replication for user generated content (nothing entered on Proxy tab).

- JK

bswx

Level 2

JK, I seem to lost your attachment, also its not showing up on thread. Please repost for me.

bswx

Level 2

JK, Thats seems to be exact same configuration I have. is there any other thing that needs to be done in order the reverse replication to work?

JK_Kendall

Level 9

Obviously, I'm not an expert. It really depends on your deployment (authors, publishers, dispatcher (if any)).

Instead of embedding, I've actually attached the screenshot of the OOTB configuration from AEM 6.0 this time.

If you've exhausted the knowledge of the forum, you might contact Customer Care to open a support ticket.

If you do so, please provide as much information as you can about your deployment (versions and topology) and your use case.

AnkurAhlawat-1

Level 6

As per my understanding from AEM 6.1 the concept of reverse replication is deprecated and no longer in use. In place of it AEM team comes up with a new concept of community sync. Which act a separate repository from where all publish servers will sync there data. In this data wont be reverse replicated back to author from publish instead it will go to a cntral repository and from there all publish nodes will get sync. This is introduced to reduce author resource utilization and make it highly available.

Please correct me if any one feel i am wrong.

regards,

Ankur Ahlawat

AEM CQ5 Tutorials

O

ogill

Accepted solution

Adobe Employee

Hi,

as JK asked, what is the use case for using Reverse Replication? Previously it was used for synching of Users and User Generated Content.

We now do not support reverse replication of UGC, instead you should use xSRP( requires AEM Communities licence). For users and groups you should use Sling Content Distribution (SCD), which as a part of Sling requires no licence above your AEM licence.

So essentially the only use case left for reverse replication is for cq:page nodes. So if you do have a valid use case, from the documentation, reverse replication is a two step process:

As the publish environment is usually in the DMZ, to get content back to the author environment the connection must be initiated from the author instance. This is done with:

an outbox in the publish environment where the content is placed.
an agent (publish) in the author environment which periodically polls the outbox for new content.

So you have to enable two agents. But the docs do not give complete details on the setup, as you also need to get content into the reverse replication outbox on the publish instance. You could do this by using a launcher that listens for events relating to pages and adds them to the agent, this would be the better approach as you would not want to use on modification as you could end up in a an infinite loop. You also need to handle pushing content out from the author instance back to the publish instances. So there is a lot of work involved to get reverse replication working, so again it comes down to what is your use case?

Regards,

Opkar

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

JK_Kendall

Level 9

(edited to correct my misinformation)

Hi,

Opkar provided the best explanation.

This is how the reverse replicaiton appears in AEM 6.1 and 6.2 :

from author :

agents on author - Reverse Replication Agent (publish reverse) is configured and active
agents on publish - Reverse Replication (outbox) is not active.

from publish :

agents on author - Reverse Replication Agent (publish reverse) is not active
agents on publish - Reverse Replication (outbox) is active.

If you're not using localhost:4502 for author and localhost:4503 for publish, then the configuration must be edited.

Reverse replication is used for AEM Communities when creating sub-communities (community groups) initiated by a privileged member on a publish instance.

These three features of AEM Communities do not use reverse replication :

1) tunnel service - eliminates the need to replicate users and user groups between author and publish instances. Enabling the tunnel service provides the ability to access users and user groups that exist on a publish instance from an author instance.

2) user sync - eliminates the need to replicate users and user groups among multiple publish instances (publish farm). This is an AEM platform feature being used by Communities based on Sling Content Distribution. While it is controlled by the author instance, these members and member groups are never created on author. (Note: publish-side users are often referred to as members.)

3) SRP - eliminates the need to reverse-replicate user generated content (UGC) entered on a publish instance. SRP manages a common UGC store

accessible to all author and publish instances, when using MSRP and ASRP,
accessible to all publish instances (but not author) when using a publish cluster for JSRP.

Details for developers are here : Storage Resource Provider for UGC.

- JK

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded