ÃÛ¶¹ÊÓƵ

1.2.5 Data Landing Zone

In this exercise, the goal is to setup your Data Landing Zone Source connector with Azure Blob storage.

Data Landing Zone is an Azure Blob storage interface provisioned by ÃÛ¶¹ÊÓƵ Experience Platform, granting you to access a secure, cloud-based file storage facility to bring files into Platform. Data Landing Zone supports SAS-based authentication and its data is protected with standard Azure Blob storage security mechanisms at rest and in transit. SAS-based authentication allows you to securely access your Data Landing Zone container through a public internet connection.

Prerequisites

To copy blobs or files to your ÃÛ¶¹ÊÓƵ Experience Platform Data Landing Zone you’ll use AzCopy, a command-line utility. You can download a version for your operating system via , scroll down on that page to Download the AzCopy portable binary and select the approproate version for your OS.

1.2.5.2 Connect Data Landing Zone to ÃÛ¶¹ÊÓƵ Experience Platform

Log in to ÃÛ¶¹ÊÓƵ Experience Platform by going to this URL: .

After logging in, you’ll land on the homepage of ÃÛ¶¹ÊÓƵ Experience Platform.

Before you continue, you need to select a sandbox. The sandbox to select is named --aepSandboxName--. After selecting the appropriate sandbox, you’ll see the screen change and now you’re in your dedicated sandbox.

In the left menu, go to Sources. In the Sources catalog, search for data landing.

Click the Data Landing Zone card, you’ll see the credentials on the right tab.

Click the icon as indicated to copy the SASUri.

Copy your csv-file to your AEP data landing zone

You’ll now ingest data into ÃÛ¶¹ÊÓƵ Experience Platform using Azure command line tools using AZCopy.

Open a terminal at the location of you azcopy install location and execute the following command to copy a file into AEP’s data landing zone:

./azcopy copy <your-local-file> <your SASUri>

Make sure to surround your SASUri with double quotes. Replace <your-local-file> by the path to your local copy of the file global-context-websiteinteractions.csv in the azcopy directory, and replace <your SASUri> by the SASUri value which you copied from the ÃÛ¶¹ÊÓƵ Experience Platform UI. Your command should look like this:

./azcopy copy global-context-websiteinteractions.csv "https://sndbxdtlnd2bimpjpzo14hp6.blob.core.windows.net/dlz-user-container?sv=2020-04-08&si=dlz-xxxxxxx-9843-4973-ae52-xxxxxxxx&sr=c&sp=racwdlm&sig=DN3kdhKzard%2BQwKASKg67Zxxxxxxxxxxxxxxxx"

After executing the above command in your terminal, you’ll see this:

Lookup your file in your Data Landing Zone

Go to your Data Landing Zone in ÃÛ¶¹ÊÓƵ Experience Platform.

Select Sources, search for data landing and click the Setup button.

This will open the Data Landing Zone. You’ll see the file that you just uploaded in the data landing zone’s select data panel.

Process your file

Select your file and select Delimited as data format. You’ll then see a preview of your data. Click Next.

You can now start mapping the uploaded data to match the XDM schema of your dataset.

Select Existing dataset and select the dataset Demo System - Event Dataset for Website (Global v1.1). Click Next.

Now you are ready map the incoming source data from your csv file to the target fields from the dataset’s XDM schema.

Map fields

First of all, click the Clear all mappings button. You can then start with a clean mapping.

Next, click New field type and then select Add new field.

To map the ecid source field, select the field identities.ecid and click Select.

Next, click Map target field.

Select the field --aepTenantId--.identification.core.ecid in the schema structure.

You need to map a couple of other fields, click + New field type followed by Add new field and add fields for this mapping

When finished your screen should look like, the screen below. Click Next.

Click Next.

Click Finish.

Monitor dataflow

To monitor you dataflow, go to Sources, Dataflows and click on your dataflow:

Loading the data can take a couple of minutes, when succesful, you’ll see a status of Success:

Next Step: Summary and benefits

Go Back to Module 1.2

Go Back to All Modules