The AMS 2.0 Dispatcher standard/AEM as Cloud Dispatcher configurations enable modularized dispatcher configurations and also simplify and remove the duplicate configuration.
As shown in the below diagram, one of the major changes is using symlinks to avoid duplication of farm files and host configurations. In earlier versions, the farm and vhost files are duplicated under available and enabled folders, this leads to duplication and overhead for management — the changes should be applied in two different files.
In AMS 2.0/AEM as Cloud Service dispatcher configurations, the files are managed through symlinks, the actual file is inside the available folder, and symlink created to the file under the enabled folder. The symlinks are going to be relative to the available folder — ../available_vhosts/test.vhost
~/dispatcher/src/conf.d/available_vhots/test.vhost — original
~/dispatcher/src/conf.d/enabled_vhosts/test.vhost — symlink
/dispatcher/src/conf.dispatcher.d/enabled_farms/test_farm.any — symlink
We are in process of converting our existing Dispatcher configurations to AMS 2.0 Dispatcher Standard.I would like to understand one point that should we always create Symlink for the available confs and we need to follow this process strictly?Right now ,we have copied the confs. in available folder to enable folder and deployed ,aboe to deploy from Cloud Manager.Will it cause any issues if we follow this process ,recognizing virtual hosts?
How to create Symlink for the Dispatcher configured in Windows system locally?Any tools are available?