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

AEM as cloud service - Precautionary measures for content deployment

Avatar

Level 2

We are planning to use CRX Package manager to migrate content from Dev to STG environment on AEM as cloud service. The content includes pages, experience fragments, content fragments and assets. The total volume of contents to be transferred is less that 1 GB. 


Are there any precautionary measures to be taken before carrying out this operation? We used to stop the asset workflows when we did a similar activity in AEM on-prem. Are there any such steps to be followed before heading to the content transfer via the package manager?

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 9

You can disable post processing in AEMaaCS[1]. Default processing will happen anyways. I would suggest to break down package in smaller size(eg 200 MB) packages and collect data like how much time it took to install. Big packages sometimes does not install fully as per my experience on On-Prem. Keep an eye on logs as well.

Probably same content needs to be migrated on Prod as well so monitoring on Stage will help.

[1]

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/manage/asset...

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 9

You can disable post processing in AEMaaCS[1]. Default processing will happen anyways. I would suggest to break down package in smaller size(eg 200 MB) packages and collect data like how much time it took to install. Big packages sometimes does not install fully as per my experience on On-Prem. Keep an eye on logs as well.

Probably same content needs to be migrated on Prod as well so monitoring on Stage will help.

[1]

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/manage/asset...