Ready to get started?

Learn more about the CData JDBC Driver for FedEx or download a free trial:

Download Now

ETL FedEx in Oracle Data Integrator

This article shows how to transfer FedEx data into a data warehouse using Oracle Data Integrator.

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

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

This article walks through a JDBC-based ETL -- FedEx to Oracle. After reverse engineering a data model of FedEx 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 and .lic file, located in the installation folder, into the ODI userlib directory:

On Unix: ~/.odi/oracledi/userlib On Windows: %APPDATA%\Roaming\odi\oracledi\userlib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of FedEx data. After reverse engineering, you can query real-time FedEx data and create mappings based on FedEx 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 FedEx.
    • Technology: Select Generic SQL.
    • Logical Schema: Enter FedEx.
    • Context: Select Global.
  3. On the Data Server screen of the resulting dialog, enter the following information:
    • Name: Enter FedEx.
    • Driver List: Select Oracle JDBC Driver.
    • Driver: Enter cdata.jdbc.fedex.FedExDriver
    • URL: Enter the JDBC URL containing the connection string.

      There are five pieces of information needed in order to authenticate its actions with the FedEx service. This information is below.

      • Server: This controls the URL where the requests should be sent. Common testing options for this are: "https://gatewaybeta.fedex.com:443/xml", "https://wsbeta.fedex.com:443/xml", "https://gatewaybeta.fedex.com:443/web-service", and "https://wsbeta.fedex.com:443/web-service"
      • DeveloperKey: This is the identifier part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
      • Password: This is the secret part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
      • AccountNumber: This valid 9-digit FedEx account number is used for logging into the FedEx server.
      • MeterNumber: This value is used for submitting requests to FedEx. This value will be provided to you by FedEx after registration.
      • PrintLabelLocation: This property is required if one intends to use the GenerateLabels or GenerateReturnLabels stored procedures. This should be set to the folder location where generated labels should be stored.

      The Cache Database

      Many of the useful tasks available from FedEx require a lot of data. To ensure this data is easy to input and recall later, utilizes a cache database to make these requests. You must set the cache connection properties:

      • CacheProvider: The specific database you are using to cache with. For example, org.sqlite.JDBC.
      • CacheConnection: The connection string to be passed to the cache provider. For example, jdbc:sqlite:C:\users\username\documents\fedexcache.db

      Built-in Connection String Designer

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

      java -jar cdata.jdbc.fedex.jar

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

      Below is a typical connection string:

      jdbc:fedex:Server='https://gatewaybeta.fedex.com:443/xml';DeveloperKey='alsdkfjpqoewiru';Password='zxczxqqtyiuowkdlkn';AccountNumber='110371337';MeterNumber='240134349'; PrintLabelLocation='C:\users\username\documents\mylabels';CacheProvider='org.sqlite.JDBC';CacheConnection='jdbc:sqlite:C:\users\username\documents\fedexcache.db';
  4. On the Physical Schema screen, enter the following information:
    • Schema (Schema): Enter FedEx.
    • Schema (Work Schema): Enter FedEx.
  5. In the opened model click Reverse Engineer to retrieve the metadata for FedEx tables.

Edit and Save FedEx Data

After reverse engineering you can now work with FedEx data in ODI. To edit and save FedEx 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 FedEx. You will load Senders 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 Senders table in FedEx: CREATE TABLE ODI_DEMO.TRG_SENDERS (PHONE NUMBER(20,0),FirstName 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_SENDERS 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_SENDERS table from the Sales Administration model onto the mapping.
  7. Drag the Senders table from the FedEx 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 SENDERS_AP in TARGET_GROUP.
  10. In the SENDERS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

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