Access UKG Pro WFM Data as a Remote Oracle Database

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 UKG Pro WFM to create a database link from UKG Pro WFM to Oracle and to query UKG Pro WFM data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to UKG Pro WFM as an ODBC Data Source

Information for connecting to UKG Pro WFM follows, along with different instructions for configuring a DSN in Windows and Linux environments.

Start by setting the Profile connection property to the location of the UKGProWFM Profile on disk (e.g. C:\profiles\UKGProWFM.apip). Next, set the ProfileSettings connection property to the connection string for UKGProWFM (see below).

UKGProWFM API Profile Settings

UKG Pro Workforce Management uses OAuth 2.0 with the Resource Owner Password Credentials grant (grant_type=password) to authorize access to the API. Unlike most OAuth-based profiles, this does not use a browser redirect/authorization-code step: the driver exchanges your UKG Pro WFM username, password, client ID, and client secret directly for an access token.

Set the following connection properties to authenticate:

• AuthScheme: Set this to OAuthPassword.
• Host: Set this to the hostname of your UKG Pro Workforce Management datacenter/tenant (for example, yourcompany.mykronos.com). Do not include the protocol (https://) or a trailing slash.
• OAuthClientId: Set this to the client ID issued for your UKG Pro Workforce Management OAuth application.
• OAuthClientSecret: Set this to the client secret issued for your UKG Pro Workforce Management OAuth application.
• User: Set this to your UKG Pro Workforce Management username.
• Password: Set this to your UKG Pro Workforce Management password.

Access tokens are obtained from https://{Host}/api/authentication/access_token. Refresh tokens issued by UKG Pro Workforce Management expire after 7 days; if a refresh attempt fails because the refresh token itself has expired, the driver must re-authenticate with your User/Password credentials to obtain a new access token.

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 UKG Pro WFM 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 UKG Pro WFM 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 API Source]
Driver = CData ODBC Driver for UKG Pro WFM
Description = My Description
Profile = C:\profiles\UKGProWFM.apip
AuthScheme = OAuthPassword
ProfileSettings = 'Host = yourcompany.mykronos.com
User = your_username
Password = your_password
'
OAuthClientId = your_client_id
OAuthClientSecret = your_client_secret

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 UKG Pro WFM data just as you would an Oracle database. Set the following properties when working with UKG Pro WFM 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-api/lib/cdata.odbc.api.ini in a text editor and set the encoding.

cdata.odbc.api.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 UKG Pro WFM data that enables you to query live UKG Pro WFM data as an Oracle database.

1. Create the file initmyukgprowfmdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:

   initmyukgprowfmdb.ora

   HS_FDS_CONNECT_INFO = "CData API Sys"

2. 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 = myukgprowfmdb)
         (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 = myukgprowfmdb)
         (ORACLE_HOME = your-oracle-home)
         (PROGRAM = hsodbc)
       )
     )
   

3. Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:

   tnsnames.ora

   
   myukgprowfmdb  =
     (DESCRIPTION=
       (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
       (CONNECT_DATA=(SID=myukgprowfmdb))
       (HS=OK)
     ) 
   

4. Restart the listener.

5. Test the configuration with the following command:

   tnsping myukgprowfmdb

6. Open SQL*Plus and create the database link with the command below:

   CREATE DATABASE LINK myukgprowfmdb CONNECT TO "user" IDENTIFIED BY "password" USING 'myukgprowfmdb';

You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):

SELECT * from "Employees"@myukgprowfmdb WHERE PersonId = '12345';