Upgrading AEM 6.4 to AEM Cloud Service Commerce Code

[shelly-goel]

Hello,

We've got a requirement to upgrade from AEM 6.4 to AEM as a Cloud Service. Though the environment upgrade is fine, the CIF connector and commerce code does not work as is within the upgraded environment. Please suggest if AEM commerce code can be tweaked as per new project structure to work with AEM cloud Service and if 'Repository Modernizer' can be used for same. OR it would be better to re-write all the customizations (mainly frontend code) based on latest archetype.

The venia sample code have two profiles for cloud and classic. Could anyone suggest what's the technical difference between these two profiles and if the same codebase can be built for both cloud & classic then possibly can we also adjust our commerce code from classic to cloud compatible?

Venia Reference Store: https://github.com/adobe/aem-cif-guides-venia

Repository Modernizer: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/moving/refactoring-tools/re...

Thanks

[Vijayalakshmi_S]

Hi @shelly-goel,

Venia Storefront is a sample reference implementation that supports both AEM as a Cloud Service (cloud profile) and AEM 6.5 (Classic profile)
Now that you are working on upgrading the code base to AEMasCS, we should use cloud profile.

• Steps for setting up venia in our local Cloud Service SDK is documented as video in
  https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content-and-commerce/storef...
  • CIF connector is to be updated as Commerce add on which is available as a Sling Feature Archive(This is used in the above demo video) in Software distribution for AEMasCS and dedicated package for AEM 6.5.
• You can also try creating new archetype project using version 24 with includeCommerce - y for AEMasCS to arrive at the project structure followed and to know the differences with respect to your custom project code base.

Useful links from Adobe Docs related to this subject: (Ignore, if you have already checked)

• Notable changes with respect to commerce in AEMasCS is available in
  https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content-and-commerce/change...
• Migration guide : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content-and-commerce/migrat...
• Complete guide on Commerce in AEMasCS(including above docs) : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content-and-commerce/home.h...

[shelly-goel]

Thanks Vijaylakshi, I have those details. I was looking for how AEM cloud service upgrade will impact the commerce custom FE code. The sample venia store have same code for both classic and on-premise, just the profile is different. Does that mean only the packaging is different otherwise same code can be used.

[Vijayalakshmi_S]

Hi @shelly-goel,

Major difference between these profiles is the dependencies. Classic profile uses artifact named "uber-jar" while AEMasCS/cloud profile uses artifact named "aem-sdk-api"

Also with respect to this context, there are some excludes in config specific to profile as evident from ui.config,  ui.content and ui.apps modules.

[kautuk_sahni]

@shelly-goel We are coming with a Live In-person Meetup in New York on Content & Commerce Optimization.
See: https://adobe.ly/3A6DFYy  | Join and Invite your Peers.