Create an AEM Unstructured Data Lake Object (UDLO) (Beta)

Create an Unstructured Data Lake Object (UDLO) in Data 360 to ingest your organization’s content from AEM into Data 360. The data stream ingests data from your selected repositories into a UDLO and maps it to an Unstructured Data Map Object (UDMO). Data 360 uses the UDMO to create a search index and uses it to ground AI-generated responses. See the Unstructured Data Reference for a list of supported file formats.

The AEM connector is a pilot or beta service that is subject to the Beta Services Terms at Agreements—Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

User Permissions Needed
To connect unstructured data from an external blob store:	Data Cloud Architect

Before you begin:

Set up an AEM connection.
Verify that you have a path to the Root Directory.
Verify that you have a list of tags you want to filter with.

From the App Launcher, select Data Cloud.
Select Data Lake Objects and then click New.
Select the From External Files tile, and click Next.
From the New Data Lake Object page, select the Adobe Experience Manager (AEM) connector tile and click Next.
From the Connection Details dropdown, select the AEM connection you previously created. Data Cloud autopopulates the source based on the connection that you select.
In the Core Content section, for Content Root Path search for the path to the Root Directory.
In the Content Types field, select the items you want to include from AEM. For example:
- Web Pages: Ingests all AEM Web pages from the AEM sites platform.
- Digital Assets: Ingests all AEM managed digital assets (image, audio, video, document).
Apply filters to limit the items you want to ingest. By default, Data 360 ingests all items. Use any or all of these filters:
- Asset File Types: Use this filter to limit the asset type. Enter a comma-separated list of file extensions. For example .jpg, .mp3, .mpg. See Adobe’s documentation for a list of file formats.
- Included Tags: Use this filter to include explicitly tagged contents in a comma-separated list. Data 360 includes any asset tagged with any of the provided tags. This field is case-sensitive. Data 360 ignores any misspelled tags.
- Excluded Tags: Use this filter to exclude explicitly tagged contents in a comma-separated list. Data 360 excludes any asset tagged with any of the provided tags. This field is case-sensitive. Data 360 ignores any misspelled tags.
- Creation Date: Select a date from the calendar widget. Data 360 ingests any asset or page created on or after that date.
- Last Update Date: Select a date from the calendar widget. Data 360 ingests any asset or page updated on or after that date.
Click Next. The connector runs by default every two hours. You can monitor sync status in Data Stream status.
Add an Object Name and an Object API Name for the UDLO. See Data Lake Object Naming Standards. Make sure that the object API name is unique, and the field autopopulates based on the object name.
In the Unstructured Data Model Object Mapping section, select New.
From the Data Space Dropdown, leave the selection as Default.
For the UDMO mapping, enter an Object Name and an Object API Name. See Data Lake Object Naming Standards. Make sure that the object API name is unique. The field autopopulates based on the object name.
Optionally, select the Enable Unstructured Content Harmonization with system defaults checkbox to turn on content harmonization for the UDMO. You can leave content harmonization turned off for now and turn on content harmonization later.
If you are using this feature, go to the Feature Manager and turn on both content harmonization and rendering.

When you turn on content harmonization, you turn on collection of content viewer engagement data.
Select Next.
In the Search Index Configuration section, leave the checkbox selected to Enable Semantic Search with System Defaults. The system default settings automatically select text fields and apply a chunking strategy for each field. Deselect the checkbox to create a search index configuration later.
Leave the remaining fields as-is to use the default settings, or rename and change the Search Configuration details and objects to make changes.
Save your work.

The connector begins to ingest your content. The ingestion process takes several minutes and the length of time depends on the size and number of the AEM assets you’re ingesting.