Ready to get started?

Learn more about the CData JDBC Driver for Authorize.Net or download a free trial:

Download Now

Connect to Authorize.Net Data in DBVisualizer

Integrate Authorize.Net data with visual data analysis tools and data connection wizards in DBVisualizer

The CData JDBC Driver for Authorize.Net implements JDBC standards to provide connectivity to Authorize.Net data in applications ranging from business intelligence tools to IDEs. This article shows how to establish a connection to Authorize.Net data in DBVisualizer and use the table editor to load Authorize.Net data.

Create a New JDBC Data Source for Authorize.Net Data

Follow the steps below to use the Driver Manager to provide connectivity to Authorize.Net data from DBVisualizer tools.

  1. In DBVisualizer, click Tools -> Driver Manager -> Create a New Driver.
  2. Enter a name for the data source.
  3. Enter the following in the URL Format box: jdbc:authorizenet:
    The DBVisualizer Driver Manager.
  4. In the User Specified tab, click the Open File button and select the cdata.jdbc.authorizenet.jar file, located in the lib subfolder of the installation directory.
  5. In the Driver Class menu, select the AuthorizeNetDriver class, cdata.jdbc.authorizenet.AuthorizeNetDriver.

Define the Connection to the JDBC Data Source

Follow the steps below to save connection properties in the JDBC URL.

  1. In the Database tab, right-click the Database Connection node and click Create a Database Connection.
  2. In the Connection section, set the following options:

    • Database Type: If you selected the wizard option, the database type is automatically detected. If you selected the "No Wizard" option, select the Generic or Auto Detect option in the Database Type menu.
    • Driver: Select the driver you just created.
    • Database URL: Enter the full JDBC URL. The syntax of the JDBC URL is jdbc:authorizenet: followed by the connection properties in a semicolon-separated list of name-value pairs.

      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.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the Authorize.Net JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.authorizenet.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

      A typical connection string is below:

      jdbc:authorizenet:LoginId=MyLoginId;TransactionKey=MyTransactionKey;
    • Database UserId: The username to use to authenticate to Authorize.Net.
    • Database Password: The password to use to authenticate to Authorize.Net.
  3. On the Connection tab, click Connect.

To browse through tables exposed by the Authorize.Net JDBC Driver, right-click a table and click Open in New Tab.

To execute SQL queries, use the SQL Commander tool: Click SQL Commander -> New SQL Commander. Select the Database Connection, Database, and Schema from the available menus.

See the "Supported SQL" chapter in the help documentation for more information on the supported SQL. See the "Data Model" chapter for table-specific information.