Build a PostgreSQL Interface for Adobe Experience Manager Data using the CData JDBC Driver

There are a vast number of PostgreSQL clients available on the Internet. From standard Drivers to BI and Analytics tools, PostgreSQL is a popular interface for data access. Using our JDBC Drivers, you can now create PostgreSQL entry-points that you can connect to from any standard client.

To access Adobe Experience Manager data as a PostgreSQL database, use the CData JDBC Driver for Adobe Experience Manager and a JDBC foreign data wrapper (FDW). In this article, we compile the FDW, install it, and query Adobe Experience Manager data from PostgreSQL Server.

Connect to Adobe Experience Manager Data as a JDBC Data Source

To connect to Adobe Experience Manager as a JDBC data source, you will need the following:

• Driver JAR path: The JAR is located in the lib subfolder of the installation directory.

• Driver class:

  cdata.jdbc.adobeexperiencemanager.AdobeExperienceManagerDriver
  

• JDBC URL: The URL must start with "jdbc:adobeexperiencemanager:" and can include any of the connection properties in name-value pairs separated with semicolons.

  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.

  

  A typical JDBC URL is below:

  jdbc:adobeexperiencemanager:URL=https://author-p12345-e67890.adobeaemcloud.com/crx/server;User=admin;Password=admin;
  

Build the JDBC Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The jdbc2_fdw extension is used as an example (downloadable here).

1. Add a symlink from the shared object for your version of the JRE to /usr/lib/libjvm.so. For example:

   ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so
   

2. Start the build:

   make install USE_PGXS=1
   

Query Adobe Experience Manager Data as a PostgreSQL Database

After you have installed the extension, follow the steps below to start executing queries to Adobe Experience Manager data:

1. Log into your database.
2. Load the extension for the database:

   CREATE EXTENSION jdbc2_fdw;
   

3. Create a server object for Adobe Experience Manager:

   CREATE SERVER AdobeExperienceManager 
   FOREIGN DATA WRAPPER jdbc2_fdw OPTIONS (
   drivername 'cdata.jdbc.adobeexperiencemanager.AdobeExperienceManagerDriver',
   url 'jdbc:adobeexperiencemanager:URL=https://author-p12345-e67890.adobeaemcloud.com/crx/server;User=admin;Password=admin;',
   querytimeout '15',
   jarfile '/home/MyUser/CData/CData\ JDBC\ Driver\ for\ Salesforce MyDriverEdition/lib/cdata.jdbc.adobeexperiencemanager.jar'); 
   

4. Create a user mapping for the username and password of a user known to the MySQL daemon.

   CREATE USER MAPPING for postgres SERVER AdobeExperienceManager OPTIONS (
   username 'admin', 
   password 'test');
   

5. Create a foreign table in your local database:

   postgres=# CREATE FOREIGN TABLE content (
   content_id text,
   content_Id text,
   content_Name numeric) 
   SERVER AdobeExperienceManager OPTIONS (
   table_name 'content');
   

postgres=# SELECT * FROM content;