![]() |
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 Driver for Square, Kafka can work with live Square data. This article describes how to connect, access and stream Square data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the Square 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 Square data. When you issue complex SQL queries to Square, the driver pushes supported SQL operations, like filters and aggregations, directly to Square 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 Square data using native data types.
Before connecting the CData JDBC Driver for streaming Square data in Apache Kafka Topics, install and configure the following in the client Linux-based system.
mkdir Square
mv SquareJDBCDriver.zip Square/
unzip SquareJDBCDriver.zip
ls cd lib/
cp -r /path/to/CData JDBC Driver for Square/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.square.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 Square 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_square_01",
"config": {
"connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector",
"connection.url": "jdbc:square:OAuthClientId=MyAppId;OAuthClientSecret=MyAppSecret;CallbackURL=http://localhost:33333;LocationId=MyDefaultLocation;InitiateOAuth=GETANDREFRESH;",
"topic.prefix": "square-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 Driver for Square. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.square.jar
Fill in the connection properties and copy the connection string to the clipboard.
Square uses the OAuth authentication standard. To authenticate using OAuth, register an app with Square to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
Additionally, you must specify the LocationId. You can retrieve the Ids for your Locations by querying the Locations table. Alternatively, you can set the LocationId in the search criteria of your query.
๐ Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)This request adds all the tables/contents from Square 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 Driver for Square and start streaming Square data into Apache Kafka. Reach out to our Support Team if you have any questions.
Download a free trial of the Square Driver to get started:
Download NowLearn more:
๐ Square IconEasy-to-use Square client enables Java-based applications to easily consume Square Transactions, Items, Subscriptions, etc.