![]() |
VOOZH | about |
Apache Kafka is an open-source stream processing platform that is primarily used for building real-time data pipelines and event-driven applications. When paired with the CData JDBC-ODBC Bridge Driver, Kafka can work with live JDBC-ODBC Bridge data. This article describes how to connect, access and stream JDBC-ODBC Bridge data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the JDBC-ODBC Bridge data received using Kafka infrastructure in the Confluent Platform.
With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live JDBC-ODBC Bridge data. When you issue complex SQL queries to JDBC-ODBC Bridge, the driver pushes supported SQL operations, like filters and aggregations, directly to JDBC-ODBC Bridge 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 JDBC-ODBC Bridge data using native data types.
Before connecting the CData JDBC Driver for streaming JDBC-ODBC Bridge data in Apache Kafka Topics, install and configure the following in the client Linux-based system.
mkdir JDBCODBC
mv JDBCODBCJDBCDriver.zip JDBCODBC/
unzip JDBCODBCJDBCDriver.zip
ls cd lib/
cp -r /path/to/CData JDBC-ODBC Bridge Driver/lib/* /usr/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/ cd /usr/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/
java -jar cdata.jdbc.jdbcodbc.jar -l
confluent local services start
This starts all the Confluent Services like Zookeeper, Kafka, Schema Registry, Kafka REST, Kafka CONNECT, ksqlDB and Control Center. You are now ready to use the CData JDBC driver for JDBC-ODBC Bridge to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.
๐ Start the Confluent local services curl --location 'server_address:8083/connectors'
--header 'Content-Type: application/json'
--data '{
"name": "jdbc_source_cdata_jdbcodbc_01",
"config": {
"connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector",
"connection.url": "jdbc:jdbcodbc:Driver={ODBC_Driver_Name};Driver_Property1=Driver_Value1;Driver_Property2=Driver_Value2;...",
"topic.prefix": "jdbcodbc-01-",
"mode": "bulk"
}
}'
Let us understand the fields used in the HTTP POST body (shown above):
For assistance in constructing the JDBC URL, use the connection string designer built into the CData JDBC-ODBC Bridge Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.jdbcodbc.jar
Fill in the connection properties and copy the connection string to the clipboard.
To connect to an ODBC data source, specify either the DSN (data source name) or specify an ODBC connection string: Set Driver and the connection properties for your ODBC driver. ๐ Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)This request adds all the tables/contents from JDBC-ODBC Bridge as Kafka Topics.
Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.
ksql list topics;๐ List the Kafka Topics (BigCommerce is shown)
PRINT topic FROM BEGINNING;
To access the Confluent Control Center user interface, ensure to run the "confluent local services" as described in the above section and type http://<server address>:9021/clusters/ on your local browser.
๐ Connect with Confluent Control CenterDownload a free, 30-day trial of the CData JDBC-ODBC Bridge Driver and start streaming JDBC-ODBC Bridge data into Apache Kafka. Reach out to our Support Team if you have any questions.
Download a free trial of the JDBC-ODBC Bridge to get started:
Download NowLearn more:
๐ ODBC Connectivity from Java IconThe JDBC-ODBC Bridge provides JDBC access from any Java App to ODBC data sources on Windows, Linux and Mac. Whether your organization uses Java-based tools for reporting and analytics, or builds custom Java solutions, the CData JDBC-ODBC Bridge provides an easy way to connect with any ODBC data source.