ETL Salesforce Data Cloud in Oracle Data Integrator

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

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

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

     Salesforce Data Cloud supports authentication via the OAuth standard.

     OAuth

     Set to OAuth.

     Desktop Applications

     CData provides an embedded OAuth application that simplifies authentication at the desktop.

     You can also authenticate from the desktop via a custom OAuth application, which you configure and register at the Salesforce Data Cloud console. For further information, see Creating a Custom OAuth App in the Help documentation.

     Before you connect, set these properties:

     • : GETANDREFRESH. You can use to avoid repeating the OAuth exchange and manually setting the .
     • (custom applications only): The Client ID assigned when you registered your custom OAuth application.
     • (custom applications only): The Client Secret assigned when you registered your custom OAuth application.

     When you connect, the driver opens Salesforce Data Cloud's OAuth endpoint in your default browser. Log in and grant permissions to the application.

     The driver then completes the OAuth process as follows:

     • Extracts the access token from the callback URL.
     • Obtains a new access token when the old one expires.
     • Saves OAuth values in so that they persist across connections.

     For other OAuth methods, including Web Applications and Headless Machines, refer to the Help documentation.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.salesforcedatacloud.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:salesforcedatacloud:InitiateOAuth=GETANDREFRESH;
     

   👁 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 Salesforce Data Cloud, enter the Schema selected, otherwise enter SalesforceDataCloud.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Salesforce Data Cloud, enter the Schema selected, otherwise enter SalesforceDataCloud.
   👁 Configuring the Physical Schema
   
5. In the opened model click Reverse Engineer to retrieve the metadata for Salesforce Data Cloud tables. 👁 Reverse Engineer the Model
   

Edit and Save Salesforce Data Cloud Data

After reverse engineering you can now work with Salesforce Data Cloud data in ODI. To view Salesforce Data Cloud 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 Salesforce Data Cloud. You will load Account 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 Account table in Salesforce Data Cloud:

   CREATE TABLE ODI_DEMO.TRG_ACCOUNT ([ACCOUNT NAME] NUMBER(20,0),[Account 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_ACCOUNT 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_ACCOUNT table from the Sales Administration model onto the mapping.
7. Drag the Account table from the Salesforce Data Cloud 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 ACCOUNT_AP in TARGET_GROUP.
10. In the ACCOUNT_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. 👁 SQL-based access to Salesforce Data Cloud enables you to use standard database-to-database knowledge modules.
    

You can then run the mapping to load Salesforce Data Cloud data into Oracle.