Access Onfleet 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 Onfleet to create a database link from Onfleet to Oracle and to query Onfleet data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.
Connect to Onfleet as an ODBC Data Source
Information for connecting to Onfleet follows, along with different instructions for configuring a DSN in Windows and Linux environments.
Onfleet uses HTTP ApiKey Authentication. Your Onfleet API Key is used to authenticate requests. You can generate or view your API Key in the Onfleet dashboard under Settings > API.
Using ApiKey Authentication
After setting the following connection properties, you are ready to connect:
- AuthScheme: Set this to APIKey.
- APIKey: Set this to your Onfleet API Key.
Example connection string:
Profile=C:\profiles\Onfleet.apip;AuthScheme=APIKey;ProfileSettings="ApiKey=your_api_key";
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 Onfleet 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 Onfleet 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 Onfleet Description = My Description Profile = C:\profiles\Onfleet.apip AuthScheme = APIKey ProfileSettings = "ApiKey = your_api_key"
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 Onfleet data just as you would an Oracle database. Set the following properties when working with Onfleet 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 Onfleet data that enables you to query live Onfleet data as an Oracle database.
-
Create the file initmyonfleetdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:
initmyonfleetdb.ora
HS_FDS_CONNECT_INFO = "CData API 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 = myonfleetdb) (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 = myonfleetdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) ) -
Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:
tnsnames.ora
myonfleetdb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=myonfleetdb)) (HS=OK) ) - Restart the listener.
Test the configuration with the following command:
tnsping myonfleetdb
-
Open SQL*Plus and create the database link with the command below:
CREATE DATABASE LINK myonfleetdb CONNECT TO "user" IDENTIFIED BY "password" USING 'myonfleetdb';
You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):
SELECT * from "Administrators"@myonfleetdb WHERE = '';