AEM and ÃÛ¶¹ÊÓƵ Commerce Integration Using Commerce Integration Framework aem-framework
The Experience Manager and ÃÛ¶¹ÊÓƵ Commerce are seamlessly integrated using the Commerce Integration Framework (CIF). CIF enables AEM to directly access and communicate with the commerce instance using ÃÛ¶¹ÊÓƵ Commerce’s .
- This scenario, where CIF communicates with commerce via GraphQL.
- AEM Content Fragments work together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to deliver structured content for use in your applications.
Architecture Overview overview
The overall architecture is as follows:
Within CIF, there is support for server-side and client-side communication patterns.
Server-side APIs calls are implemented using the built-in, generic in combination with a for the commerce GraphQL schema. Also, any GraphQL query or mutation in GQL format can be used.
For the client-side components, which are built using , the is used.
AEM CIF Core Component Architecture cif-core-components
follow very similar design patterns and best practices as the .
The business logic and backend communication with ÃÛ¶¹ÊÓƵ Commerce for the AEM CIF Core Components is implemented in Sling Models. In case it is necessary to customize this logic to fulfill project-specific requirements, the delegation Pattern for Sling Models can be used.
Within projects, AEM CIF Core Components and custom project components can easily retrieve the configured client for an ÃÛ¶¹ÊÓƵ Commerce store associated with an AEM page via Sling Context-Aware configuration.
Search search
CIF provides out-of-the-box a that is a server-side rendered search experience based on . Commerce customers have the option to use Live Search instead. Follow this link to learn more about the CIF - Live Search integration.