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 →Stream Workday Data into Apache Kafka Topics
Access and stream Workday data in Apache Kafka using the CData JDBC Driver and the Kafka Connect JDBC connector.
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 Workday, Kafka can work with live Workday data. This article describes how to connect, access and stream Workday data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the Workday 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 Workday data. When you issue complex SQL queries to Workday, the driver pushes supported SQL operations, like filters and aggregations, directly to Workday 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 Workday data using native data types.
About Workday Data Integration
CData provides the easiest way to access and integrate live data from Workday. Customers use CData connectivity to:
- Access the tables and datasets you create in Prism Analytics Data Catalog, working with the native Workday data hub without compromising the fidelity of your Workday system.
- Access Workday Reports-as-a-Service to surface data from departmental datasets not available from Prism and datasets larger than Prism allows.
- Access base data objects with WQL, REST, or SOAP, getting more granular, detailed access but with the potential need for Workday admins or IT to help craft queries.
Users frequently integrate Workday with analytics tools such as Tableau, Power BI, and Excel, and leverage our tools to replicate Workday data to databases or data warehouses. Access is secured at the user level, based on the authenticated user's identity and role.
For more information on configuring Workday to work with CData, refer to our Knowledge Base articles: Comprehensive Workday Connectivity through Workday WQL and Reports-as-a-Service & Workday + CData: Connection & Integration Best Practices.
Getting Started
Prerequisites
Before connecting the CData JDBC Driver for streaming Workday data in Apache Kafka Topics, install and configure the following in the client Linux-based system.
- Confluent Platform for Apache Kafka
- Confluent Hub CLI Installation
- Self-Managed Kafka JDBC Source Connector for Confluent Platform
Define a New JDBC Connection to Workday data
- Download CData JDBC Driver for Workday on a Linux-based system
- Follow the given instructions to create a new directory extract all the driver contents into it:
- Create a new directory named Workday
mkdir Workday
- Move the downloaded driver file (.zip) into this new directory
mv WorkdayJDBCDriver.zip Workday/
- Unzip the CData WorkdayJDBCDriver contents into this new directory
unzip WorkdayJDBCDriver.zip
- Create a new directory named Workday
- Open the Workday directory and navigate to the lib folder
ls cd lib/
- Copy the contents of the lib folder of Workday into the lib folder of Kafka Connect JDBC. Check the Kafka Connect JDBC folder contents to confirm that the cdata.jdbc.workday.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/
- Install the CData Workday JDBC driver license using the given command, followed by your Name and Email ID
java -jar cdata.jdbc.workday.jar -l
- Enter the product key or "TRIAL" (In the scenarios of license expiry, please contact our CData Support team)
- 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 Workday to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.
- 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_workday_01", "config": { "connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector", "connection.url": "jdbc:workday:User=myuser;Password=mypassword;Tenant=mycompany_gm1;BaseURL=https://wd3-impl-services1.workday.com;ConnectionType=WQL;; InitiateOAuth=GETANDREFRESH", "topic.prefix": "workday-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 Workday data.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Workday JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.workday.jar
Fill in the connection properties and copy the connection string to the clipboard.
To connect to Workday, users need to find the Tenant and BaseURL and then select their API type.
Obtaining the BaseURL and Tenant
To obtain the BaseURL and Tenant properties, log into Workday and search for "View API Clients." On this screen, you'll find the Workday REST API Endpoint, a URL that includes both the BaseURL and Tenant.
The format of the REST API Endpoint is: https://domain.com/subdirectories/mycompany, where:
- https://domain.com/subdirectories/ is the BaseURL.
- mycompany (the portion of the url after the very last slash) is the Tenant.
Using ConnectionType to Select the API
The value you use for the ConnectionType property determines which Workday API you use. See our Community Article for more information on Workday connectivity options and best practices.
API ConnectionType Value WQL WQL Reports as a Service Reports REST REST SOAP SOAP
Authentication
Your method of authentication depends on which API you are using.
- WQL, Reports as a Service, REST: Use OAuth authentication.
- SOAP: Use Basic or OAuth authentication.
See the Help documentation for more information on configuring OAuth with Workday.
- topic.prefix: A prefix that will be added to the Kafka topics created by the connector. It's set to "workday-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 Workday as Kafka Topics.
Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.
- Run ksqlDB and list the topics. Use the commands:
ksql list topics;
- 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 Workday and start streaming Workday data into Apache Kafka. Reach out to our Support Team if you have any questions.