Ready to get started?

Connect to live data from ConstantContact with the API Driver

Connect to ConstantContact

Feed ConstantContact Data into FineReport



How to set ConstantContact data as a JDBC data source in FineReport.

The CData JDBC Driver for ConstantContact fully implements the JDBC standard and can provide ConstantContact data connectivity to a wide variety of BI, reporting, and ETL tools and custom applications. In this article, we explain how to set ConstantContact data as JDBC data source in FineReport and view ConstantContact data as a table in the Report Designer.

Set Up a JDBC Data Source of ConstantContact Data

Follow the instruction below to set ConstantContact data as a FineReport database connection.

  1. Copy the cdata.jdbc.api.jar file from the lib folder in the CData JDBC Driver for ConstantContact installation directory to the lib folder of the FineReport installation directory. You will need to copy the cdata.jdbc.api.lic file as well.
  2. From the Server tab, select Define Data Connection, click to add a new connection, and click JDBC.

Next we will set up the data connection definition in the window.

  1. Database: Others
  2. JDBC Driver: cdata.jdbc.api.APIDriver
  3. URL: A standard JDBC connection string using semicolon-separated connection properties.

    Start by setting the Profile connection property to the location of the ConstantContact Profile on disk (e.g. C:\profiles\ConstantContact.apip). Next, set the ProfileSettings connection property to the connection string for Profile (see below).

    ConstantContact API Profile Settings

    ConstantContact uses OAuth-based authentication.

    First, you will need to register an OAuth application with ConstantContact. You can do so from the ConstantContact API Guide (https://v3.developer.constantcontact.com/api_guide/index.html), under "MyApplications" > "New Application". Your Oauth application will be assigned a client id (API Key) and you can generate a client secret (Secret).

    After setting the following connection properties, you are ready to connect:

    • AuthScheme: Set this to OAuth.
    • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
    • OAuthClientId: Set this to the client_id that is specified in you app settings.
    • OAuthClientSecret: Set this to the client_secret that is specified in you app settings.
    • CallbackURL: Set this to the Redirect URI you specified in your app settings.

    Built-in Connection String Designer

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

    java -jar cdata.jdbc.api.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 JDBC URL is below:

    jdbc:api:Profile=C:\profiles\ConstantContact.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;
  4. Click Connection pool attributes and set Test before getting connections to No.

Click Test connection to ensure you have configured the connection properly. With the connection to ConstantContact set up, you can use it as FineReport data source.

Select ConstantContact Data in the Report Designer.

  1. Click to add a new template data set and select DB query to open the database query window.
  2. Choose the JDBC connection that you created from the dropdown list.
  3. The ConstantContact entities will appear as tables on the left pane.
  4. Write a SELECT statement for the ConstantContact data tables and columns that you want to load.
  5. Click preview and data is shown as table.

With these simple steps, ConstantContact can be used as a JDBC data source in FineReport.