Setting up and troubleshooting Adobe IO Events can be intricate due to the multifaceted technology stack, which requires AEM and Adobe IO to work in tandem.
I’ve compiled a list of Common Problems and Solutions that I encountered while configuring this setup.
For detailed instructions on setting up Adobe IO Events, please refer: Enable Adobe IO Events in AEMaaCS
Continue readingIn certain scenarios, you may need to perform extensive processing in response to events occurring within AEM. Nowadays, Adobe I/O presents a contemporary solution in such situations to offload processing from AEM.
For example, say you need to invalidate Akamai cache upon page replication. In this scenario, you can capture the page publish event in Adobe I/O and trigger the invalidate call to Akamai through Adobe I/O using a runtime function. Alternatively, you could set up a webhook on Adobe I/O to make the API call directly from the webhook.
Context-Aware Configurations (CAC) in Adobe Experience Manager (AEM) provide a way to manage configurations for an AEM application in a flexible and context-aware manner. They allow developers to define and manage configuration settings that can vary depending on different countries or regions. So what are the benefits of CAC and why should we use them?
Continue readingTo implement SAML (Security Assertion Markup Language) on the publish environment in Adobe Experience Manager (AEM), following steps are required.
Continue readingMany a times there might be a requirement of migrating from an on-prem AEM website to AMS AEM or AEMaaCS. During the process of migrating from an old website to a new website, it is expected for the old website to continue operating until the new website is ready to go live. Once the go-live phase is reached, the old website is de-provisioned, and the new website takes its place on the same domain.
This transition involves a standard DNS switch that occurs during the cutover phase. However, if the customer opts to bring their own CDN (previously used for their legacy websites), a DNS switch is not necessary, and instead, the origin needs to be updated on the CDN. This article will focus on the latter scenario, exploring how it’s possible to conduct tests on the actual domain for the new websites much before going live to prevent any unexpected surprises on the day of the golive.
Continue readingIn certain cases, clients may have the requirement to use their own CDN(Bring Your Own CDN) in conjunction with Adobe Fastly CDN in AEM as a Cloud Service (AEMaaCS). This allows them to have greater flexibility in configuring the CDN according to their specific needs, as compared to Fastly which may have more restrictions. However, setting up this configuration requires careful planning and proper configuration to ensure it functions correctly.
Continue readingFor AEM Project development and delivery — we use the Author, Publish, Maven commands and Local Dispatcher setup (Start, Stop etc.)
For Mac Users — we can optimise the process by setting up the Alias for the frequently used commands which will improve the productivity — we will not need to look for the path again and again.
Continue readingBefore 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?
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 readingAssets 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 reading