Adobe Experience Manager Sites & More

gangadharpotala · 10/30/25

Hi Everyone,

I've setup a local Dispatcher for AEM 6.5 using the Adobe generic configuration, and it's working fine. Now I want to switch to using my project-specific Dispatcher configuration folder(which already exists in my project repository) instead of the generic one.
I followed this link:- https://medium.com/@toimrank/aem-dispatcher-setup-9dd2cc8cf253 to do generic setup.

Could someone please guide me on the proper step to:

1. Point the local Dispatcher setup to my project's Dispatcher configuration folder.

2. Structure and organize the project Dispatcher files(vhosts, filters, cache, etc.,) correctly

3.Integrate it smoothly with the existing AEM 6.5 local env.

4. Any best practices or references for project-level Dispatcher setups.

I just want to make sure I'm following the right approach before making the switch.

This is how my project dispatcher folder structure looks like:

Thanks in advance for your guidance!

Regards,

Gangadhar P

giuseppebaglio · 10/30/25

hi @gangadharpotala,
You can find a guide provided by Adobe for installing a Dispatcher that closely matches the AMS version at the following link: AEM Dispatcher Docker

I usually prefer using the Dispatcher tool included with the AEM as a Cloud Service (AEMasCS) toolkit, as I find it easier and more convenient: AEM Dispatcher Tools Guide

For best practices, you can refer to the AEM Archetype to gain deeper insights into the recommended structure. Here is the folder for AMS: AMS Dispatcher Archetype

Additionally, I recommend reading this official page on the security checklist for a more comprehensive understanding: Security Checklist for AEM Dispatcher

gangadharpotala · 10/30/25

Since I’m working with AEM 6.5 (on-prem/local) and not the AEM as a Cloud Service setup, my goal is to integrate our project-specific dispatcher configuration (non-AMS) into the existing local Apache dispatcher setup — without using Docker or the AEMaaCS dispatcher tools.

Could you please confirm if it’s fine to simplify:

Update the DispatcherConfig path in the Apache httpd.conf (or vhost) to point to my project’s dispatcher.any inside our repo (e.g., C:\CodeBase\myproject\dispatcher\conf.dispatcher.d\...), and
Keep the same structure as AMS style (conf.d/enabled_vhosts, conf.dispatcher.d/filters, cache, etc.), even if I’m running it locally against AEM 6.5 publish?

Also, are there any specific differences or compatibility issues to watch out for when applying the AMS-style dispatcher configuration in a non-cloud AEM 6.5 local environment?

Appreciate your guidance — I just want to make sure I’m aligning with best practices while keeping the setup consistent across local and AMS-like environments.

tatvam · 10/30/25

I have done this. And based on what you are saying, let's validate few assumptions.

You have the dispatcher module in code where all the mappings are already there. In which case all you have to do it point or include your dispatcher.conf (the file that has vhost) into your httpd.conf to associate the vhost to apache.
If the mappings need to be updated, then you'd have to do one step at a time by first setting up your apache vhosts, then the necessary rewrites and incorporate the dispatcher module and associated farms gradually.

muskaanchandwani · 10/31/25

Hello @gangadharpotala

1. Update the DispatcherConfig path in Apache’s httpd.conf or vhost file to reference your project's dispatcher.any file.
2. You can use the AMS style folder structure :
dispatcher/
└─ conf.dispatcher.d/
├─ dispatcher.any
├─ farms/
├─ filters/
├─ cache/
├─ renders/
├─ enabled_vhosts/
├─ rewrites/

AMS AEM 6.5 Dispatcher File Structure :
https://experienceleague.adobe.com/en/docs/experience-manager-learn/ams/dispatcher/basic-file-layout
https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/dispatcher.ams/src

Generic Documentation and Guidelines :
https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/dispatche...