Build a PostgreSQL Interface for DocuSign 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 DocuSign data as a PostgreSQL database, use the CData JDBC Driver for DocuSign and a JDBC foreign data wrapper (FDW). In this article, we compile the FDW, install it, and query DocuSign data from PostgreSQL Server.

Connect to DocuSign Data as a JDBC Data Source

To connect to DocuSign 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.docusign.DocuSignDriver
  

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

  To connect to DocuSign, set the following connection properties:

  • UseSandbox: indicates whether current user account is sandbox or not (FALSE by default)
  • AccountId (optional): set it in the connection string if you have access to multiple Account Ids

  Authenticating to DocuSign

  DocuSign uses the OAuth authentication standard. To authenticate using OAuth, create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the Help documentation more information.

  Built-in Connection String Designer

  For assistance in constructing the JDBC URL, use the connection string designer built into the DocuSign JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

  java -jar cdata.jdbc.docusign.jar
  

  Fill in the connection properties and copy the connection string to the clipboard.

  👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
  

  A typical JDBC URL is below:

  jdbc:docusign:OAuthClientId=MyClientId; OAuthClientSecret=MyClientSecret; 
  CallbackURL=http://localhost:33333;
  
  

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 DocuSign Data as a PostgreSQL Database

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

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

   CREATE EXTENSION jdbc2_fdw;
   

3. Create a server object for DocuSign:

   CREATE SERVER DocuSign 
   FOREIGN DATA WRAPPER jdbc2_fdw OPTIONS (
   drivername 'cdata.jdbc.docusign.DocuSignDriver',
   url 'jdbc:docusign:OAuthClientId=MyClientId; OAuthClientSecret=MyClientSecret; 
   CallbackURL=http://localhost:33333;
   ',
   querytimeout '15',
   jarfile '/home/MyUser/CData/CData\ JDBC\ Driver\ for\ Salesforce MyDriverEdition/lib/cdata.jdbc.docusign.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 DocuSign OPTIONS (
   username 'admin', 
   password 'test');
   

5. Create a foreign table in your local database:

   postgres=# CREATE FOREIGN TABLE documents (
   documents_id text,
   documents_DocumentId text,
   documents_DocumentName numeric) 
   SERVER DocuSign OPTIONS (
   table_name 'documents');
   

You can now execute SELECT commands to DocuSign:

postgres=# SELECT * FROM documents;