Configure the CData JDBC Driver for FedEx in a Connection Pool in Tomcat

Ready to get started?

Download for a free trial:

Download Now

Learn more:

FedEx JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with FedEx data including Packages, Shipments, Recipients, and more!

Connect to FedEx data from a connection pool in Tomcat.

The CData JDBC Drivers support standard JDBC interfaces to integrate with Web applications running on the JVM. This article details how to connect to FedEx data from a connection pool in Tomcat.

Connect to FedEx Data through a Connection Pool in Tomcat

  1. Copy the CData JAR and CData .lic file to $CATALINA_HOME/lib. The CData JAR is located in the lib subfolder of the installation directory.
  2. Add a definition of the resource to the context. Specify the JDBC URL here.

    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: "", "", "", and ""
    • 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

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

    You can see the JDBC URL specified in the resource definition below.

    <Resource name="jdbc/fedex" auth="Container" type="javax.sql.DataSource" driverClassName="" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:fedex:Server='';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';" maxActive="20" maxIdle="10" maxWait="-1" />

    To allow a single application to access FedEx data, add the code above to the context.xml in the application's META-INF directory.

    For a shared resource configuration, add the code above to the context.xml located in $CATALINA_BASE/conf. A shared resource configuration provides connectivity to FedEx for all applications.

  3. Add a reference to the resource to the web.xml for the application. FedEx data JSP jdbc/FedEx javax.sql.DataSource Container
  4. Initialize connections from the connection pool: Context initContext = new InitialContext(); Context envContext = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/FedEx"); Connection conn = ds.getConnection();

More Tomcat Integration

The steps above show how to connect to FedEx data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.