Multiple AEM Sites on a Local Dispatcher | AEM Community Blog Seeding

Multiple AEM Sites on a Local Dispatcher by Juan Ayala

Abstract

The dispatcher is an integral part of the AEM architecture. So important that it has made it into AEMaaCS. But it is simple and has not changed in a long time. In fact, I'm surprised it has even lasted this long. Its basic core functions are caching and filtering! Couldn't we do that with an Nginx module? Or a Traefik plugin? I'm willing to bet that in the years to come, it will get phased out in AEMaaCS. In favor of a more managed solution.


What has improved is the tooling provided by Adobe. When I first started on AEM, I remember setting up Apache on my MacBook. Ewww... Then I set it up on Vagrant. Then Docker. But with AEMaaCS, the tools are there for you already.


Before you can start spinning out sites, you will need two things. The dispatcher tools. And a working validation script.


Set up local Dispatcher Tools
This is already well documented. So I will not get into much detail. The gist of it is that once you finish, the tools directory is somewhere on your local machine. And the bin folder got added to the PATH environment variable. For example here is a short script I would use on a MackBook

unzip aem-sdk-xxx.zip
chmod a+x aem-sdk-dispatcher-tools-x.x.x-unix.sh
./aem-sdk-dispatcher-tools-x.x.x-unix.sh
mkdir -p ~/aem-sdk
mv dispatcher-sdk-x.x.x ~/aem-sdk/dispatcher
export PATH=$PATH:~/aem-sdk/dispatcher/bin

Read Full Blog

Multiple AEM Sites on a Local Dispatcher

Q&A

Please use this thread to ask the related questions.