We have a person who's main job is to build a package on our prod env, download it, then upload and install it on our 5 non prod environments on a daily basis. This is so our uat/test/hotfix envs etc. have the latest content.
Given the limitations imposed on Cloud AEM, is there a way to automate this? Maybe selenium scripts?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @TB3dock
To sync content between instances please use below 2 tools if you are having large amount of data.
1. Use Adobe recommended tools such as Grabbit and File Valut tools to synccontent if you have large data.
2. Create a package & install it on instance- If you have less amount of data.
Please find below information to understand and configure above mentioned tools in AEM.
https://github.com/TWCable/grabbit
https://relevancelab.com/2019/07/04/get-moving-with-aem-and-grabbit/
I hope this helps.
Regards,
Santosh
https://www.techinnovia.com/blog/
I could see a solution but still requires few more steps to be automated-
Look at this article once if that helps.
Hi @TB3dock
To sync content between instances please use below 2 tools if you are having large amount of data.
1. Use Adobe recommended tools such as Grabbit and File Valut tools to synccontent if you have large data.
2. Create a package & install it on instance- If you have less amount of data.
Please find below information to understand and configure above mentioned tools in AEM.
https://github.com/TWCable/grabbit
https://relevancelab.com/2019/07/04/get-moving-with-aem-and-grabbit/
I hope this helps.
Regards,
Santosh
https://www.techinnovia.com/blog/
Thanks for the reply, but the tools you mention here appear to be manual - we need to automate the process.
Please try https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html#:~:text=....
Effortlessly synchronize AEM Author instances, ensuring seamless updates for pages, assets, experience fragments, content fragments, tags, and /conf/* data. Compatibility with AEM CS, preservation of binary data, version history, and node ordering, all while benefiting from incremental updates based on jcr:lastModified/cq:lastModified.
Views
Likes
Replies