Creating a JDBC Data Source

You can create a JDBC data source to connect from your Java application. Creating a JDBC data source based on the CData JDBC Driver for Adobe Experience Manager consists of three basic steps:

1. Add the driver JAR file to the classpath. The JAR file is located in the lib subfolder of the installation directory. Note that the .lic file must be located in the same folder as the JAR file.
2. Provide the driver class. For example:
   

   cdata.jdbc.adobeexperiencemanager.AdobeExperienceManagerDriver

3. Provide the JDBC URL. For example:
   

   jdbc:adobeexperiencemanager:URL=http://localhost:4502/crx/server;User=admin;Password=admin;
   
   or
   
   jdbc:cdata:adobeexperiencemanager:URL=http://localhost:4502/crx/server;User=admin;Password=admin;

   You can use the second format above whenever there is a conflict in your application between drivers using the same URL format to ensure you are using the CData driver. The URL must start with either "jdbc:adobeexperiencemanager:" or "jdbc:cdata:adobeexperiencemanager:" and can include any of the connection properties in name-value pairs separated with semicolons.

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.