Please let me know the steps required to carry out AEM integration with any eCommerce Engine using the AEM eCommerce Connector.
I am assuming that the Connector does some tasks on its own, rather than the developer doing everything from scratch.
I raised a similar query early, but did not see any traction.
Appreciate all your replies.
The job of a connector to Sync the Product Data between the eCom Plateform and AEM. The End user will see the product pages and other functionality like add to cart, order etc from AEM and once the order it placed the details will be placed to eCom Engine.
AEM always need a connector to integrate with commerce engine. For major of the shelf commerce systems Adobe or Partners provide integrations which are ready to use. List of connectors > eCommerce
Thanks for your inputs.
I already understood that the Connector offers these OOB components and functionalities.
My question is more from an implementation perspective.
What is it we, as developers, should do to have these many functionalities available to us from the connector?
Is this connector the same for all eCommerce Providers or it is different for each of them?
You may say that it is requirements driven, but kindly consider a typical scenario.
From eCommerce Provider perspective, I would think that we should perform the activities, listed in all our other tutorials, to create a eCommerce Provider.
With this, will the loop close or we need to do anything more to affect this integration?
Keeping my above reply to Navin in view, please clarify on the connector.
From your above post, it looks like the connector is different for each of the eCommerce Providers.
So, the coding for the advertised eCommerce Engines is already done.
Do we still need to add more coding on top of them to make them work?
Also, From eCommerce Provider perspective, should we perform the activities, listed in all our other tutorials, to create a eCommerce Provider, to .affect this integration?
The URL, Developing (generic) says:
"The integration framework includes an integration layer with an API. This allows you to build AEM components for eCommerce capabilities (independent of your specific eCommerce engine). It also allows you to use the internal CRX database or to plug in an eCommerce system and pull product data into AEM.
A number of out-of-the-box AEM components are provided to use the integration layer. Currently these are:
What do we mean by Out of Box?
Do we not need to customize/configure them?
In such a case, the API being the same, is the implementation of these components going to be different for different eCommerce Providers?
For some eCommerce Providers like Hybris, these implementations are already offered?
And for others, we need to write code?
I am sorry, I am not getting the full picture and that is why I once again request an Adobe Connect session at the earliest..
It is shipped as part of AEM.
Very likely yes, for example you want to display different attributes for a product or modify the cart ui.
No the components us the commerce API, so they are in depended of eCommerce Provider. Remember the architecture diagram the implementation of the commerce API (which is basically what is called connector) is taking care of the abstraction.
Yes for commerce providers on the help page we or partners provide the implementation. For others you need to write code, see the webinar links above.