ETL Cvent in Oracle Data Integrator

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

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

This article walks through a JDBC-based ETL -- Cvent to Oracle. After reverse engineering a data model of Cvent 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.cvent.jar) and .lic file (cdata.jdbc.cvent.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 Cvent data. After reverse engineering, you can query real-time Cvent data and create mappings based on Cvent 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 Cvent.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter Cvent.
   • Context: Select Global.
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter Cvent.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.cvent.CventDriver
   • URL: Enter the JDBC URL containing the connection string.

     Before you can authenticate to Cvent, you must create a workspace and an OAuth application.

     Creating a Workspace

     To create a workspace:

     1. Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) >> Admin.
     2. In the Admin menu, navigate to Integrations >> REST API.
     3. A new tab launches for Developer Management. Click on Manage API Access in the new tab.
     4. Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
        • Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
        • Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the driver, you need to set the following scopes:

          event/attendees:read	event/attendees:write	event/contacts:read
          event/contacts:write	event/custom-fields:read	event/custom-fields:write
          event/events:read	event/events:write	event/sessions:delete
          event/sessions:read	event/sessions:write	event/speakers:delete
          event/speakers:read	event/speakers:write	budget/budget-items:read
          budget/budget-items:write	exhibitor/exhibitors:read	exhibitor/exhibitors:write
          survey/surveys:read	survey/surveys:write

     Creating an OAuth Application

     After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.

     Connecting to Cvent

     After creating an OAuth application, set the following connection properties to connect to Cvent:

     • InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
     • OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
     • OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.cvent.jar

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

     Below is a typical connection string:

     jdbc:cvent:OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;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 Cvent, enter the Schema selected, otherwise enter Cvent.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Cvent, enter the Schema selected, otherwise enter Cvent.
5. In the opened model click Reverse Engineer to retrieve the metadata for Cvent tables.

Edit and Save Cvent Data

After reverse engineering you can now work with Cvent data in ODI. To edit and save Cvent 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 Cvent. You will load Events 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 Events table in Cvent: CREATE TABLE ODI_DEMO.TRG_EVENTS (TITLE 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_EVENTS 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_EVENTS table from the Sales Administration model onto the mapping.
7. Drag the Events table from the Cvent 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 EVENTS_AP in TARGET_GROUP.
10. In the EVENTS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

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