Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to OData Services in CloverDX (formerly CloverETL)
Transfer OData services using the visual workflow in the CloverDX data integration tool.
The CData JDBC Driver for OData enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with OData as sources and destinations. In this article, you will use the JDBC Driver for OData to set up a simple transfer into a flat file. The CData JDBC Driver for OData enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with OData as sources and destinations. In this article, you will use the JDBC Driver for OData to set up a simple transfer into a flat file.
About OData Data Integration
CData simplifies access and integration of live OData services data. Our customers leverage CData connectivity to:
- Access OData versions 2.0, 3.0, and 4.0, working with legacy services and the latest features and capabilities.
- Leverage advanced query options, including $filter, $select, and $expand, enhancing data retrieval from 3rd party tools.
- Use Server-side execution of aggregation and grouping to minimize data transfer and boost performance.
- Authenticate securely using a variety of schemes, including Azure AD, digest, negotiate, NTLM, OAuth, and more means secure authentication with every connection.
- Use SQL stored procedures to manage OData service entities - listing, creating, and removing associations between entities.
Customers use CData's solutions to regularly integrate their OData services with preferred tools, such as Power BI, MicroStrategy, or Tableau, and to replicate data from OData services to their databases or data warehouses.
Getting Started
Connect to OData as a JDBC Data Source
- Create the connection to OData services. In a new CloverDX graph, right-click the Connections node in the Outline pane and click Connections -> Create Connection. The Database Connection wizard is displayed.
- Click the plus icon to load a driver from a JAR. Browse to the lib subfolder of the installation directory and select the cdata.jdbc.odata.jar file.
- Enter the JDBC URL.
The User and Password properties, under the Authentication section, must be set to valid OData user credentials. In addition, you will need to specify a URL to a valid OData server organization root or OData services file.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the OData JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.odata.jar
Fill in the connection properties and copy the connection string to the clipboard.
A typical JDBC URL is below:
jdbc:odata:URL=http://services.odata.org/V4/Northwind/Northwind.svc;UseIdUrl=True;OData Version=4.0;Data Format=ATOM;

Query OData Services with the DBInputTable Component
- Drag a DBInputTable from the Readers selection of the Palette onto the job flow and double-click it to open the configuration editor.
- In the DB connection property, select the OData JDBC data source from the drop-down menu.
- Enter the SQL query. For example:
SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId
Write the Output of the Query to a UniversalDataWriter
- Drag a UniversalDataWriter from the Writers selection onto the jobflow.
- Double-click the UniversalDataWriter to open the configuration editor and add a file URL.
- Right-click the DBInputTable and then click Extract Metadata.
- Connect the output port of the DBInputTable to the UniversalDataWriter.
- In the resulting Select Metadata menu for the UniversalDataWriter, choose the Orders table. (You can also open this menu by right-clicking the input port for the UniversalDataWriter.)
- Click Run to write to the file.
