How to create Certinia federated tables in MySQL

You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for Certinia data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for Certinia: After you have started the service, you can create a server and tables using the FEDERATED Storage Engine in MySQL. You can then work with Certinia data just as you would local MySQL tables.

Connect to Certinia Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

There are several authentication methods available for connecting to Certinia: login credentials, SSO, and OAuth.

Authenticating with a Login and Token

Set the User and Password to your login credentials. Additionally, set the SecurityToken. By default, the SecurityToken is required, but you can make it optional by allowing a range of trusted IP addresses.

To disable the security token:

1. Log in to Certinia and enter "Network Access" in the Quick Find box in the setup section.
2. Add your IP address to the list of trusted IP addresses.

To obtain the security token:

1. Open the personal information page on certinia.com.
2. Click the link to reset your security token. The token will be emailed to you.
3. Specify the security token in the SecurityToken connection property or append it to the Password.

Authenticating with OAuth

If you do not have access to the user name and password or do not want to require them, use the OAuth user consent flow. See the OAuth section in the Help for an authentication guide.

Connecting to Certinia Sandbox Accounts

Set UseSandbox to true (false by default) to use a Certinia sandbox account. Ensure that you specify a sandbox user name in User.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to Certinia data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

👁 Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)

Create a FEDERATED Server and Tables for Certinia Data

After you have configured and started the service, create a FEDERATED server to simplify the process of creating FEDERATED tables:

Create a FEDERATED Server

The following statement will create a FEDERATED server based on the ODBC Driver for Certinia. Note that the username and password of the FEDERATED server must match a user account you defined on the Users tab of the SQL Gateway.

CREATE SERVER fedCertinia
FOREIGN DATA WRAPPER mysql
OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData Certinia Sys');

Create a FEDERATED Table

To create a FEDERATED table using our newly created server, use the CONNECTION keyword and pass the name of the FEDERATED server and the remote table (Account). Refer to the following template for the statement to create a FEDERATED table:

CREATE TABLE fed_account (
 ...,
 billingstate TYPE(LEN),
 name TYPE(LEN),
 ...,
)
ENGINE=FEDERATED
DEFAULT CHARSET=latin1
CONNECTION='fedCertinia/account';

NOTE: The table schema for the FEDERATED table must match the remote table schema exactly. You can always connect directly to the MySQL remoting service using any MySQL client and run a SHOW CREATE TABLE query to get the table schema.

Execute Queries

You can now execute queries to the Certinia FEDERATED tables from any tool that can connect to MySQL, which is particularly useful if you need to JOIN data from a local table with data from Certinia. Refer to the following example:

SELECT 
 fed_account.billingstate, 
 local_table.custom_field 
FROM 
 local_table 
JOIN 
 fed_account 
ON 
 local_table.foreign_billingstate = fed_account.billingstate;