Best Practices for Managing Dispatcher Configurations Across Multiple Environments and Locales in AEM as a Cloud Service

Question

Hi Community,

We are managing multiple environments in Adobe Experience Manager (AEM) as a Cloud Service, including RDE, DEV, Stage, and Production, with approximately 60 locales (different DNS) per environment per program . Each environment requires its own dispatcher configuration, including vhosts and farm files, specific to each locale.

Currently, maintaining all these configurations in the same confd and confdispatcherd directories is creating significant clutter and complexity, making it challenging to manage and scale effectively.

Could you provide guidance on the following:

Best Practices for Structuring Dispatcher Configurations: Are there recommended approaches or strategies for organizing dispatcher configurations (vhosts, farm files, etc.) per environment and locale in AEM as a Cloud Service to reduce clutter and improve maintainability?
Environment-Specific Configurations: Is it possible to leverage run modes or similar mechanisms in AEM as a Cloud Service to manage dispatcher configurations specific to each environment (e.g., RDE, DEV, Stage, Production)?

Documentation or References: Could you share any relevant documentation, guides, or examples that demonstrate how to efficiently structure and manage dispatcher configurations in a complex, multi-environment, multi-locale setup?

Hemant_arora · Accepted Answer

Follow this link https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/ams-aem to migrate dispatcher from AMS to cloud. There are number of files which are irrelevant in cloud , just follow the instructions.
secondly its generally not advised to keep different configs for each environment, generally for even for multi locale we can keep same config for each environment. But sometimes customers have requirement where their redirect rules and other filters are different for each environment then you can do a set up like this

dispatcher/
├── src/
│ ├── conf.d/
│ │ ├── available_vhosts/
│ │ ├── enabled_vhosts/
│ │ ├── enabled_vhosts/dev.vhost

│ │ ├── enabled_vhosts/stg.vhost

│ │ ├── enabled_vhosts/prod.vhost
│ │ ├── rewrites/

│ │ ├── rewrites/dev

│ │ ├── rewrites/stg

│ │ ├── rewrites/prod
│ │ ├── filters/
│ │ ├── headers/
│ │ ├── variables/
│ │ └── rewrite.rules
│ ├── conf.dispatcher.d/

│ │ ├── available_farms/

│ │ ├── enabled_farms/
│ │ ├── cache/
│ │ ├── clientheaders/
│ │ ├── filters/
│ │ ├── farms/
│ │ └── virtualhosts/
│ └── conf/
│ ├── dispatcher.any
│ └── httpd.conf
├── docker/
│ └── Dockerfile
└── README.md

You would needy multiple farms in case you are configuring for multiple domains
for RDE , the dev config will work, or you can deploy dev or prod config whatever u want
The rewrites can manage pages to load locale specific content
Example

RewriteRule ^/([a-z]{2}_[a-z]{2})/$ /$1 [R=301,L]
RewriteRule ^/es_us/home.html /$1 [R=301,L]
RewriteRule ^/([a-z]{2}_[a-z]{2})/home.html$ /$1 [R=301,L]
RewriteRule ^/([a-z]{2}_[a-z]{2})/?$ /content/mysite/$1/home.html [PT,NC,L]

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded