Ready to get started?

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

Download Now

Create an FedEx Data Source for Denodo Platform

Use the CData JDBC Driver for FedEx to create a virtual data source for FedEx data in the Denodo Virtual DataPort Administrator.

Denodo Platform is a data virtualization product providing a single point of contact for enterprise database data. When paired with the CData JDBC Driver for FedEx, Denodo users can work with live FedEx data alongside other enterprise data sources. This article walks through creating a virtual data source for FedEx in the Denodo Virtual DataPort Administrator.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live FedEx data. When you issue complex SQL queries to FedEx, the driver pushes supported SQL operations, like filters and aggregations, directly to FedEx and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze FedEx data using native data types.

Create an FedEx Virtual Port

To connect to live FedEx data from Denodo, you need to copy the JDBC Driver JAR file to the external library directory for Denodo and create a new JDBC Data Source from the Virtual DataPort Administrator tool.

  1. Download the CData JDBC Driver for FedEx installer, unzip the package, and run the JAR file to install the driver.
  2. Copy the JAR File (and license file if it exists) from the installation location (typically C:\Program Files\CData\CData JDBC Driver for FedEx\lib\) to the Denodo external library directory (C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-fedex-19).
  3. Open the Denodo Virtual DataPort Administrator tool and navigate to the Server Explorer tab.
  4. Right-click "admin" and select New -> Data source -> JDBC.
  5. Configure the JDBC Connection:
    • Name: your choice, e.g.: fedex
    • Database adapter: Generic
    • Driver class path: C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-fedex-19
    • Driver class: cdata.jdbc.fedex.FedExDriver
    • Database URI: Set this to a JDBC URL using the necessary connection properties. For example,

      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';

      Information on creating the Database URI follows:

      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.

      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
  6. Click the "Test connection" button to confirm the configuration and click Save.

View FedEx Data in the VirtualPort Administrator Tool

After creating the data source, you can create a base view of FedEx data for use in the Denodo Platform.

  1. Click the "Create base view" button in the newly created VirtualPort (admin.FedEx).
  2. Expand the object tree and select the objects (tables) you wish to import.
  3. Click the "Create selected" button to create views of the FedEx data.
    Optional: Click "Create associations from foreign keys" to define relationships between the objects.
  4. With the view(s) created, navigate to a table (cdata_fedex_senders) in the Server Explorer and double-click the selected table.
  5. In the new tab, click "Execution panel" to open a query panel.
  6. Customize the query in the "Execute" tab or use the default:
    SELECT * FROM cdata_fedex_senders CONTEXT ('i18n'='us_est', 'cache_wait_for_load'='true')
    
  7. Click Execute to view the data.

With the base view created, you can now work with live FedEx data like you would any other data source in Denodo Platform, for example, querying FedEx in the Denodo Data Catalog.

Download a free, 30-day trial of the CData JDBC Driver for FedEx and start working with your live FedEx data in Denodo Platform. Reach out to our Support Team if you have any questions.