Overview of Dispatcher & Configuration in Apache Web Server for AEM by Lalit Kamble

Abstract

In this blog, you’ll learn about dispatcher and how to configure it with Apache web server. But before we get to that, let’s discuss AEM author and publisher.

Author

The content that will be published to the publisher is designed, created, and reviewed in the instance. It defaults to using port 4502. Author is the primary data source and can also be referred to as the parent instance.

Publisher

The data that we have replicated from the author to a mapped publisher is essentially contained in publisher, which is the child instance of the author. The role of the publisher is to share out the workload with the author. This instance’s default port is 4503.

Need for Dispatcher
AEM server is a content repository where data is stored, authored and managed. Though AEM itself can be used as a website server to end users, it can’t exactly handle millions of requests. And when those requests hit the AEM servers functionality slows down. There are certain things expected from a well-functioning website like security, caching, redirects, load balancing access requests, and more. That’s where Dispatcher comes into action to serve all this functionality configured with a web server communicating between AEM and the end user.

AEM and Webserver are two different applications and Dispatcher helps them communicate and manage the end user delivery. Dispatcher says what and when to perform.

Read Full Blog

Overview of Dispatcher & Configuration in Apache Web Server for AEM 

Q&A

Please use this thread to ask the related questions.