Reverse replication only replicates back to author | Community
Skip to main content
October 16, 2015
Solved

Reverse replication only replicates back to author

  • October 16, 2015
  • 11 replies
  • 1930 views

Hi there

I've got an web application where the user has to enter some values into a form and then submit it. Upon submit, a cq:Page node is created on the publish instance. I'm setting the 3 properties cq:distribute, cq:lastModified and cq:lastModifiedBy in order to trigger a reverse replication.

While the replication back to the author works fine, it won't replicate it to the other publish instances. Is there something I have to configure on the author or in my code in order to tell the author to replicate the content back to all other publish instances?

Any tips are welcome :)

Thank you!

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 Scott_Brodersen

Sham HC wrote...

verify workflow launcher configuration in author comparing with fresh instance. You might have removed some OOB configs.

 

Here are the docs for that topic: http://docs.adobe.com/docs/en/aem/6-0/administer/operations/workflows/wf-start.html#Starting%20Workflows%20When%20Nodes%20Change

scott

11 replies

Sham_HC
October 16, 2015

verify workflow launcher configuration in author comparing with fresh instance. You might have removed some OOB configs.

October 16, 2015

How many publishers are you using ?

Is all agents connectivity is successful? and also test view logs in publishers and see /content successful.

AhatiusAuthor
October 16, 2015

Hi Gokul

We have 2 publish instances. Normal replication works fine, nothing is blocked. I can see in the reverse replication log, that the author pulled the modified page.

Do I need some kind of workflow?

Scott_Brodersen
Scott_BrodersenAccepted solution
October 16, 2015

Sham HC wrote...

verify workflow launcher configuration in author comparing with fresh instance. You might have removed some OOB configs.

 

Here are the docs for that topic: http://docs.adobe.com/docs/en/aem/6-0/administer/operations/workflows/wf-start.html#Starting%20Workflows%20When%20Nodes%20Change

scott

AhatiusAuthor
October 16, 2015

Scott Brodersen wrote...

Sham HC wrote...

verify workflow launcher configuration in author comparing with fresh instance. You might have removed some OOB configs.

 

Here are the docs for that topic: http://docs.adobe.com/docs/en/aem/6-0/administer/operations/workflows/wf-start.html#Starting%20Workflows%20When%20Nodes%20Change

scott

 

Hi Scott

Thanks for the documentation. To clarify my application a bit: It's an application for internal use, where all our dealers should enter the opening times of their store location. So there's a form which will take the times from monday to sunday. The location to save the times on the CQ server is /etc/openingtimes/dealers. Each dealer has it's own dealer-id, so my application first checks if there already is a node with the dealer-id. If there isn't a node of the type cq:Page is created, the name being the dealer-id. Under this node is a jcr:content of the type cq:PageContent, which has sub nodes for each department (the type being nt:unstructured). The department node has a node for each day (also type nt:unstructured) containing the hours as String.

Overall it would look like this:
/etc/openingtimes/dealers (nt:folder)
/etc/openingtimes/dealers/DEALERID (cq:Page)
/etc/openingtimes/dealers/DEALERID/jcr:content (cq:PageContent)
/etc/openingtimes/dealers/DEALERID/jcr:content/DEPARTMENTNAME (nt:unstructured)
/etc/openingtimes/dealers/DEALERID/jcr:content/DEPARTMENTNAME/DAYOFTHEWEEK (nt:unstructured)

I have now created a launcher on my author system, the config is like this:

[img]launcher.png[/img]

The Replicate opening times workflow looks like this:

[img]Workflow_1.png[/img]

[img]Workflow_2.png[/img]

But somehow it still won't replicate the nodes from the author to the other publish. Does the modified event type also trigger when a node is created within that folder?

Thanks for any feedback :)

AhatiusAuthor
October 16, 2015

Anyone? I have tried playing around with the workflow, but it still only replicates back to the author, not to the other publish instance.

Any hint on what might be wrong would be greatly appreciated :)

Sham_HC
October 16, 2015

Ahatius wrote...

Anyone? I have tried playing around with the workflow, but it still only replicates back to the author, not to the other publish instance.

Any hint on what might be wrong would be greatly appreciated :)

 


In workflow launcher use /etc/openingtimes/dealers(/.*)

AhatiusAuthor
October 16, 2015

Sham HC wrote...

Ahatius wrote...

Anyone? I have tried playing around with the workflow, but it still only replicates back to the author, not to the other publish instance.

Any hint on what might be wrong would be greatly appreciated :)

 


In workflow launcher use /etc/openingtimes/dealers(/.*)

 

Hi Sham

Thanks for your input :)

Unfortunately it still doesn't seem to work. To be sure it's nothing with our production environment, I've tried this on my local cq instances, but it won't work. After the author pulled the modified content to itself, this message appears in the logs:

com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl Is in same workflow: /etc/workflow/models/replicate_opening_times/model payload: /etc/openingtimes/dealers/620

I also tried using the default Reverse Replication Model, but that won't bring my dealer to the other publish instance either.

Thanks :)

Sham_HC
October 16, 2015

Ahatius wrote...

Sham HC wrote...

Ahatius wrote...

Anyone? I have tried playing around with the workflow, but it still only replicates back to the author, not to the other publish instance.

Any hint on what might be wrong would be greatly appreciated :)

 


In workflow launcher use /etc/openingtimes/dealers(/.*)

 

Hi Sham

Thanks for your input :)

Unfortunately it still doesn't seem to work. To be sure it's nothing with our production environment, I've tried this on my local cq instances, but it won't work. After the author pulled the modified content to itself, this message appears in the logs:

  1. com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl Is in same workflow: /etc/workflow/models/replicate_opening_times/model payload: /etc/openingtimes/dealers/620

I also tried using the default Reverse Replication Model, but that won't bring my dealer to the other publish instance either.

Thanks :)

 


That means flow is correct.  In replication agent can you verify if ignore default is checked?

AhatiusAuthor
October 16, 2015

Sham HC wrote...

Ahatius wrote...

Sham HC wrote...

Ahatius wrote...

Anyone? I have tried playing around with the workflow, but it still only replicates back to the author, not to the other publish instance.

Any hint on what might be wrong would be greatly appreciated :)

 


In workflow launcher use /etc/openingtimes/dealers(/.*)

 

Hi Sham

Thanks for your input :)

Unfortunately it still doesn't seem to work. To be sure it's nothing with our production environment, I've tried this on my local cq instances, but it won't work. After the author pulled the modified content to itself, this message appears in the logs:

  1. com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl Is in same workflow: /etc/workflow/models/replicate_opening_times/model payload: /etc/openingtimes/dealers/620

I also tried using the default Reverse Replication Model, but that won't bring my dealer to the other publish instance either.

Thanks :)

 


That means flow is correct.  In replication agent can you verify if ignore default is checked?

 

Hi Sham

On our production environment Ignore default is not checked on both publish-agents. Should it be activated?

Thanks for your help :)