AEM as a Cloud Service — Dispatcher Converter Tool | AEM Community Blog Seeding

[kautuk_sahni]

AEM as a Cloud Service — Dispatcher Converter Tool by Dinesh Chaudhary

Abstract

Overview
With Adobe Experience Manager (AEM) being available as a Cloud Service, there are a few notable changes on how Apache & Dispatcher configurations can be structured so that they can be deployed on the cloud. Below is an important if not exhaustive change list for dispatcher configurations on AEMaaCS.
Some Apache directives may not be used (for example Listen or LogLevel)

Only some pieces of the Dispatcher configuration can be put in include files and their naming is important. For example, filter rules that you want to reuse across different hosts must be put in a file called filters/filters.any.

There is an extra validation to disallow filter rules written using /glob to prevent security issues.
All virtual host sections should refer to port 80. Statement in virtual host section that refers to any port other than 80 will not get processed.

This article outlines the Dispatcher Converter which is part of the initiative by Adobe of developing code refactoring tools to make existing content (code, package structure, indexes, configurations) compatible with AEM as a Cloud Service. This tool converts existing AEM Dispatcher configurations to AEM as a Cloud Service compatible Dispatcher configurations by honoring the changes listed above along with the ones checked by validator script which comes as part of Dispatcher Tools mentioned here.

Read Full Blog

AEM as a Cloud Service — Dispatcher Converter Tool

Q&A

Please use this thread to ask the related questions.