Before delving into setting up the SMTP integration, it is important to think about the following questions:
1. Advanced Networking Requirements : Is client SMTP public/internet or private/intranet?
Page 2 of 3
In AEMaaCS you can set environment variables using adobe IO CLI and use them in dispatcher using ${var}. But how do you do the same with the local dispatcher SDK.
This is fairly simple to do. All you need to do is associate your docker_run with your env variables file. Lets see how!
Continue readingWhy a namespace is required?
Assets metadata in AEM might be updated from multiple 3rd party systems. Namespaces help us identify the source of the metadata.
To persist custom metadata properties to the binary. Unless a namespace is attached to a property, the property will not be persisted to the binary.
Continue readingThough Localised XF say for header and footer, work fine with sling dynamic include on author and publisher, it doesn’t work properly on dispatcher. However with few small changes we can make this work for Localised XF’s as well. Lets see how.
Continue readingAEMaaCS sdk now comes with a docker dispatcher which can be run in a docker container. Setup is straightforward, just follow the below steps.
Continue readingA very common use case is to use multilingual/localised XF’s for header and footer for multilingual site. By default this is how the OOTB template is available in the AEM archetype as well and is the recommended approach to implement header and footer in Touch UI.
Continue readingAdobe Asset Link(AAL) panel allows creatives to access and modify content stored in AEM Assets directly via creative cloud apps.
Adobe Asset Link connects Adobe Experience Manager (AEM) Assets with Creative Cloud desktop apps Adobe InDesign, Adobe Photoshop, and Adobe Illustrator.
A very common use case is to use Experience Fragments/XF’s for Header and footer in editable template. In fact this is how the OOTB AEM archetype implements header and footer. However you would very soon notice issues with the caching of XF’s and would need to device a caching strategy. Lets discuss the issues and how to resolve them.
Continue readingA common issue with Experience fragment(XF) is cache invalidation of pages referencing the XF. When a Experience fragment(XF) is modified and published, pages which reference the XF are not updated and still shows old XF content. This happens because the XF content/html is cached as part of each page instead of being referenced from a shared location.
Page needs to be explicitly activated/invalidated to view the updated content of the XF. This can be quite tedious and unpractical at times for the authors. There are multiple ways to tackle this problem.
Following my previous post of setting up docker dispatcher for AEMaaCS, here is how you can do some basic troubleshooting like ssh into your container, checking logs, cache etc of your dispatcher running inside a docker container.
I would recommend installing this vcode extension to view and troubleshoot your docker containers.
Continue reading