Dispatcher setup on Linux Error | Community
Skip to main content
K
kolluax
Level 3
December 17, 2024
Solved

Dispatcher setup on Linux Error

  • December 17, 2024
  • 3 replies
  • 924 views

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

Best answer by Shashi_Mulugu

@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.

 

https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/getting-started/dispatcher-install

3 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity AdvisorAccepted solution
Community Advisor
December 18, 2024

@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.

 

https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/getting-started/dispatcher-install

K
kolluaxAuthor
Level 3
December 23, 2024

@shashi_mulugu  Thanks for the reply, If you look at the last line on my httpd.conf, i have includes conf.d/*.conf , this directory contains a dispatcher.conf which has those handles configured. Again, even on this file for the directive "DispatcherConfig" when i define conf/dispatcher.any, my HTTPD wont start.

I think my problem is to try tell HTTPD (httpd.conf) where my dispatcher configs are (dispatcher.any).

How would i know my Apache is working ? When i hit the port i could see requests coming to access.log. Should i place a sample index.html under /etc/httpd (?) which is my root ?

 

@briankasingli  - This is an on prem installation, can i find this validate.sh under dispatcher configs downloaded from project archetype ?

 

Thanks,

Abhishek

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
December 19, 2024

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/content-delivery/validation-debug#local-validation-flexible-mode

 

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    January 7, 2025

    @kolluax  Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    K
    kolluaxAuthor
    Level 3
    January 7, 2025

    Thank you, i had to move the dispatcher handles into dispatcher.vhost.conf ( /conf.d) which fixed the issue. For some reason, having the handle within httpd.conf was throwing syntax errors and preventing restart. 

    Thanks,

    Abhishek

    Terms & ConditionsAccessibility statement

    Loading footer...