Build Outlook-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 API Driver for JDBC enables users to access live Outlook data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Outlook data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from Outlook to Google BigQuery,

Upload the CData API Driver for JDBC to Google Data Fusion

Upload the CData API Driver for JDBC to your Google Data Fusion instance to work with live Outlook 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: cdataapi-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver
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.api) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.api.APIDriver)
   
5. Click "Finish"

Connect to Outlook Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Outlook 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
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-api)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Outlook. For example:
     
     jdbc:api:RTK=5246...;Profile=C:\profiles\Outlook.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;TenantId=your_tenant_id;CallbackUrl=http://localhost:33333;

     Using OAuth Authentication

     Microsoft Graph API uses OAuth 2.0 for authentication. You must register an application in the Microsoft Azure Portal to obtain OAuth credentials (Client ID and Client Secret).

     Obtaining OAuth Credentials

     1. Log in to the Azure Portal.
     2. Navigate to Azure Active Directory > App registrations.
     3. Click New registration to create a new application.
     4. Enter an application name and select the appropriate account types.
     5. Set the Redirect URI to your application's callback URL (e.g., http://localhost:33333 for desktop apps).
     6. Click Register to create the application.
     7. On the application overview page, copy the Application (client) ID - this is your OAuthClientId.
     8. Navigate to Certificates & secrets and create a new client secret.
     9. Copy the client secret value - this is your OAuthClientSecret.
     10. Navigate to API permissions and add the required Microsoft Graph API permissions:
         • Mail.Read - For accessing email messages
         • Contacts.Read - For accessing contacts
         • Calendars.Read - For accessing calendar events
         • Tasks.Read - For accessing To Do tasks
         • offline_access - For obtaining refresh tokens
     11. Click Grant admin consent to grant these permissions.

     Connecting with OAuth

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

     • AuthScheme: Set this to OAuth.
     • InitiateOAuth: Set this to GETANDREFRESH. The CData API Profile for Outlook will automatically walk through the OAuth process in order to obtain the access token.
     • OAuthClientId: Set this to the Application (client) ID from Azure Portal.
     • OAuthClientSecret: Set this to the client secret value from Azure Portal.
     • TenantId: Set this to your Azure AD tenant identifier (GUID or domain name like 'contoso.onmicrosoft.com').
     • CallbackURL: Set this to the Redirect URI you specified in your app registration (e.g., http://localhost:33333 for desktop apps).

     Example connection string

     Profile=C:\profiles\Outlook.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;TenantId=your_tenant_id;CallbackUrl=http://localhost:33333;
     

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Outlook 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.

     
   • Set Import Query to a SQL query that will extract the data you want from Outlook, i.e.:
     SELECT * FROM CalendarGroupCalendars
   
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 api-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 Outlook data into
   

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

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