How to connect to Adobe Experience Manager Data in DBVisualizer
The CData JDBC Driver for Adobe Experience Manager implements JDBC standards to provide connectivity to Adobe Experience Manager data in applications ranging from business intelligence tools to IDEs. This article shows how to establish a connection to Adobe Experience Manager data in DBVisualizer and use the table editor to load Adobe Experience Manager data.
Create a New Driver Definition for Adobe Experience Manager Data
Follow the steps below to use the Driver Manager to provide connectivity to Adobe Experience Manager data from DBVisualizer tools.
- In DBVisualizer, click Tools -> Driver Manager.
- Click the plus sign "" to create a new driver.
- Select "Custom" as the template.
- On the Driver Settings tab:
- Set Name to a user-friendly name (e.g. "CData Adobe Experience Manager Driver")
- Set URL Format to jdbc:adobeexperiencemanager:
- In Driver artifacts and jar files (jars are loaded in order from top):
- Click the plus sign "" -> "Add Files"
- Navigate to the "lib" folder in the installation directory (C:\Program Files\CData JDBC Driver for Adobe Experience Manager XXXX\)
- Select the JAR file (cdata.jdbc.AdobeExperienceManager.jar) and click "Open"
- The Driver Class should populate automatically. If not, select class (cdata.jdbc.adobeexperiencemanager.AdobeExperienceManagerDriver).
Define the Connection to the JDBC Data Source
Close the "Driver Manager" and follow the steps below to save connection properties in the JDBC URL.
- In the "Databases" tab, click the plus sign "" and select the driver you just created.
In the "Connection" section, set the following options:
- Database Type: If you selected the wizard option, the database type is automatically detected. If you selected the "No Wizard" option, select the Generic or Auto Detect option in the Database Type menu.
- Driver Type: Select the driver you just created.
Database URL: Enter the full JDBC URL. The syntax of the JDBC URL is jdbc:adobeexperiencemanager: followed by the connection properties in a semicolon-separated list of name-value pairs.
The driver connects to Adobe Experience Manager (AEM) instances that expose the JCR repository over WebDAV. It supports both on-premises AEM and AEM as a Cloud Service deployments.
To establish a connection, set the following properties:
- URL: The WebDAV-enabled JCR server URL.
- AEM as a Cloud Service: https://author-pXXXXX-eXXXXX.adobeaemcloud.com/crx/server
- Local development: http://localhost:4502/crx/server
- User: Your AEM username.
- Password: Your AEM password.
Note: Tables are dynamically generated based on the JCR repository structure. Ensure that the configured user has sufficient permissions to access the required content paths in the AEM repository.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Adobe Experience Manager JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.adobeexperiencemanager.jar
Fill in the connection properties and copy the connection string to the clipboard.
When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
A typical connection string is below:
jdbc:adobeexperiencemanager:URL=https://author-p12345-e67890.adobeaemcloud.com/crx/server;User=admin;Password=admin;
- URL: The WebDAV-enabled JCR server URL.
- NOTE: Database Userid and Database Password correspond with the User and Password properties for Adobe Experience Manager.
- On the Connection tab, click Connect.
To browse through tables exposed by the Adobe Experience Manager JDBC Driver, right-click a table and click "Open in New Tab."
To execute SQL queries, use the SQL Commander tool: Click SQL Commander -> New SQL Commander. Select the Database Connection, Database, and Schema from the available menus.
See the "Supported SQL" chapter in the help documentation for more information on the supported SQL. See the "Data Model" chapter for table-specific information.