Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Access Workday Data as a Remote Oracle Database
Use the Oracle ODBC Gateway and Heterogeneous Services technology to access Workday data from your Oracle system.
The Oracle Database Gateway for ODBC and Heterogeneous Services technology enable you to connect to ODBC data sources as remote Oracle databases. This article shows how to use the CData ODBC Driver for Workday to create a database link from Workday to Oracle and to query Workday data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.
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
Connect to Workday as an ODBC Data Source
Information for connecting to Workday follows, along with different instructions for configuring a DSN in Windows and Linux environments.
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.
Windows
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Note: If you need to modify the DSN or create other Workday DSNs, you must use a system DSN and the bitness of the DSN must match your Oracle system. You can access and create 32-bit DSNs on a 64-bit system by opening the 32-bit ODBC Data Source Administrator from C:\Windows\SysWOW64\odbcad32.exe.
Linux
If you are installing the CData ODBC Driver for Workday in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
/etc/odbc.ini
[CData Workday Source]
Driver = CData ODBC Driver for Workday
Description = My Description
User = myuser
Password = mypassword
Tenant = mycompany_gm1
BaseURL = https://wd3-impl-services1.workday.com
ConnectionType = WQL
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Set Connection Properties for Compatibility with Oracle
The driver provides several connection properties that streamline accessing Workday data just as you would an Oracle database. Set the following properties when working with Workday data in SQL*Plus and SQL Developer. For compatibility with Oracle, you will need to set the following connection properties, in addition to authentication and other required connection properties.
MapToWVarchar=False
Set this property to map string data types to SQL_VARCHAR instead of SQL_WVARCHAR. By default, the driver uses SQL_WVARCHAR to accommodate various international character sets. You can use this property to avoid the ORA-28528 Heterogeneous Services data type conversion error when the Unicode type is returned.
MaximumColumnSize=4000
Set this property to restrict the maximum column size to 4000 characters.
IncludeDualTable=True
Set this property to mock the Oracle DUAL table. SQL Developer uses this table to test the connection.
Linux Configuration
In Linux environments, Oracle uses UTF-8 to communicate with the unixODBC Driver manager, whereas the default driver encoding is UTF-16. To resolve this, open the file /opt/cdata/cdata-driver-for-workday/lib/cdata.odbc.workday.ini in a text editor and set the encoding.
cdata.odbc.workday.ini
[Driver]
DriverManagerEncoding = UTF-8
Configure the ODBC Gateway, Oracle Net, and Oracle Database
Follow the procedure below to set up an ODBC gateway to Workday data that enables you to query live Workday data as an Oracle database.
-
Create the file initmyworkdaydb.ora in the folder oracle-home-directory/hs/admin and add the following setting:
initmyworkdaydb.ora
HS_FDS_CONNECT_INFO = "CData Workday Sys"
-
Add an entry to the listener.ora file. This file is located in oracle-home-directory/NETWORK/admin.
If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:
listener.ora
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myworkdaydb) (ORACLE_HOME = your-oracle-home) (PROGRAM = dg4odbc) ) )
If you are using Heterogeneous Services, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:
listener.ora
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myworkdaydb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) )
-
Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:
tnsnames.ora
myworkdaydb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=myworkdaydb)) (HS=OK) )
- Restart the listener.
Test the configuration with the following command:
tnsping myworkdaydb
-
Open SQL*Plus and create the database link with the command below:
CREATE DATABASE LINK myworkdaydb CONNECT TO "user" IDENTIFIED BY "password" USING 'myworkdaydb';
You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):
SELECT * from "Workers"@myworkdaydb WHERE Legal_Name_Last_Name = 'Morgan';