Was this article helpful?
Thanks for your feedback
SAP Commerce Cloud (Hybris) is one of the most efficient and flexible e-commerce project development platform. Specifically designed for B2B businesses and retailers, it offers unparalleled opportunities for digital transformation to these segments.
The new offerings of SAP Commerce Cloud enable marketers to create online offers on-the-fly for specific customers. SAP Commerce Cloud provides flexibility and adaptability to various business demands and helps in reducing dependency between different application modules.
Integrating Hybris with Contentstack
The headless and modular architecture of SAP Commerce Cloud makes it easy to integrate with Contentstack. To do that, you can use an open source solution named Kyma that facilitates integration between the applications, that is, Contentstack and Hybris.
Kyma manages the flow of business events in an existing enterprise solution such as SAP Hybris which results in extension modules to execute inside Kyma but outside the legacy applications.
You can create an application connector for Kyma that registers Contentstack events, received through webhooks. This could be any event in Contentstack such as update content (change in product description, and so on).
You'll also have to register the APIs in this connector and specify how the authentication will happen. The application connector will then establish authentication through certificates between the two services. The exchange of information using certificates between Hybris and Contentstack through the application connector in Kyma is called a handshake.
To understand this process, let's assume that you have a content type named Products in Contentstack with an entry for each product. These products are mapped to products in SAP Hybris let's say through the product IDs.
Now when you make any change in the product in SAP Hybris, it should update the corresponding product entry in Contentstack.
For this, SAP Hybris, after updating a product, will issue a certificate to the application connector in Kyma. It verifies the certificates and if the request is from a valid source, it is passed to another service, such as AWS Lambda, to make the relevant changes in the corresponding entry of the Product content type in Contentstack.
