Author: Rahul Aggarwal (Page 1 of 2)

Using AEM events in Adobe IO – AEMaaCS

In 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.

Continue reading

Context Aware Configs in AEM

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 reading

Test on the actual domain before go-live on AEM

Many 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 reading

Troubleshooting BYOCDN Integration in AEMaaCS

In 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 reading

Custom Namespace in AEM

Why 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 reading
« Older posts