ETL HubDB in Oracle Data Integrator

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

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

This article walks through a JDBC-based ETL -- HubDB to Oracle. After reverse engineering a data model of HubDB 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.hubdb.jar) and .lic file (cdata.jdbc.hubdb.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 HubDB data. After reverse engineering, you can query real-time HubDB data and create mappings based on HubDB tables.

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

     There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

     Using a Custom OAuth App

     AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

     Follow the steps below to register an application and obtain the OAuth client credentials:

     1. Log into your HubSpot app developer account.
        • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
     2. On the developer account home page, click the Apps tab.
     3. Click Create app.
     4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
     5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
        • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
        • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
     6. Click Create App. HubSpot then generates the application, along with its associated credentials.
     7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

     8. Under Scopes, select any scopes you need for your application's intended functionality.

        A minimum of the following scopes is required to access tables:

        • hubdb
        • oauth
        • crm.objects.owners.read
     9. Click Save changes.
     10. Install the application into a production portal with access to the features that are required by the integration.
         • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
         • Navigate to the copied link in your browser. Select a standard account in which to install the application.
         • Click Connect app. You can close the resulting tab.

     Using a Private App

     To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

     You can generate a private application token by following the steps below:

     1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
     2. In the left sidebar menu, navigate to Integrations > Private Apps.
     3. Click Create private app.
     4. On the Basic Info tab, configure the details of your application (name, logo, and description).
     5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
     6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
     7. After you are done configuring your application, click Create app in the top right.
     8. Review the info about your application's access token, click Continue creating, and then Show token.
     9. Click Copy to copy the private application token.

     To connect, set PrivateAppToken to the private application token you retrieved.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.hubdb.jar

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

     Below is a typical connection string:

     jdbc:hubdb:AuthScheme=OAuth;OAuthClientID=MyOAuthClientID;OAuthClientSecret=MyOAuthClientSecret;CallbackURL=http://localhost:33333;InitiateOAuth=GETANDREFRESH
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 HubDB, enter the Schema selected, otherwise enter HubDB.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for HubDB, enter the Schema selected, otherwise enter HubDB.
5. In the opened model click Reverse Engineer to retrieve the metadata for HubDB tables.

Edit and Save HubDB Data

After reverse engineering you can now work with HubDB data in ODI. To edit and save HubDB data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes.

Create an ETL Project

Follow the steps below to create an ETL from HubDB. You will load NorthwindProducts 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 NorthwindProducts table in HubDB: CREATE TABLE ODI_DEMO.TRG_NORTHWINDPRODUCTS (NAME NUMBER(20,0),PartitionKey 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_NORTHWINDPRODUCTS 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_NORTHWINDPRODUCTS table from the Sales Administration model onto the mapping.
7. Drag the NorthwindProducts table from the HubDB 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 NORTHWINDPRODUCTS_AP in TARGET_GROUP.
10. In the NORTHWINDPRODUCTS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

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