Name: Integrating SAP Commerce Cloud and Composable Storefront with SAP Customer Data Cloud - Part 1
Uploaded: 2024-5-10
Duration: 629 s
Description: In Part 1 of this three-part video series, we’ll demonstrate an SAP Commerce Cloud and Composable Storefront Integration using the GConnector tool. You will learn what are GConnectors for CMS and eCommerce and get an E2E setup demo.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div>In Part 1 of this three-part video series, we’ll demonstrate an SAP Commerce Cloud and Composable Storefront Integration using the GConnector tool. You will learn what are GConnectors for CMS and eCommerce and get an E2E setup demo.</div></div></div></div></div>

Integrating SAP Commerce Cloud and Composable Storefront with SAP Customer Data Cloud - Part 1

In this three-part video series,  we’ll demonstrate an SAP Commerce Cloud  and Composable Storefront Integration  using the GConnector tool.   This video is Part 1 of 3.  You will learn: What are GConnectors  for CMS and eCommerce? The main features of GConnectors for CMS and eCommerce  Followed by an E2E setup demo.   GConnector for CMS or eCommerce is a tool that makes implementing Customer Data Cloud  within a CMS or e-commerce platform easy.   The customer's session and customer data  are synced in real-time  between Customer Data Cloud  and the CMS or e-commerce.   Some of the Key Features include:  Support for Customer Identity Session synchronization Secure by design  UID-based sync Field mapping and hooks for data transformation Easy logging and debugging And built-in localization support,  including inheriting language  from the CMS and fallback language definition.   Data sync between SAP Customer Data Cloud  and the CMS is based on the Customer Data Cloud UID.  This way, user information is independent of any input the user provides, such as name or e-mail,  and passed consistently between systems  to provide seamless integration  and improve the users' experience.   The CMS creates the UID field automatically  when the GConnector is installed.   When configuring Customer Data Cloud  for CMS integrations,  the e-mail is always the login identifier  included in the loginID.   Fields in one system are dynamically mapped  to the corresponding field in the other system.   By default, the GConnector usually maps the following fields  for every user in every CMS:  first name, last name, and e-mail.   The SAP Customer Data Cloud integration  provides a set of SAP Commerce extensions  to enable Customer Identity,  real-time customer data sync, managing of profile updates,  and user consent  from SAP Commerce Cloud.   SAP Customer Data Cloud screen-sets are implemented on the Commerce side as a set of CMS components  in the gigya-login-addon extension.   Customer Identity and Social login flows  are going through Customer Data Cloud.   Session Management First, choose whether you want the GConnector  to manage the sessions or use SAP Commerce Cloud.   If you choose SAP Commerce Cloud,  or Hybris,  then everything is handled by the Hybris CMS.   If you choose Customer Data Cloud  to lead the session, the GConnector will control when the sessions end.  You can utilize a single session configuration  between some or all your storefronts.   Multiple configurations are only necessary  if you want the storefronts to have different session configurations.   Field Mapping By default, the following required  SAP Commerce fields are mapped from SAP Customer Data Cloud  to SAP Commerce for registration,  login, and profile update:  UID and firstName  Data Sync  The data in the mapped fields is synced automatically  every time a user logs in or their profile is updated regardless of whether it is being updated via the user or a Backoffice User.  You can configure how the synchronization will be handled in your Customer Data Cloud configuration.  This synchronization happens  via tasks or in the same thread  as the update or login.   By default, all synchronizations  are asynchronous.   Let's get started with a demo.   We’ll set up the integration in three systems:  SAP Customer Data Cloud,  SAP Commerce Cloud,  and Composable Storefront.   First, go to the SAP Customer Data Cloud Console  to create a site and an application.   In SAP Customer Data Cloud Console,  choose Site Selector under the Sites menu   and choose Create Site  to create a site for the SAP Commerce Cloud integration.   On the Add Site popup,  enter the Site Domain   and choose a local data center – EU.   Choose OK to create the site.   Back on the Sites screen,  find the new site   and click on the API Key value  to copy and back up the site API key  for future reference.   To make sure the site’s screen-sets are initialized, navigate to the UI Builder  under the User Interfacing menu.   Wait for the Web Screen-Sets tab  to be fully loaded  and you can see the Default screen-sets.   Now, we can create the permission group and application for the SAP Commerce Cloud integration.  Navigate to the Administration section,   then under the Access Management menu  select Permission Groups  and choose Create Group.   On the Create New Group popup,  enter the name   and choose Create to create the permission group.   On the Permission Groups screen,  click on the three-dot actions menu  on the new group and choose Edit.   On the Edit Group screen,  choose the necessary privileges on the Privileges tab.   For example, you can give Write Access  to User Records,   Delete User Records under Identity Access,   and Full API Access under External Integrations  Choose Save to save the permission grants.   On the Scope tab, choose the site  you created in the previous step  for the integration   and choose Update Scope.   It’s OK to leave the default configurations  as they are in the other tabs.   Next, we’ll create an application  and assign the permission group.    Choose Applications under the Access Management menu   and then choose Create Application.   On the Create New Application popup,  enter the Name  and choose a permission Group.   Choose Create to create the application.   Now that the SAP Customer Data Cloud configurations are completed,  we can setup the connection  with SAP Commerce Cloud,  map the SAP Customer Data Cloud fields,  and configure the user sessions in the SAP Commerce Cloud Backoffice.   Note: The building and deployment  of SAP Commerce Cloud  and Composable Storefront on the Cloud Portal  will be covered in the part 2 demo.   In the Backoffice, navigate to Customer Data Cloud Configuration  under SAP Customer Data Cloud   and choose the plus button.   On the Create SAP Customer Data Cloud  Config popup, enter a code,   Customer Data Cloud site API key,   data center,   application key,  and secret.   Choose the SAP Commerce Cloud CMS site  from the dropdown menu   and choose Finish to create the Customer Data Cloud configuration.  Navigate to Session Configuration  under SAP Customer Data Cloud  and choose the plus button.   On the Create Session Configuration popup,  enter a code for the configuration.   Choose SAP CDC for Session Lead.   Choose Browser Closed for Session Type. Enter minus 1 for Session Duration in Seconds.   Choose the Customer Data Cloud configuration   and choose Finish  to create the configuration.   Navigate to Customer Data Field Mappings  under SAP Customer Data Cloud  and choose the plus button.   We’ll create two mapping  for the email and name fields.  Enter a code in the Create Field Mapping popup   and choose the Customer Data Cloud config.   Choose Both for Sync Direction.   Enter a name for Hybris Attribute Name.   Enter profile.firstname  for Customer Data Cloud Attribute Name.   Choose string for Hybris Type.   Choose Finish to create the mapping  for the name field.   Choose the plus button  to create a mapping for the email field.   Enter a code in the Create Field Mapping popup   and choose the Customer Data Cloud config.   For Sync Direction choose G2H, meaning sync from Customer Data Cloud to Commerce.   Enter a name for Hybris Attribute Name.   Enter profile.email for Customer Data Cloud Attribute Name.   Choose string for Hybris Type,  then Finish.   Now that we’ve configured everything  in the Backoffice,  we can go to the storefront to verify the integration features.  This concludes part 1 of our demo for the SAP Commerce Cloud  and Composable Storefront Integration  with SAP Customer Data Cloud.  Thank you for watching.