Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

AEM CIF and SAP Hybris Integration - Schema Issue

Avatar

Level 4

Hi Team,

 

We are trying to connect AEM with SAP hybris e-commerce using CIF.
In this process, we have followed the official documentation and reference guide and have adopted Diconium suggested Adobe IO reference implementation.

However, we are facing issues while resolving the response from Hybris and converting them into GraphQL schema (as all the Core components are tightly coupled with Magento schema). Do we have any detailed guide apart from reference documents to tackle it and any suggested approach recommended by Adobe that we can follow?
Any reference implementation for CIF Core components with Hybris and details will also be highly appreciated.

Thanks,
Manpreet

 

@kautuk_sahni

1 Accepted Solution

Avatar

Correct answer by
Employee

Mapping 3rd parties schema to the required schema is the main goal of the IO Runtime connector. If you change code in AEM, the CIF add-on will probably not work anymore.

 

View solution in original post

8 Replies

Avatar

Employee

You can find a detailed description on how the GraphQL connector works in https://github.com/adobe/commerce-cif-graphql-integration-reference. To ensure compatibility of your implementation with the CIF core components and CIF add-on, I recommend using the compatibility tool at https://github.com/adobe/commerce-cif-graphql-integration-reference/blob/master/schemas/README.md#co....

Avatar

Level 4

Thanks for your response @Herzog31.

 

As we are using SAP hybris backend and core components are designed based on Magento schema, what is the recommendation in cases of incompatibility  - modifying the schema or manipulating the response at the IO layer? Is there any implementation/documentation we can refer to?

 

Regards,

Manpreet

Avatar

Employee

By deploying the CIF connector on I/O Runtime,  you get the same API endpoint as with a Commerce instance. thus, the components will work. However, most customers build their own client-side components that directly talk to SAP Commerce OCC API. They only implement in the CIF connector what is needed to enable CIF authoring.

Avatar

Level 2

@Martin_Buergi_Adobe  Even if we deploy the IO runtime following the documentation, in case of 3rd part (hybris) the dialog fields with CIFcategroy picker and Product picker doesn't work and throws error.

Do we have any insight what query or series of operations happens to get the category from 3rd part (in case of magneto it works fine) 

 

Avatar

Level 4

Thanks for your response @Martin_Buergi_Adobe,

 

What is the recommendation in cases of incompatibility  - modifying the schema or manipulating the response at the IO layer? Is there any implementation/documentation we can refer to?

Also, we were trying to reuse the authoring capabilities of core components, especially the product and category picker. However, it seems that this is not a straightforward change by changing the configuration to our commerce endpoint but would rather need customization either in IO layer or native AEM library(mostly component js) files. Any insights here would be really helpful.

 

Regards,

Manpreet

Avatar

Correct answer by
Employee

Mapping 3rd parties schema to the required schema is the main goal of the IO Runtime connector. If you change code in AEM, the CIF add-on will probably not work anymore.