Hi all,
I was trying to setup a dispatcher on our Linux server which is also running AEM on 4503. I followed the Adobe documentation at "Installing Dispatcher | Adobe Experience Manager"
When i add an entry DispatcherConfig conf/dispatcher.any inside conf/httpd.conf file, i am not able to restart httpd.
I have only modified the below files as per the documentation, attached them for your reference
httpd.conf file (placed under conf directory)
dispatcher.any (placed under conf directory)
If i comment the line which prevents dispatcher restart, from logs i could see dispatcher returning 404 and also says "Dispatcher set as handler, but not configured in server [publisher url]"
I am able to see Dispatcher initialized successfully message, so i know dispatcher module has been loaded successfully.
For a start i included wild cards under /virtualhosts in dispatcher.any. Added aem publisher URL under /renders . Anything else i am missing ?
Thanks for any help that you could offer.
Regards,
Abhishek
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
@kolluax have you tried to setup Apache first without dispatcher? It should work as a standalone webserver. Then we can dispatcher configs to make it dispatcher.
In your httpd file, I can't see VHost configuration inside which we need to configure dispatcher handles.
Views
Replies
Total Likes
When using AEM dispatcher locally, the local dispatcher typically won't start or function properly if your dispatcher validation rules fail. Dispatcher configuration validation is critical in AEMaaCS to ensure that the rules adhere to the strict configurations enforced by the cloud environment.
Use the validate.sh
script provided by Adobe within the dispatcher tools package to test and resolve any validation issues before deploying or running the dispatcher locally.
Documentation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/con...
Views
Replies
Total Likes