Stream SAS Data Sets Data into Apache Kafka Topics

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 SAS Data Sets, Kafka can work with live SAS Data Sets data. This article describes how to connect, access and stream SAS Data Sets data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the SAS Data Sets 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 SAS Data Sets data. When you issue complex SQL queries to SAS Data Sets, the driver pushes supported SQL operations, like filters and aggregations, directly to SAS Data Sets 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 SAS Data Sets data using native data types.

Prerequisites

Before connecting the CData JDBC Driver for streaming SAS Data Sets data in Apache Kafka Topics, install and configure the following in the client Linux-based system.

1. Confluent Platform for Apache Kafka
2. Confluent Hub CLI Installation
3. Self-Managed Kafka JDBC Source Connector for Confluent Platform

Define a New JDBC Connection to SAS Data Sets data

1. Download CData JDBC Driver for SAS Data Sets on a Linux-based system
2. Follow the given instructions to create a new directory extract all the driver contents into it:
   1. Create a new directory named SAS Data Sets mkdir SASDataSets
   2. Move the downloaded driver file (.zip) into this new directory mv SASDataSetsJDBCDriver.zip SASDataSets/
   3. Unzip the CData SASDataSetsJDBCDriver contents into this new directory unzip SASDataSetsJDBCDriver.zip
3. Open the SAS Data Sets directory and navigate to the lib folder ls cd lib/
4. Copy the contents of the lib folder of SAS Data Sets into the lib folder of Kafka Connect JDBC. Check the Kafka Connect JDBC folder contents to confirm that the cdata.jdbc.sasdatasets.jar file is successfully copied into the lib folder cp * ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/ cd ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/
5. Install the CData SAS Data Sets JDBC driver license using the given command, followed by your Name and Email ID java -jar cdata.jdbc.sasdatasets.jar -l
6. Enter the product key or "TRIAL" (In the scenarios of license expiry, please contact our CData Support team)
7. Start the Confluent local services using the command: 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 SAS Data Sets to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.

8. Create the Kafka topics manually using a POST HTTP API Request: curl --location 'server_address:8083/connectors' --header 'Content-Type: application/json' --data '{ "name": "jdbc_source_cdata_sasdatasets_01", "config": { "connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector", "connection.url": "jdbc:sasdatasets:URI=C:/myfolder;", "topic.prefix": "sasdatasets-01-", "mode": "bulk" } }'

   Let us understand the fields used in the HTTP POST body (shown above):

   • connector.class: Specifies the Java class of the Kafka Connect connector to be used.
   • connection.url: The JDBC connection URL to connect with SAS Data Sets data.

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the SAS Data Sets JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.sasdatasets.jar

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

     Set the following connection properties to connect to your SAS DataSet files:

     Connecting to Local Files

     • Set the Connection Type to "Local." Local files support SELECT, INSERT, and DELETE commands.
     • Set the URI to a folder containing SAS files, e.g. C:\PATH\TO\FOLDER\.

     Connecting to Cloud-Hosted SAS DataSet Files

     While the driver is capable of pulling data from SAS DataSet files hosted on a variety of cloud data stores, INSERT, UPDATE, and DELETE are not supported outside of local files in this driver.

     Set the Connection Type to the service hosting your SAS DataSet files. A unique prefix at the beginning of the URI connection property is used to identify the cloud data store and the remainder of the path is a relative path to the desired folder (one table per file) or single file (a single table). For more information, refer to the Getting Started section of the Help documentation.

   • topic.prefix: A prefix that will be added to the Kafka topics created by the connector. It's set to "sasdatasets-01-".
   • mode: Specifies the mode in which the connector operates. In this case, it's set to "bulk", which suggests that the connector is configured to perform bulk data transfer.

   This request adds all the tables/contents from SAS Data Sets as Kafka Topics.

   Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.

9. Run ksqlDB and list the topics. Use the commands: ksql list topics;
10. To view the data inside the topics, type the SQL Statement: PRINT topic FROM BEGINNING;

Connecting with the Confluent Control Center

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.

Get Started Today

Download a free, 30-day trial of the CData JDBC Driver for SAS Data Sets and start streaming SAS Data Sets data into Apache Kafka. Reach out to our Support Team if you have any questions.