Expand my Community achievements bar.

SOLVED

Dispatcher Flush Agent not triggering on receive

Avatar

Community Advisor

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?l...

 

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.


Aanchal Sikka

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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:

imrul001_0-1693230094575.png

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 

View solution in original post

2 Replies

Avatar

Community Advisor

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 

Avatar

Correct answer by
Community Advisor

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:

imrul001_0-1693230094575.png

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