Name: Setting Up the SAP CIAM Connector in the SAP Customer Data Platform
Uploaded: 2024-6-13
Duration: 283 s
Description: Learn how to set up an SAP Customer Data Cloud CIAM connector in this video. Discover the step-by-step process of connecting to an S3 bucket, setting up connectors, and mapping fields.

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><div><div><div><div>Learn how to set up an SAP Customer Data Cloud CIAM connector in this video. Discover the step-by-step process of connecting to an S3 bucket, setting up connectors, and mapping fields.<br><br></div></div></div></div></div></div></div></div></div>

Setting Up the SAP CIAM Connector in the SAP Customer Data Platform

Welcome to this video of the brand new customer data platform console.  So now we've seen how to set up an application that will connect to a cloud storage, in this case an S3 bucket.  What I'll do next is instead of running you through the setup for a given connector, I'll just demo something I've set up  before, so I've set up a connector from,  so an application that uses connector to Gigya, so customer data cloud.  And you'll see that when you create a new application,  you have a few different connectors that are available. Obviously this list is going to grow over time, but in our case, the one we want to look at is the customer data cloud CIAM connector.  So you'll see you have to enter a little bit of information in here.  So I'll just jump into the one I've already previously set up.  So if I go into the edit mode, you'll see that there's a few things that need to be set up here, like, for example, the user CIAM secret, which are the credentials that are going to let you access  the application residing on the Gigya side,  which you must have set up previously.  And in this case, the API key, which is going to be the unique identifier of the site that you'll be targeting when pulling data.  Here, inside the base URL, you need to define the URL where the data center for this particular API key is.  So in my case, it is the EU1, so European data center.  So it's really as simple as that. And once you've got the main application setup  that is going to connect to my Gigya, my Customer Data Cloud site, we can start adding events.  So previously, I've created an event myself.  So we just go inside this event.  You'll see that basically, similarly to what we've done with the Cloud storage, we need to define the processing purpose, what data type we are targeting and the event name.  So in this case, we can say activities data, for instance.  You'll notice that when you access the model page, there is a schema that is already predefined, it's pretty extensive.  What this is, this is the default customer data cloud schema.  So when you create a new site on the customer data cloud site, you have a schema that is predefined, and that's all the fields that are part of this schema.  At this point, your actual schema, so all the fields you've custom added into your schema are not here, so you'll need to add them as part of this data model setup, but all the default fields are already here.  Similarly to what we've done previously in the Cloud Storage example, you have on the left-hand side  your schema, which obviously has quite  a few fields. The beauty of the console is that it lets you filter.  If I filter by name, you'll see only highlighted do I have all the instances of names within the sub-schemas as well.  As I said, similarly to how we've done the mapping on the Cloud Storage application events, you can just basically drag and drop the field. In this case, it's already mapped here.  One interesting and important feature that you need to have in mind is,  you'll need to obviously map your UID, so the unique identifier  from your Customer Data Cloud site into the CIAM ID, and that will do an automatic binding behind the scene.  It's basically as simple as that. Once again, similarly to the way we've done the application for the cloud storage, we have a polling feature as well.  In this case, I've got a polling setup to poll users every minute.  This can obviously be changed to much less frequent intervals if there's no genuine need for polling users that often.  That's how you set up a CIAM Customer Data Cloud connector in this case.