With AEM Commerce as a Cloud Service, brands with multiple Adobe Commerce deployments now enjoy the simplicity of a single experience management layer.
AEM is a powerful content management system (CMS) that seamlessly connects and streamlines the creation of digital content and media and its delivery to provide omnichannel, personalized customer experiences. Having a single experience management layer to combine and simplify these processes not only accelerates time to value (TTV) but also decreases the total cost of ownership (TCO).
In this post, Part 5 of our Commerce Integration Framework (CIF) series, we’re going to walk you through the steps of deploying a complex setup, connecting a single Adobe Experience Manager (AEM) as a Cloud Services environment with multiple Adobe Commerce deployments.
This is a new feature that was introduced in the latest release for AEM Commerce as a Cloud Service. So in this post, we want to give you an overview of the setup options, explain the architecture, and show you what a multiple commerce endpoint deployment looks like. We’ll guide you through the configuration steps, too. But first, let’s first look at a simple deployment to help you more fully understand the power of this new feature.
Simple deployment of AEM as a Cloud Services with a single instance of Adobe Commerce
Figure 1 illustrates a simple and pretty typical deployment of AEM as a Cloud Services together with a single instance of Adobe Commerce. This setup pattern is currently used by the majority of our AEM Content and Commerce customers. It works perfectly fine for one or multiple commerce websites. Using AEM Multi Site Manager, customers can roll out global stores and websites, each of them connected to a dedicated store configuration on Adobe Commerce.