Commerce Multi-Store Setup multi-store
The ÃÛ¶¹ÊÓƵ Experience Manager (AEM) CIF Core Components can be used on multiple AEM site structures and the underlying GraphQL client implementation can connect to different ÃÛ¶¹ÊÓƵ Commerce stores / store views. This allows projects to implement complex multi-store / multi-site setups.
A video walkthrough detailing options for integrating multiple ÃÛ¶¹ÊÓƵ Commerce Store Views with ÃÛ¶¹ÊÓƵ Experience Manager Sites.
AEM Multi-Site Management features of Live Copy and Language Copy are used with the Commerce Integration Framework to globally manage sites across regions and locales.
The recommended setup is to use a 1:1 relationship between the AEM site and the ÃÛ¶¹ÊÓƵ Commerce store view.
To connect an AEM site and AEM CIF Core Components to a dedicated store view, do the following:
Configuration configuration
-
Configure multiple stores & store views according to the pattern described in ÃÛ¶¹ÊÓƵ Commerce Websites, Stores & Views
-
Make sure the connection between AEM & ÃÛ¶¹ÊÓƵ Commerce is working.
-
Create a child configuration of the CIF Cloud Service config following these steps:
- In AEM go to Tools > General > Configuration Browser
- Select the base configuration that you created
- Create a configuration using the steps described at point 2 above
This new configuration is created as a child configuration of the base one. You can now go to Tools > General > Configuration Browser and create the configuration settings.
note tip TIP Commerce catalogs can be addressed by using IDs or UIDs. UIDs got introduced in ÃÛ¶¹ÊÓƵ Commerce 2.4.2. Only enable this if your commerce backend supports a GraphQL schema of version 2.4.2 or later. -
Assign the child configuration to an AEM site
- Go to the AEM Sites console
- Navigate to the region or language root of your site structure. For example,
/content/venia/us _or_ /content/venia/us/enfor the Venia sample page - Select the page and open the page properties
- Select the Advanced tab
- In the
Configurationsection, select the configuration that you created at step 3