Ready to get started?

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

Download Now

Enable the FedEx JDBC Driver in KNIME

Use standard data access components in KNIME to create charts and reports with FedEx data.

One of the strengths of the CData JDBC Driver for FedEx is its cross-platform support, enabling integration with major BI tools. Follow the procedure below to access FedEx data in KNIME and to create a chart from FedEx data using the report designer.

Define a New JDBC Connection to FedEx Data

  1. Install the Report Designer extension: Click File -> Install KNIME Extensions, and filter on "Report".
  2. In a new workflow, click File -> Preferences and expand the KNIME -> Databases node to add cdata.jdbc.fedex.jar. The driver JAR is located in the lib subfolder of the installation directory.
  3. In the Node Repository view, expand the Database -> Read/Write node and drag a Database Reader onto the workflow editor.
  4. Double-click the Database Reader and set the following properties:

    • Database Driver: In the menu, select the driver name, cdata.jdbc.fedex.FedExDriver
    • Database URL: Enter the connection properties. The JDBC URL begins with jdbc:fedex: and is followed by a semicolon-separated list of connection properties.

      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.

      When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

      A typical JDBC URL is below.

      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';
    • User Name: The username used to authenticate.
    • Password: The password used to authenticate.
    • SQL Statement: Enter an SQL query in the SQL Statement box or double-click a table. This article uses the query below to create a chart: SELECT FirstName, Phone FROM Senders WHERE SenderID = ab26f704-5edf-4a9f-9e4c-25
  5. Test the connection by clicking Fetch Metadata.

  6. Connect the Database Reader to a Data to Report node to supply the dataset to a range of data visualization controls. Click Execute and then click Edit Report at the top of the workflow to open the report designer perspective.
  7. You can now generate reports based on live data. To create a chart, drag the chart control from the palette to the report designer. In the resulting wizard, you can use the filtering and aggregation controls available in KNIME.

Troubleshooting

The following list shows how to resolve common errors:

  • Encountered duplicate row Id "Row1": To resolve this error, add the following to the knime.ini file located in your KNIME installation directory:-Dknime.database.fetchsize=0