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

Connect to Miro as an ODBC Data Source

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

Using API Key Authentication

Miro uses API Key authentication with an access token. To generate an access token:

1. Log in to your Miro account
2. Navigate to Settings > Your apps
3. Click "Create new app" or select an existing app
4. Configure the required permissions (e.g., boards:read, teams:read)
5. Install the app and generate an access token
6. Copy the generated access token (it will only be shown once)

After obtaining your access token, set the following connection properties:

• AuthScheme: Set this to APIKey.
• APIKey: Set this to your access token.

Connecting to Miro

Once the authentication is configured, you can connect to Miro and query data from any of the available tables such as Boards, Items, Teams, Organizations, and more.

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 Miro 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 Miro 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 Miro
Description = My Description
Profile = C:\profiles\Miro.apip
AuthScheme = APIKey
ProfileSettings = 'APIKey = your_access_token'

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 Miro data just as you would an Oracle database. Set the following properties when working with Miro 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 Miro data that enables you to query live Miro data as an Oracle database.

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

   initmymirodb.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 = mymirodb)
         (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 = mymirodb)
         (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

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

4. Restart the listener.

5. Test the configuration with the following command:

   tnsping mymirodb

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

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

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

SELECT * from "Boards"@mymirodb WHERE BoardId = '3074457361234567890';