AEM and Magento Integration using Commerce Integration Framework

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,199 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,199 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

01-07-2019

Experience Manager and Magento are seamlessly integrated using the Commerce Integration Framework (CIF). CIF enables AEM to access a Magento instance and bind the catalog data via GraphQL. It also allows AEM Authors to use Product and Category Pickers and a read-only Product Console to browse through product and category data fetched on-demand from Magento. In addition, CIF provides an out-of-the-box storefront that can accelerate commerce projects.

Architecture

The overall architecture is as follows:

Architecture Overview

AEM Venia Reference Store-front

The AEM Venia reference storefront is a modern production-ready reference storefront showcasing a basic B2C commerce journey. It can be used to kickstart commerce projects and accelerate projects using AEM, CIF, and Magento. It demonstrates best practices for integrating AEM and Magento and shows how to use the Commerce Core Components. It also provides pre-sales with a reference site to demo the integration between AEM and Magento.

The project is open source and available on GitHub.

AEM CIF Core Components and AEM Authoring

Basic components are provided, common across commerce implementations such as Product Detail, Product List, Navigation, Search, etc. They can be used as-is or be extended.

The AEM CIF Core Components work like the AEM Sites Core Components but are dedicated to commerce specific use-cases.

These components key benefits are:

  • They are easy to use in your projects.
  • They can be used as-is or with very minimal modifications.
  • They provide best practices for connecting with Magento via GraphQL APIs or REST APIs

Components such as Product Teaser and Product Carousel are provided to enable AEM Authors to create Experience pages in AEM, combining marketing and commerce content. These components can be easily dragged and dropped on to a content page created in AEM and linked to specific products or categories using the Product or Category Picker in AEM.All the components are open-sourced on GitHub.

This shows full transparency on changes made going forward and allows you to get the latest version very easily. You can also provide pull requests for improvements and bug fixes that can be incorporated.

AEM Commerce connector for Magento and GraphQL

This connector provides integration of Magento products and categories in the AEM Commerce console as well as authoring features like product and category pickers. It also provides authoring features to display product and category information of data stored in Magento from within AEM by using Magento's GraphQL APIs

  • The AEM Commerce console shows a hierarchal view of products stored in Magento organized by category.
  • The Product Picker is an AEM Dialog field, similar to the Asset Picker, that would be used with an AEM Component to allow a user to select one or more products.
  • The Category Picker is an AEM Dialog field, similar to the Asset Picker or Product Picker, that would be used with an AEM Component to allow an author to select one or more category.

The AEM Commerce connector is expected to be used to enhance the AEM authoring experience with deeper integration with Magento products and categories.

It is open source on GitHub and you are welcome to contribute.

Even if you have very specific use-cases, the connector can be used a reference to build additional extensions to the AEM UI, but keep in mind that any extensions to the AEM UI can have an impact on future upgrades.

Read full article @ AEM and Magento Integration using Commerce Integration Framework

Community Resources:

Webinar Recording: https://my.adobeconnect.com/p5cqfbrtdbus/

Replies

Avatar

Avatar
Give Back
Level 1
Sharma_Shruti
Level 1

Like

1 like

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile

Avatar
Give Back
Level 1
Sharma_Shruti
Level 1

Like

1 like

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile
Sharma_Shruti
Level 1

21-10-2019

Can anyone please confirm that CIF Connector only works with secured GraphQL endpoint URL as the Magento I am using is currently not secured. While checking the logs, I get the message: HTTP protocol is not supported and while trying with HTTPS, it says - Connection Timed Out.

Avatar

Avatar
Ignite 3
Employee
venkateshs73486
Employee

Likes

10 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Ignite 3
Employee
venkateshs73486
Employee

Likes

10 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
venkateshs73486
Employee

05-11-2019

Hi Kautuk,

My customer is planning to use custom integration mechanism b/w AEM and Magento.

Though we have suggested CIF, they have reservations about using it.

Do you have any information on how many customers use CIF and how is the feedback?

That would help us in convincing them.

Avatar

Avatar
Boost 1
Level 1
venumuvva2019
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
venumuvva2019
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
venumuvva2019
Level 1

25-11-2019

Yes i have received the same error. They are not supporting http. Have you got your issue resolved?

Avatar

Avatar
Validate 1
MVP
Albin_Issac
MVP

Likes

106 likes

Total Posts

119 posts

Correct reply

33 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Validate 1
MVP
Albin_Issac
MVP

Likes

106 likes

Total Posts

119 posts

Correct reply

33 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
Albin_Issac
MVP

03-01-2020

Here is another blog with integrating AEM 6.5 with Magneto on-premise through CIF

https://www.albinsblog.com/2019/12/how-to-integrate-aem-with-magento-e-commerce-through-CIF-framewor...

Avatar

Avatar
Give Back 5
Employee
mhaack
Employee

Likes

17 likes

Total Posts

18 posts

Correct reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Give Back 5
Employee
mhaack
Employee

Likes

17 likes

Total Posts

18 posts

Correct reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile
mhaack
Employee

14-09-2020

Hi, this has been changed with the last release, which introduced a switch to use HTTP only as well. However, this is only recommended for local development or demonstrations. Don't disable HTTPS for production environments.