Migrating /etc/map from AMS to AEMaaCS

[pardeepg4829047]

Hi,

We are migrating client website from AEM 6.5 (AMS) to AEMaaCS. As part of the migration, we noticed that existing 6.5 codebase has etc mappings defined under /etc/map like below:

Do we need to make any changes to these for cloud migration and for them to work as expected. 

[sravs]

Hi @pardeepg4829047 , This is still supported in AEMaaCS. Please refer for more information on resource mapping 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dep...

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/seo-and...

[pardeepg4829047]

What about the runmode based mappings defined using the folders like map.publish.prod  OR map.publish.stage ? Will these also be supported as-is ?

[Jörg_Hoh · Accepted solution]

I am not aware that AEM supports this runmode-based mappings directly. You have to configure the ResourceResolverFactory per runmode and specify the different paths there.

[Albin_Issac]

Considering that AEM does not inherently support run mode-specific ETC map folders, this functionality can be achieved through a run mode-specific JCR resolver pointing to an environment-specific ETC map path. This approach is also applicable in AEM as a Cloud. However, a challenge arises as AEM as a Cloud enables the 'dev' run mode for all environments except for stage and prod. To support environment-specific ETC maps, the aforementioned solution must be combined with a Cloud Manager Variable. For more details, please refer to How to Configure Environment-Specific ETC Maps for AEM as a Cloud Service. Feel free to contact me if you have any questions.

Regards,

Albin

My Profile