Dispatcher Flush Agent not triggering on receive | Adobe Higher Education
Skip to main content
aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
August 27, 2023
Resuelto

Dispatcher Flush Agent not triggering on receive

  • August 27, 2023
  • 2 respuestas
  • 888 visualizaciones

Hello,

 

I am trying to set up Dispatcher invalidation based on Receive events on AEM publish. The Dispatcher Flush Agent is set up on AEM publish as per https://experienceleague.adobe.com/docs/experience-manager-learn/ams/dispatcher/disp-flushing.html?lang=en#dispatcher-flush-replication-receiving-virtual-host

 

The agent is not triggering, when replicated content is received on publish. However, if I enable the "Modification" trigger in Agent and then manually update content on publish, it works fine.

 

Requesting suggestions on how to fix the "Dispatcher flush Agent" based on received event on AEM publish.

Este tema ha sido cerrado para respuestas.
Mejor respuesta de A_H_M_Imrul

Hello @aanchal-sikka,

 

As @kaikubad rightfully said, please make sure your author and publish servers can access the dispatcher server on port 80. The connection parameters in dispatcher can be found 

under "/etc/httpd/conf.dispatcher.d/enabled_farms/001_ams_author_flush_farm.any" and "/etc/httpd/conf.dispatcher.d/enabled_farms/002_ams_publish_flush_farm.any"

 

 

/allowedClients { /0000 { /glob "*.*.*.*" // allowing all IP to be able to access /type "allow" } }

 

 

 

Another point to note here is: while configuring the dispatcher flush agent make sure you put the correct host in the header:

The HTTP Header host: "dispflush" (for this example case) to work you should have a vhost file (ideally its called aem_flush.vhost and available OOTB from AMS) where the Servername is set to dispflush.

 

You can share more insight about your current setup for better help..

 

Thanks 

2 respuestas

kaikubad
Community Advisor
kaikubadCommunity Advisor
Community Advisor
August 28, 2023

Hi @aanchal-sikka ,
I am sure that you haven't made any mistake on following the documentation. I checked the documentation and our dispatcher setup. Both are same and working. Can you please check if the dispatcher ip is accessible from your publish environment?

Usually on AMS they are configured in a same private network so that they can be accessible from each other with private ip.

 

My assumption is the publish and dispatcher is not in same network or you need to put the private ip of the dispatcher with port no which is 80 

    A_H_M_Imrul
    Community Advisor
    A_H_M_ImrulCommunity AdvisorRespuesta
    Community Advisor
    August 28, 2023

    Hello @aanchal-sikka,

     

    As @kaikubad rightfully said, please make sure your author and publish servers can access the dispatcher server on port 80. The connection parameters in dispatcher can be found 

    under "/etc/httpd/conf.dispatcher.d/enabled_farms/001_ams_author_flush_farm.any" and "/etc/httpd/conf.dispatcher.d/enabled_farms/002_ams_publish_flush_farm.any"

     

     

    /allowedClients { /0000 { /glob "*.*.*.*" // allowing all IP to be able to access /type "allow" } }

     

     

     

    Another point to note here is: while configuring the dispatcher flush agent make sure you put the correct host in the header:

    The HTTP Header host: "dispflush" (for this example case) to work you should have a vhost file (ideally its called aem_flush.vhost and available OOTB from AMS) where the Servername is set to dispflush.

     

    You can share more insight about your current setup for better help..

     

    Thanks 

      Términos y condicionesAccessibility statement

      Loading footer...