Ready to get started?

Learn more about the CData JDBC Driver for Epicor ERP or download a free trial:

Download Now

Connect to Epicor ERP Data in DBVisualizer

Integrate Epicor ERP data with visual data analysis tools and data connection wizards in DBVisualizer

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

Create a New JDBC Data Source for Epicor ERP Data

Follow the steps below to use the Driver Manager to provide connectivity to Epicor ERP 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:epicorerp:
    The DBVisualizer Driver Manager.
  4. In the User Specified tab, click the Open File button and select the cdata.jdbc.epicorerp.jar file, located in the lib subfolder of the installation directory.
  5. In the Driver Class menu, select the EpicorERPDriver class, cdata.jdbc.epicorerp.EpicorERPDriver.

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:epicorerp: followed by the connection properties in a semicolon-separated list of name-value pairs.

      To successfully connect to your ERP instance, you must specify the following connection properties:

      • Url:the URL of the server hosting your ERP instance. For example, https://myserver.EpicorSaaS.com
      • ERPInstance: the name of your ERP instance.
      • User: the username of your account.
      • Password: the password of your account.
      • Service: the service you want to retrieve data from. For example, BaqSvc.

      In addition, you may also set the optional connection properties:

      • ApiKey: An optional key that may be required for connection to some services depending on your account configuration.
      • ApiVersion: Defaults to v1. May be set to v2 to use the newer Epicor API.
      • Company: Required if you set the ApiVersion to v2.

      Built-in Connection String Designer

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

      java -jar cdata.jdbc.epicorerp.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:epicorerp:ervice=Erp.BO.CustomerSvc;ERPInstance=MyInstance;URL=https://myaccount.epicorsaas.com;User=username;Password=password;InitiateOAuth=GETANDREFRESH
    • Database UserId: The username to use to authenticate to Epicor ERP.
    • Database Password: The password to use to authenticate to Epicor ERP.
  3. On the Connection tab, click Connect.

To browse through tables exposed by the Epicor ERP 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.