Hi everyone,
I'm looking for the best way to upgrade our local SDK version for AEMaaCS. Right now, we're packaging our content and installing it in the new SDK, but this is really time consuming and a bit of a hassle to do every time we have a SDK upgrade.
Does anyone have any suggestions on a better way to do this, maybe a way we can automate this process to make things easier for all our developers?
Appreciate any help and resources, thanks!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @IshaJa
here you go https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/local-development-...
Hi Arun, I saw this but all those approaches are essentially the same where we package and install the content over to the new instance. I'm mainly looking for suggestions on how to automate the process.
Hi @IshaJa,
I solved this routine by creating of 2 bash scripts to setup AEM local instances (author and publish) and to migrate a content using a CRX2OAK tool (https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/upgr...). Example of command:
echo "Migrating content from $OLD_AEM_FOLDER_LOCATION to $NEW_AEM_FOLDER_LOCATION..."
java $CRX_2_OAK_JVM_ARGS -jar $CRX_2_OAK_JAR_LOCATION \
"$OLD_AEM_FOLDER_LOCATION/crx-quickstart/repository" \
"$NEW_AEM_FOLDER_LOCATION/crx-quickstart/repository" \
"--src-datastore=$OLD_AEM_FOLDER_LOCATION/crx-quickstart/repository/datastore/" \
"--datastore=$NEW_AEM_FOLDER_LOCATION/crx-quickstart/repository/datastore/" \
$CRX_2_OAK_INCLUDE_PATHS_ARG \
$CRX_2_OAK_MERGE_PATHS_ARG \
$CRX_2_OAK_EXCLUDE_PATHS_ARG \
$CRX_2_OAK_ADDITIONAL_ARGS \
--fail-on-error --copy-binaries --ignore-missing-binaries --log-level TRACE || error_exit "CRX2OAK migration failed"
Views
Likes
Replies