AEMaaCS - what's the best way to upgrade local SDK version? | Community
Skip to main content
I
IshaJa
Level 2
September 5, 2024
Solved

AEMaaCS - what's the best way to upgrade local SDK version?

  • September 5, 2024
  • 2 replies
  • 1147 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
September 5, 2024

Hi @ishaja 
here you go https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/aem-runtime#how-to-avoid-content-loss-when-upgrading-the-aem-sdk 

Arun Patidar
    I
    IshaJaAuthor
    Level 2
    September 5, 2024

    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.

      konstantyn_diachenko
      Community Advisor
      konstantyn_diachenkoCommunity Advisor
      Community Advisor
      September 5, 2024

      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/upgrading/using-crx2oak). 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"

       

      Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
        somen-sarkar
        Community Advisor
        somen-sarkarCommunity AdvisorAccepted solution
        Community Advisor
        September 6, 2024

        Hi @ishaja ,

        Pls check the below article . This can be helpful .

         

        https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/batch-script-for-efficient-aem-upgrade-a-developer-s-time-saving/td-p/702034

         

        Thanks,

        Somen

          Terms & ConditionsAccessibility statement

          Loading footer...