Hi all,
In AEM as a cloud service, Dispatcher needs to be accessed using Cloud Manager mandatorily?
Probably the architecture and the security restrictions force us to access Cloud Manager for Dispatcher and it could not accessed outside,
Kindly suggest.
Appreciate all your responses.
Thanks,
RK.
Solved! Go to Solution.
Views
Replies
Total Likes
In AEM cloud, Dispatcher configurations are part of code base in your maven project
So all the configurations changes should be done through code base and deployed using pipelines using cloudmanager
Yes @AEM_Forum, for AEMaaCS dispatcher logs can only be accessed from Cloud manager or aio.
For more clarity, please refer to https://blog.arborydigital.com/tailing-aemaacs-logs
https://www.aemcq5tutorials.com/tutorials/tail-logs-on-aem-as-cloud-service/
Views
Replies
Total Likes
Hi,
I am referring to accessing Dispatcher itself.
If I want to modify Dispatcher settings in AEM as a cloud service, how/where to access Dispatcher please?
Thanks,
RK.
Views
Replies
Total Likes
In AEM cloud, Dispatcher configurations are part of code base in your maven project
So all the configurations changes should be done through code base and deployed using pipelines using cloudmanager
All code changes in AEMaaCS have to go-through pipelines. This includes Dispatcher as well.
This rule assures that AEMaaCS lives upto the expectation of always available.
If code doesn't pass the pipeline's dispatcher validator, it can't be deployed.
All dispatcher configs/changes should be tested locally on dispatcher set-up deployed on docker.
Views
Likes
Replies