ETL Talkdesk in Oracle Data Integrator

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
This article shows how to transfer Talkdesk data into a data warehouse using Oracle Data Integrator.

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

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

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

      Talkdesk uses the OAuth 2.0 Client Credentials grant. There is no browser-based authorization step and no callback URL.

      Set the following connection properties:

      • AccountName: The name of your Talkdesk account.
      • Region: The region where your Talkdesk instance is deployed. Supported values are US (default), EU, CA, AU, UK, and FedRamp.
      • OAuthClientId: The Client Id assigned when you registered your custom OAuth application.
      • OAuthClientSecret: The Client Secret assigned to your custom OAuth application.

      Creating a Custom OAuth Application

      1. Log in to your Talkdesk account and select OAuth Clients from the navigation menu.
      2. Click Create OAuth Client and give the client a descriptive name.
      3. Set Grant Type to Client Credentials.
      4. Click Add scopes and select the scopes for the data you want to access.
      5. Click Create and copy the Client Id and Client Secret.

      When you connect, the driver automatically requests an access token from Talkdesk, caches it, and refreshes it when it expires. Make sure the scopes selected for the application match the views you plan to query, or the token request can fail.

      Built-in Connection String Designer

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

      
      java -jar cdata.jdbc.talkdesk.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:talkdesk:AccountName=myAccount;Region=US;OAuthClientId=myClientId;OAuthClientSecret=myClientSecret;
      
    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 Talkdesk, enter the Schema selected, otherwise enter Talkdesk.
    • Database (Work Catalog): Enter CData.
    • Owner (Work Schema): If you select a Schema for Talkdesk, enter the Schema selected, otherwise enter Talkdesk.
    Configuring the Physical Schema
  5. In the opened model click Reverse Engineer to retrieve the metadata for Talkdesk tables. Reverse Engineer the Model

Edit and Save Talkdesk Data

After reverse engineering you can now work with Talkdesk data in ODI. To view Talkdesk 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 Talkdesk. You will load Users 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 Users table in Talkdesk:
    
    CREATE TABLE ODI_DEMO.TRG_USERS (NAME 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_USERS 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_USERS table from the Sales Administration model onto the mapping.
  7. Drag the Users table from the Talkdesk 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 USERS_AP in TARGET_GROUP.
  10. In the USERS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. SQL-based access to Talkdesk enables you to use standard database-to-database knowledge modules.

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

Ready to get started?

Download a free trial of the Talkdesk Driver to get started:

 Download Now

Learn more:

Talkdesk Icon Talkdesk JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with Talkdesk data including Accounts, Attributes, BillingAccounts, Callbacks, Campaigns, Cases, Contacts, GuardianUsers, Invoices, Products, Subscriptions, Teams, Users, Wallets, and more!