Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Configuring Dispatchers pointing to Author Instances

Avatar

Level 1

I am trying to configure a dispatcher that will be sitting in front of two author instances (currently testing with just one instance though). Our goal is to improve the performance of the authoring environment. I was reading in this document

http://dev.day.com/docs/en/cq/current/deploying/dispatcher.html

And found a discussion about configuring for Author instances which included a link to a specific author_dispatcher_new.any file.

http://dev.day.com/content/docs/en/cq/current/deploying/dispatcher/_jcr_content/par/download/file.re...

So I used this file, only change I made was the /hostname value for /rend01. However, when I use this dispatcher.any file the only files that get cached are related to the login page (just 4 files). If I change the line that says /allowAuthorized "0" to a "1" instead, then I get a lot of files cached. But I'm not sure if that is safe. So I guess the question is, what are the recommended settings for the dispatcher.any file in front of Author instances since the one provided doesn't seem to be correct.

Thanks,

David

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

1. For setting up Dispatcher with author server, please refer to https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/dispatcher.html?lang=en#...

 

It has detailed steps. 

 

2. You can also refer to https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/dispatcher.ams.

It has samples for author specific files recommended by Adobe

 

You roughly will need author-specific:

- vhost

- Farm

- Filter rules

- Caching rules

- redirections if any

 


Aanchal Sikka

View solution in original post

3 Replies

Avatar

Level 1

Thanks for the reply. I reviewed the FAQ and there are two entries that seem related. The first one:

How do I configure the Dispatcher for the CQ author instance?

To improve authoring performance, it is recommended that you set up a Dispatcher in front of the author instance. See this knowledgebase article for the detailed steps.

I read through the knowledgebase article and it links to the same author_dispatcher_new.any file that I was already using (from the other page listed above). So I am already using that file. In addition, the instructions are the same one I was already following - basically, update the hostname, port and docroot.

The second FAQ entry talks about how to Cache Secure Content. This information makes sense, but I'm confused because the other information provided by Adobe/Day about configuring a Dispatcher for Author instances does not make any mention of setting up secure content caching.

Do I have to setup secure content caching? Am I missing something here? I am assuming that the only benefit of having a dispatcher in front of an Author instance is to cache Author editing related pages and assets (not actual web site content). So if these assets are not getting cached as far as I can tell I am getting no benefit from the dispatcher.

Avatar

Correct answer by
Community Advisor

1. For setting up Dispatcher with author server, please refer to https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/dispatcher.html?lang=en#...

 

It has detailed steps. 

 

2. You can also refer to https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/dispatcher.ams.

It has samples for author specific files recommended by Adobe

 

You roughly will need author-specific:

- vhost

- Farm

- Filter rules

- Caching rules

- redirections if any

 


Aanchal Sikka