ETL ConstantContact in Oracle Data Integrator

Leverage existing skills by using the JDBC standard to connect to ConstantContact: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for ConstantContact connects real-time ConstantContact data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with ConstantContact just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the ConstantContact APIs in real time instead of working with flat files.

This article covers a JDBC-based ETL -- ConstantContact to Oracle. After reverse engineering a data model of ConstantContact entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR (cdata.jdbc.api.jar) and .lic file (cdata.jdbc.api.lic), located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: ~/.odi/oracledi/userlib and $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\odi\oracledi\userlib and %APPDATA%\odi\agent\lib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of ConstantContact data. After reverse engineering, you can query real-time ConstantContact data and create mappings based on ConstantContact tables.

1. In ODI, connect to your repository and click New -> Model and Topology Objects. 👁 Create a New Model
   
2. On the Model screen of the resulting dialog, enter the following information:
   • Name: Enter API.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter API.
   • Context: Select Global.
   👁 Configuring the Model
   
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter API.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.api.APIDriver
   • URL: Enter the JDBC URL containing the connection string.

     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, 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.

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

     Below is a typical connection string:

     jdbc:api:Profile=C:\profiles\ConstantContact.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;
     

   👁 Configuring the Data Server
   
4. On the Physical Schema screen, enter the following information:
   • Name: Select from the Drop Down menu.
   • Database (Catalog): Enter CData.
   • Owner (Schema): If you select a Schema for ConstantContact, enter the Schema selected, otherwise enter API.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for ConstantContact, enter the Schema selected, otherwise enter API.
   👁 Configuring the Physical Schema
   
5. In the opened model click Reverse Engineer to retrieve the metadata for ConstantContact tables. 👁 Reverse Engineer the Model
   

Edit and Save ConstantContact Data

After reverse engineering you can now work with ConstantContact data in ODI. To view ConstantContact data, expand the Models accordion in the Designer navigator, right-click a table, and click View data. 👁 Viewing the data.

Create an ETL Project

Follow the steps below to create an ETL from ConstantContact. You will load Contacts entities into the sample data warehouse included in the ODI Getting Started VM.

1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

   Alternatively you can use SQLPlus. From a command prompt enter the following:

   sqlplus / as sysdba
   

2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Contacts table in ConstantContact:

   CREATE TABLE ODI_DEMO.TRG_CONTACTS (EMAILADDRESS NUMBER(20,0),Id VARCHAR2(255));
   

3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
4. Click Reverse Engineer. The TRG_CONTACTS table is added to the model.
5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
6. Drag the TRG_CONTACTS table from the Sales Administration model onto the mapping.
7. Drag the Contacts table from the ConstantContact model onto the mapping.
8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
9. Open the Physical tab of the Mapping Editor and click CONTACTS_AP in TARGET_GROUP.
10. In the CONTACTS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. 👁 SQL-based access to ConstantContact enables you to use standard database-to-database knowledge modules.
    

You can then run the mapping to load ConstantContact data into Oracle.