Build Cvent-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Cvent enables users to access live Cvent data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Cvent data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from Cvent to Google BigQuery,

Upload the CData JDBC Driver for Cvent to Google Data Fusion

Upload the CData JDBC Driver for Cvent to your Google Data Fusion instance to work with live Cvent data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatacvent-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver 👁 Image
   
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.cvent) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.cvent.CventDriver)
   👁 Configuring the driver (Salesforce is shown.)
   
5. Click "Finish"

Connect to Cvent Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Cvent data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver 👁 Adding a database source
   
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-cvent)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Cvent. For example:
     
     jdbc:cvent:RTK=5246...;OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;InitiateOAuth=GETANDREFRESH;

     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.

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     
   • Set Import Query to a SQL query that will extract the data you want from Cvent, i.e.:
     SELECT * FROM Events
   👁 Configuring the database source
   
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like cvent-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert Cvent data into
   👁 Configuring the BigQuery sink
   

With the Source and Sink configured, you are ready to pipe Cvent data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Cvent and import it into Google BigQuery. 👁 Image

While this is a simple pipeline, you can create more complex Cvent pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Cvent and start working with your live Cvent data in Google Data Fusion today.