Broken mapping in AEM publishers

[stiegjo22]

In our QA AEM publishers, the mapping rules have changed, It now appears to be pointing to map/https/cps instead of map.publish/https/qa-cps on both QA Publishers. We checked the Apache Sling Resource Resolver Factory in both QA publishers and the mapping location looks correct. Why would the mapping not point to our QA environment defined in Apache Sling Resource Resolver Factory i? (the same configuration works fine in our stage and production publishers) Thanks.

[Lokesh_Vajrala]

Hi @stiegjo22 ,

Could this issue be related to a runmode change? Please verify the runmodes configured on the AEM publishers.

Thanks,

Lokesh

[konstantyn_diachenko · Accepted solution]

Hi @stiegjo22 ,

Sometimes it happens and restart of AEM is required to apply this change. Try to restart AEM publishers, but double-check that OSGi configuration for org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl with correct resource.resolver.map.location is present in right place.

In addition, I would suggest to restructure your /etc/map configurations in the following way:

1. Create env-specific folders with /etc/mapping
   1. /etc/map.publish.local - for local environments
   2. /etc/map.publish.dev - for dev environment
   3. /etc/map.publish.qa - for QA environment
   4. /etc/map.publish.stage - for staging environment
   5. /etc/map.publish.prod - for production environment
2. Create OSGi configuration for org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl for every env specific runmode and configure resource.resolver.map.location to the relevant /etc/map mapping:
   1. publish.dev - resource.resolver.map.location="/etc/map.publish.dev"
   2. publish.prod - resource.resolver.map.location="/etc/map.publish.prod"

Best regards,

Kostiantyn Diachenko.