What is “The Dispatcher”

Description description

Experience Manager

What is the Dispatcher?

See the following link for a basic description of what entails an AEM Dispatcher.

Table of contents

Resolution resolution

Apache Web Server

Start with a basic Apache web server installation on a Linux server.

Basic explanation of what an Apache server does:

  • Follows simple rules to serve files over the HTTP(s) protocols from its static document directory (DocumentRoot)
  • Files stored in a default location (https://experienceleague.adobe.com/var/www/html?lang=en) are matched on requests and rendered in the requesting client’s browser

AEM specific module file (mod_dispatcher.so)

Then add a plugin to the Apache webserver called the Dispatcher module.

Basic explanation of what the Adobe AEM Dispatcher module does:

  • Augments the default file handler
  • Filters out bad requests / Protects AEM’s soft belly/endpoints
  • Loads balances if more than one renderer is present
  • Allows for a living cache directory / Supports flushing of stagnant files
  • It’s the front door to all AMS installations, and it delivers websites and assets to the client’s browser
  • It caches requests to re-serve at a much faster rate than an AEM server could accomplish on its own
  • Much more

Web traffic workflow

Understanding which pieces are installed together to build a basic dispatcher server leads us to have you understand the basic web traffic workflow for an Adobe Manager Services configuration.
This should help you understand what role it plays in the chain of systems that serve content to visitors of your AEM content.

Serving already cached content

End User's Browser request
    → Cloud Provider Load Balancer
        → "The Dispatcher"
            → Checks for cached request locally if found
                → return request
                    → End User

Serving fresh content from AEM

End User's Browser request
    → Cloud Provider Load Balancer
        → "The Dispatcher"
            → Checks for cached request locally if NOT found
                → requests content from publisher
                    → publisher sends content
                        → dispatcher adds content to cache and replies
                            → End User

Content publishing/changes

AEM Author User activates content
    → Triggers content to be replicated to Publisher
        → Publisher gets content and triggers the flush request to Dispatcher
            → Dispatcher invalidates changed content
            * Next request for that content will request fresh copy from publisher