Replication Issue - Activate Node Programmatically

[adityaj]

Hi All,

We are trying to replicate the pages programmatically through:

           replicator.replicate(session,ReplicationActionTypes.Activate,path);

There seems to be some issue with replication.

The changes of the content which are getting published are not getting picked instead of that old content (Nodes present under jcr:content) is getting picked and replicated due to which the right content is not getting displayed on live site.

On author the pages are updated with the latest content, but the same content is not flowing to publishers while replicating programmatically.

When we are replicating the page through "quick Publish" option provided the latest content is replicated to the publishers.

Can anyone suggest what can be the possible issue or workaround.

Thanks,

[Mahedi_Sabuj]

Hi @adityaj,

Ensure that the Service User has the replicator permission. 

Additionally, are there any logs in the error.log file related to the replication process?

[adityaj]

The permission for user is available and In logs I can see that the path of the page which is getting replicated is also correct.

[Shashi_Mulugu]

@adityaj which version of aem you are using? Does your page has any dependent content on any other content artifacts such as images, content fragments,  exp fragments, data pages etc..? API replication doesn't ootb replicate references while you replicate references..

Also how many pages you are trying to publish at a time via API vs via manual quick publish.. Is it the same set?

[aanchal-sikka]

@adityaj 

• Please try replicating via OOTB process and check if that works. This will help assure that Author and publish IP mappings are correct.
• When you replicate via custom implementation
  • Check the path
  • Check that the replication completes
  • If you have access to CRXDE, verify content on publish
  • Assure the content is not cached.
  • Access page via Incognito mode 

[arunpatidar · Accepted solution]

Hi @adityaj 
Could you please check https://dev.to/jerinraj55551/replication-api-in-aem-adobe-experience-manager-405n?

It could be a permission issue, did you tried in local with admin access?

[kautuk_sahni]

@adityaj Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.