Multiple domains dispatcher breaking in AEMCaas | Community
Skip to main content
A
abhishek_1421
Level 2
July 6, 2023
Solved

Multiple domains dispatcher breaking in AEMCaas

  • July 6, 2023
  • 2 replies
  • 2243 views

Hi Team,

 

I am facing a issue with dispatcher configurations with multiple Hosts.

I have 2 domains

www.domainA.com

www.domainB.com

 

I have defined vhost for them with entries

domainA.vhost:-

ServerName "www.domainA.com"

# Put names of which domains are used for your published site/content here

ServerAlias "127.0.0.1" "localhost" "*.local" "*.adobeaemcloud.com" "*.adobeaemcloud.net"

domainB.vhost:-

ServerName "www.domainB.com"

# Put names of which domains are used for your published site/content here

ServerAlias "127.0.0.1" "localhost" "*.local" "*.adobeaemcloud.com" "*.adobeaemcloud.net"

 

Akamai Configuration:---------------

www.domainA.com:-

  • Host header -> publish-p*****-e*****.adobeaemcloud.com
  • X-Forwarded-Host -> www.domainA.com
  • X-AEM-Edge-Key -> Environment key

www.domainB.com:-

  • Host header -> publish-p*****-e*****.adobeaemcloud.com
  • X-Forwarded-Host -> www.domainB.com 
  • X-AEM-Edge-Key -> Environment key

 

farm files and virtualhosts files are also separate for both of them as well the rewrite rules. But when I hit the domain, both of them resolve to single content path and take single farm file.

I have followed all public documents from adobe while setup

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/dispatcher-tools.html?lang=en

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn.html?lang=en

 

What am I doing wrong? I know from Akamai its going to dispatcher and taking first farm which has "*.adobeaemcloud.com", so it can be any of them. If I remove the entry from one file, the second domain is also taking same farm. In AMS we used to have loadbalencer which was working with same configuration and files were picked up as expected. In AEMCaas we do not have loadbalencer I think so, CDN is taking content directly from Dispatcher and configurations are breaking.Anyone faced same issue?

 

Thanks,

Abhishek

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

@tanika02 @rawvarun , guess what was the issue? 

 

Adobe Support Engg gave wrong X-AEM-Edge-Key  😀 . Instead he gave cache purge key. So whoever comes to this post please double check the key that you get from Adobe. Can't blame him, might be a human error. But it wasted my 3 days😏

 

Thanks,

Abhishek

2 replies

rawvarun
Community Advisor
rawvarunCommunity Advisor
Community Advisor
July 6, 2023

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-domains.html?lang=en explains how to configure Multiple domains in dispatcher.

    A
    abhishek_1421Author
    Level 2
    July 7, 2023

    Hi @rawvarun , yes I followed all these articles . All of my configurations are working in local and in AMS. Only issue is on the moment we move to dev cloud.

      Tanika02
      Tanika02
      Level 7
      July 6, 2023

      Hello @abhishek_1421  - 

       

      So basically it seems that you have configured separate vhost entries for domainA and domainB, as well as separate Akamai configurations. However, when hitting the domains, both resolve to a single content path and use a single farm file.

       

      Here are a few things to check : 

       

      1.Ensure that you have separate Dispatcher configurations for domainA and domainB. Check the Dispatcher configuration files (`dispatcher.any`, `dispatcher.vhosts`, etc.) to confirm that the configurations are correctly defined and separate for each domain.

       

      2.In the `dispatcher.vhosts` file, make sure that the Virtual Host entry for domainA is listed before the entry for domainB. The order of the Virtual Host entries can determine which one is selected when there are overlapping configurations.

       

      3. Double-check your Akamai configuration to ensure that it is correctly configured for each domain. Confirm that the `Host header`, `X-Forwarded-Host`, and `X-AEM-Edge-Key` values are set correctly for each domain.

       

      4.If you have caching enabled, ensure that the cache invalidation settings are configured correctly for each domain. It's possible that the content is being cached and served from the cache, resulting in both domains resolving to the same content path.

       

      5.Check the Dispatcher logs for any errors or warnings related to resolving the requests for domainA and domainB. Please share to help & understand the issue better.

       

      https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-domains.html?lang=en 

       

      https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-as-cloud-service-multi-domain-cors-configuration/m-p/594630 

       

      https://levelup.gitconnected.com/aem-multitenancy-running-multiple-websites-on-a-single-aem-environment-7eaf602c36d5 

       

       

        A
        abhishek_1421Author
        Level 2
        July 7, 2023

        Hi @tanika02 ,

         

        1. Checked, OK

        2. Both have different vhosts files with only their domain entry.

        3.Checked , OK

        4.Both domains have different cache docroot so they are making cache at respective folders.

        5. Both of them are picking up single farm that logs are coming up there.

         

        My real issue is

        in earlier versions of AEM we used to have loadbalencer, that loadbalencer was configured as origin host in CDN,and divides the load to dispatcher based on domain, but in AEMCaaS, Publisher/dispatcher/LB is same i.e publish-p*****-e*****.adobeaemcloud.com which is same for both the origin hosts. How dispatcher will understand that request is coming from domainA or domainB? That is the task of Vhost files. Even if they are different why are they picking up same farm again, they should pick up its own farm.

         

         

         

         

          A
          abhishek_1421AuthorAccepted solution
          Level 2
          July 10, 2023

          @tanika02 @rawvarun , guess what was the issue? 

           

          Adobe Support Engg gave wrong X-AEM-Edge-Key  😀 . Instead he gave cache purge key. So whoever comes to this post please double check the key that you get from Adobe. Can't blame him, might be a human error. But it wasted my 3 days😏

           

          Thanks,

          Abhishek

            Terms & ConditionsAccessibility statement

            Loading footer...