Category: Home

Context Aware Configs in AEM

Context-Aware Configurations (Context Aware Configs) 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. Here’s a more detailed explanation of Context Aware Configs in AEM:

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 deprovisioned, and the new website takes its place on the same domain. This transition involves a standard DNS switch that occurs during the cutover phase.

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

Quick Alias for AEM Developers

For 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 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