Hi I want to configure my cloud dispatcher for managing multiples websites.
I have read in a post something similar...
But I am in Cloud Service, not managed, so the dispatcher.any file of my configuration says:
#
# This is a file provided by the runtime environment and only included for
# illustration purposes.
#
# DO NOT EDIT this file, your changes will have no impact on your deployment.
#
I would like to point to my websites like this:
https://publish.adobeaemcloud.com/siteA goes to my site under /content/siteA/site--A/es/homeA.html
and
https://publish.adobeaemcloud.com/siteB goes to my site under /content/siteB/site--B/es/homeB.html
How can I configure my dispatcher to do this?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi
This is a pretty common scenario, there is an official documentation handling this scenario, please try to follow the steps from this resource https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-d... and post back if you have any issue.
Other good resources:
https://www.youtube.com/watch?v=065rFmiZxq0
https://www.theaemmaven.com/post/multiple-aem-sites-on-a-local-dispatcher
Hope this helps.
Hi
This is a pretty common scenario, there is an official documentation handling this scenario, please try to follow the steps from this resource https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-d... and post back if you have any issue.
Other good resources:
https://www.youtube.com/watch?v=065rFmiZxq0
https://www.theaemmaven.com/post/multiple-aem-sites-on-a-local-dispatcher
Hope this helps.
Hi Esteban.
The problem with this documentation is that they assume that we have a domain for each site. In our environment we must share the same domain for all the sites. Actually we have left one farm file to manage all the traffic.
We tried to use more than one farm, but dispatcher validation always fails in the deployment. In addition we can´t install docker in our PC´s and we haven´t a Linux environment to test the configuration.
If you have the same domain, I think what you need to do is rely on redirects and mappings, to automatically handle the map/resolve from "siteA" to "/content/siteA".
Please check these resources which will help you to solve your scenario:
https://www.youtube.com/watch?v=bJ_cXcAE7G8
https://blog.3sharecorp.com/shortening-urls-in-aem
For your redirections, you can even use this tool to test it online if you have trouble with your local dispatcher: https://technicalseo.com/tools/htaccess/
Thanks Esteban. I will check.
It is being very hard to configure the dispatcher ..... There is no an archetype or example for multisite and the validator always throws errors about farms, renders .....
In this case I would just use a single farm and implement rewrites on the dispatcher to perform these redirects.
But if you use a single farm then, you only have a virtual host, because the farm point to a single virtualhost isn't it?
Views
Likes
Replies
Views
Likes
Replies