Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Out of Box replication(publishing) limitation

Avatar

Level 1

In which use case/scenario do we need to write custom replication code for page activation. As per my understanding with out of box feature author can publish the page along its  associated assets, So Please suggest  OTB limitations. Thanks In advance 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@shahid1 ,

You can use OOTB replication to replicate single or bulk page activations

 

Until unless you have to activate pages  programmatically, you can use OOTB replication feature to activate pages. If you want to automate any thing then only you can go with custom replication feature.

Always best practise to use OOTB features of AEM.

 

Hope this helps!!

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@shahid1 ,

You can use OOTB replication to replicate single or bulk page activations

 

Until unless you have to activate pages  programmatically, you can use OOTB replication feature to activate pages. If you want to automate any thing then only you can go with custom replication feature.

Always best practise to use OOTB features of AEM.

 

Hope this helps!!

Avatar

Community Advisor

In my previous project we had an external system(non AEM application) and that system was responsible to create tags in AEM. 

 

Business wanted replace two old tags with newly created tags from already authored and published pages . Business gave us information like

1. we need to consider published pages created with specific template,

2. pages attached with tag1,tag2 (old tags and supposed to replace with the new tag)

 

First I wrote a groovy script to identify the list of pages (actually did the dry run) and shared that list with business for their review and confirmation. The count was something around 747 (definitely content author didn't want to update these many pages with new tag and published manually as it was a time consuming effort for them).

 

After getting the business confirmation I updated pages with newly created tag and published via same groovy script.

 

This is the one use case I can recall.

 

But I won't follow this approach in case of huge page count (like 5K). In that case I will execute update script individually on author and publish instances to avoid resources to get piled up in replication queue.