This section describes how to edit the DSN configuration and then authenticate and connect to Adobe Experience Manager APIs.

DSN Configuration

You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the installation process creates a both a user DSN and a system DSN, as described in Installing the Connector.

Note: The connector stores connection information in the Windows registry. To ensure that the connector can write to the registry, either run Power BI as an administrator or use a User DSN for your connection instead of a System DSN.

User DSN

Complete the following steps to edit the DSN configuration:

1. Select Start > Search, and enter ODBC Data Sources in the Search box.
2. Choose the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).
3. Select the system data source and click Configure.
4. Edit the information on the Connection tab and click OK.

System DSN

Configure the system DSN the same way as the user DSN, except you will need to switch to the System DSN tab before performing Step 3.

Connecting to Adobe Experience Manager JCR Repository

This connection allows you to access content stored in an Adobe Experience Manager (AEM) JCR repository using WebDAV. The JCR (Java Content Repository) is the underlying storage system used by AEM to manage content nodes, properties, and metadata. You can connect to both local AEM instances and cloud-based AEM environments.

1. Set the URL to the WebDAV-enabled JCR server.
   • Local development: http://localhost:4502/crx/server
   • AEM as a Cloud Service: https://XXXX-pXXXX-eXXXX.adobeaemcloud.com/crx/server
2. Depending on the AuthScheme used:
   • For Basic make sure to provide User and Password.
   • For None no authentication is required and no additional configuration is necessary.

Once the connection is configured, you can query JCR nodes and properties exposed through the WebDAV endpoint using standard SQL queries. Ensure that the configured user has sufficient permissions to access the required content paths in the AEM repository.