Over the past cou­ple of weeks, we’ve cre­ated con­tent that addresses sev­eral top ques­tions related to the Adobe CQ Dis­patcher. This is in response to ques­tions we’ve heard from you, our com­mu­nity. I encour­age you to give a read and also check out the more in-depth doc­u­men­ta­tion I link to fur­ther below.

 What is the Dispatcher

The Dis­patcher is the Adobe caching and/or load bal­anc­ing tool that helps real­ize a fast and dynamic Web author­ing envi­ron­ment. For caching, the Dis­patcher works as part of an HTTP server, such as Apache, with the aim of stor­ing (or caching) as much of the sta­tic web­site con­tent as pos­si­ble and access­ing the website’s lay­out engine as infre­quently as pos­si­ble. In a load bal­anc­ing role, the Dis­patcher dis­trib­utes user requests (load) across dif­fer­ent clus­tered Adobe CQ instances (ren­ders).

 The graphic below gives an overview of the steps involved in con­fig­ur­ing the Dispatcher:
SV1

Click here to see a larger ver­sion of the graphic.

 New user assis­tance content

·         To under­stand Dis­patcher con­cepts and con­fig­u­ra­tion, refer to this FAQ. Wher­ever nec­es­sary, the FAQ leads you to the rel­e­vant doc­u­men­ta­tion and knowl­edge­base articles.

·         If you’re fac­ing issues while flush­ing the Dis­patcher cache, read this brand new trou­bleshoot­ing article.

 Have an unan­swered question?

We intend to make these doc­u­ments liv­ing, evolv­ing bod­ies of con­tent. There­fore, if you have a Dispatcher-related ques­tion that is not addressed in the FAQ, please feel free to post it as a comment.

Happy read­ing!

Samartha Vashishtha

Con­tent and Com­mu­nity Lead

@samarthav