Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →How to create Authorize.Net federated tables in MySQL
Use the SQL Gateway and the ODBC Driver to set up federated tables for Authorize.Net data in MySQL .
You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for Authorize.Net data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for Authorize.Net: 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 Authorize.Net data just as you would local MySQL tables.
Connect to Authorize.Net 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.
You can obtain the necessary connection properties on the Security Settings -> General Settings page after logging into your Merchant Account.
- UseSandbox: The Authorize.Net API to be used to process transactions. If you are using a production account, this property can be left blank. If you are using a developer test account, set this to 'TRUE'.
- LoginID: The API login Id associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions. Note that this value is not the same as the login Id that you use to log in to the Merchant Interface.
- TransactionKey: The transaction key associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions.
Configure the SQL Gateway
See the SQL Gateway Overview to set up connectivity to Authorize.Net 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.
Create a FEDERATED Server and Tables for Authorize.Net 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 Authorize.Net. 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 fedAuthorizeNet FOREIGN DATA WRAPPER mysql OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData AuthorizeNet 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 (SettledBatchList). Refer to the following template for the statement to create a FEDERATED table:
CREATE TABLE fed_settledbatchlist ( ..., markettype TYPE(LEN), totalcharge TYPE(LEN), ..., ) ENGINE=FEDERATED DEFAULT CHARSET=latin1 CONNECTION='fedAuthorizeNet/settledbatchlist';
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 Authorize.Net 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 Authorize.Net. Refer to the following example:
SELECT fed_settledbatchlist.markettype, local_table.custom_field FROM local_table JOIN fed_settledbatchlist ON local_table.foreign_markettype = fed_settledbatchlist.markettype;