Dispatcher and cloud manager- Validation errors on windows | Community
Skip to main content
N
NitroHazeDev
Level 9
March 31, 2022
Solved

Dispatcher and cloud manager- Validation errors on windows

  • March 31, 2022
  • 1 reply
  • 1222 views

Can someone help me clear the validation errors with dispatcher please? I have two issues below and wondering if i can create a custom rewrite and filter. I used relaxed command and it successfully completed but with below command i face below issues

Including it as part of the source code and i do have custom rewrite rules and filters.

Running the command on windows gives me the below errors
>validator.exe full -d ../out ../src1
to be honest i could not resolve it with rewrite.rules as detailed in the site
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug.html?lang=en  

 

Issue -1

conf.d\available_vhosts\custom_author.vhost:69: included file (conf.d\rewrites\rewrite.rules) does not match any known file

conf.d\available_vhosts\custom_author.vhost:69: included file (conf.d\rewrites\custom_rewrite.rules) does not match any known file

I have tried both below in vhosts file
#Include /etc/httpd/conf.d/rewrites/custom_rewrite.rules
Include conf.d/rewrites/rewrite.rules

Issue-2
Wrt filters

 

 

conf.dispatcher.d\available_farms\002_custom_author_farm.any:20: file included at unknown location: /etc/httpd/conf.dispatcher.d/filters/custom_author_filters.any





This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

Hello @nitrohazedev 

 

Prefer using Flexible Mode with Dispatcher. It resolves the issues around naming conventions for files like reqrites.

 

  • Flexible mode - the recommended mode, and the default for AEM archetype 28 and higher, which is also used by Cloud Manager for new environments created after the Cloud Manager 2021.7.0 release. Customers can activate this mode by adding the folder and file opt-in/USE_SOURCES_DIRECTLY. By using this more flexible mode, there are no limitations in the file structure under the rewrites folder that in legacy mode required a single rewrite.rules file. Also, there is no limitation on the number of rules you can add. For details on folder structure and local validation, see Validating and Debugging using Dispatcher Tools.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/disp-overview.html?lang=en#validation-debug

1 reply

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity AdvisorAccepted solution
Community Advisor
December 4, 2023

Hello @nitrohazedev 

 

Prefer using Flexible Mode with Dispatcher. It resolves the issues around naming conventions for files like reqrites.

 

  • Flexible mode - the recommended mode, and the default for AEM archetype 28 and higher, which is also used by Cloud Manager for new environments created after the Cloud Manager 2021.7.0 release. Customers can activate this mode by adding the folder and file opt-in/USE_SOURCES_DIRECTLY. By using this more flexible mode, there are no limitations in the file structure under the rewrites folder that in legacy mode required a single rewrite.rules file. Also, there is no limitation on the number of rules you can add. For details on folder structure and local validation, see Validating and Debugging using Dispatcher Tools.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/disp-overview.html?lang=en#validation-debug

Aanchal Sikka
    N
    NitroHazeDevAuthor
    Level 9
    December 4, 2023

    Hi @aanchal-sikka 

    thank you for the details. Unfortunately back then recommendation was to pick from the experience.adobe.com and fine tune. That being said been over a year that I managed to solve and if I recollect it right I managed to ensure that the sym links were generated accurately, the machine was on, was not doing so. References as such was a mess. The rest on deployment via cloud manager took care of references vs what the windows version showed.

     

      Terms & ConditionsAccessibility statement

      Loading footer...