The Ultimate Guide to AD0-E207 Adobe
Analytics Architect Master
AD0-E207 Adobe Analytics Architect Master Certification Exam Credential. In complex setups,
you may use multiple Dispatchers. For example, you may use:
one Dispatcher to publish a website on the Intranet
a second Dispatcher, under a different address and with different security settings, to publish the same
content on the Internet.
In such a case, make sure that each request goes through only one Dispatcher. A Dispatcher does not
handle requests that come from another Dispatcher. Therefore, make sure that both Dispatchers access the
AEM website directly.
Using Dispatcher with a CDN
A content delivery network (CDN), such as Akamai Edge Delivery or Amazon Cloud Front, deliver
content from a location close to the end user. By that it
speeds up response times for end users
takes load off your servers
As an HTTP infrastructure component, a CDN works much like Dispatcher: when a CDN node receives a
request, it serves the request from its cache if possible (the resource is available in the cache and is valid).
Otherwise, it reaches out to the next closest server to retrieve the resource and cache it for further requests
if appropriate.
The “next closest server” depends on your specific setup. For example, in an Akamai setup the request
can take the following path
In most cases, Dispatcher is the next server that might serve the document from a cache and influence the
response headers returned to the CDN server.
Controlling a CDN cache
There are a numer of ways to control for how long a CDN will cache a resource before it re-fetches is
from Dispatcher.
Explicit configuration
Configure, how long particular resources are held in the CDN’s cache, depending on mime type,
extension, request type, etc.
Expiration and cache-control headers
Most CDNs will honor Expires: and Cache-Control: HTTP Headers if sent by the upstream server. This
can be achieved e.g. by using the mod_expires Apache Module.
Manual invalidation
CDNs allow resources to be removed from the cache through web interfaces.
API based invalidation
Most CDNs also offer a REST and/or SOAP API that allows resources to be removed from the cache.
In a typical AEM setup, configuration by extension and/or path, which can be achieved through points 1
and 2 above, offers possibilities to set reasonable caching periods for often-used resources that do not
change often, such as design images and client libraries. When new releases are deployed, typically a
manual invalidation is required.
If this approach is used to cache managed content, it implies that content changes are only visible to end
users once the configured caching period is expired and the document is fetched from Dispatcher again.
For finer-grained control, API based invalidation allows you to invalidate a CDN’s cache as the
Dispatcher cache is invalidated. Based on the CDNs API, you can implement your own ContentBuilder
and TransportHandler (if the API is not REST-based) and set up a Replication Agent that will use these to
invalidate the CDN’s cache.
See also AEM (CQ) Dispatcher Security and CDN+Browser Caching and recorded presentation on
Dispatcher Caching.
Using a Dispatcher with an Author Server
if you are using AEM with Touch UI you should not cache author instance content. If caching was
enabled for the author instance, you need to disable it and delete the contents of the cache directory. To
disable caching, you should edit the author_dispatcher.any file and modify the /rule property of the /cache
section as follows
