Skip to end of metadata
Go to start of metadata


A Database connection is configured using the Database connector to establish access with a specific database. Once a connection is established, you can configure one or more Database activities associated with that connection to use as a source or target within an operation or script.

Most ODBC- and JDBC-compliant databases are supported. For a complete list of supported databases, see Supported Endpoints and Protocols.

If you need to convert an existing Database connection from using an ODBC driver to using a JDBC driver, see Converting from ODBC to JDBC later on this page.

Creating or Editing a Database Connection

From the design canvas, open the Connectivity tab of the design component palette:

To configure a new Database connection, within the Connectors filter, click the Database connector block:

To configure an existing Database connection, within the Endpoints filter, double-click the Database connection block:

This will open a configuration screen for the Database connection, covered next.

Configuring a Database Connection

Configuration of a Database connection includes these fields:

TIP: Fields with a variable icon support using global variablesproject variables, and Jitterbit variables. Begin typing an open square bracket [ into the field or click the variable icon to display existing variables to choose from.

  • Endpoint Name: Enter a name to use to identify the Database connection. The name must be unique for each Database connection and must not contain forward slashes (/) or colons (:). As a specific connection and its activities are referred to as an endpoint, this name is also used to identify the Database endpoint.
  • Driver Type: If you wish to filter the list of drivers, select the button for the appropriate driver type.
  • Driver: Use the dropdown to select the appropriate driver for the database. Jitterbit Harmony currently supports 32-bit drivers.

    NOTE: Database drivers are automatically detected from the Harmony Agent. For Cloud Agents, Jitterbit provides commonly used drivers. For Private Agents, installed drivers are detected from the operating system where each Private Agent is installed. In addition, you can install other database drivers on Private Agents as needed. For reference information on configuring specific databases, see Database-Specific Information.
  • Server Name: Enter the name, URL, or IP address of the database server.
  • Database Name: If applicable, enter the name of the database. This field may not be present for database drivers for which this field is not applicable, such as Oracle.
  • Login and Password: If applicable, enter a username and password that will allow access to the database. You can leave these fields blank if no username or password is required.

  • Use Default Port: Keep this checkbox selected to use the default port. The default port differs depending on the selected driver. If you don't want to use the default port, clear the Use Default Port checkbox and enter the port to use in the Port field below.

  • Port: Enter a custom port only if the database server is listening on a non-default port. This field will be enabled only if the Use Default Port box is unchecked.
  • Optional Settings: Click to expand for additional optional settings:

    • Transaction Isolation Level: If applicable, use the dropdown to select the Transact-SQL (T-SQL) isolation level. Driver-specific transaction isolation levels are not supported. The DEFAULT option uses the driver or database server default transaction isolation level.
    • Timeout (sec): To set a limit for how long to wait for a successful connection to the database, enter a number of seconds here. The default is 300 seconds (5 minutes).
    • Fetch Size: If using a JDBC driver, this tells the driver how many rows should be fetched when more rows are required. This can be used to improve the processing of large datasets.
    • Additional Connection String Parameters: To add additional parameters to the database connection string, enter them here. Note that this field is disabled if you have selected the option below to use a connection string.
    • Use Connection String: Select this checkbox to enter a connection string in the field below. If selected, this disables and overrides the Additional Connection String Parameters above. If selected and the Connection String field is left blank, the Server Name, Login, and Password as configured above will be used.
    • Connection String: If applicable, enter a connection string into the text box. The checkbox above must be selected in order for this field to be enabled.

      TIP: Consult database-specific documentation for creating manual connection strings. Examples can also be found at

      WARNING: The connection string will be visible in clear text during configuration, so you may not want to include the username and password in the string. Instead of including these parameters and values in the string, use the Login and Password fields provided as part of the UI. They will then be appended to the connection string when needed, but will not be visible on the screen.

  • Test: Click this button to verify the connection to the database. The test must be successful before you are able to save the connection configuration.

  • Save Changes: Click this button to save and close the connection configuration. If this button is not enabled, you must successfully test the connection first.

    NOTE: Unlike other connections, it is required to test a Database connection before any changes can be saved. This is required in order for the list of tables to be retrieved during Database activity configuration.

  • Discard Changes: After making changes to a new or existing configuration, click Discard Changes to close the configuration without saving. A message will ask you to confirm that you want to discard changes.
  • Delete: After opening an existing connection configuration, click Delete to permanently delete the connection from the project and close the configuration (see Component Dependencies, Deletion, and Removal).

Next Steps

After configuring a Database connection, you can configure one or more Database activities associated with that connection to use as a source or target within an operation or script. For more information, see these activities:

  • Query: Queries data from a Database connection and is used as a source in an operation or called in a script.
  • Insert: Inserts new data in a Database connection and is used as a target in an operation or called in a script. 
  • Update: Updates existing data in a Database connection and is used as a target in an operation or called in a script.
  • Upsert: Both updates existing data and inserts new data in a Database connection and is used as a target in an operation or called in a script. (Jitterbit Harmony supports Upsert activities for databases by using a combination of Query, Insert, and Update.)

Converting from ODBC to JDBC

Converting a Database connection from using an ODBC driver to using a JDBC driver is usually a straightforward process. You may need to do so if you move a project from running on a Private Agent using an ODBC driver to a Jitterbit Cloud Agent Group which, as of Jitterbit Harmony 9.8, no longer support ODBC drivers in the Cloud Agent Groups.

If your connection uses the default options, you can quickly convert it following the steps outlined below. However, if you have used the option to specify additional connection string parameters or to construct the connection string manually, you will need to adjust those options to accommodate the differences between ODBC and JDBC.

Jitterbit Support is available to help you in converting your connection to JDBC if you require assistance with converting your Database connections or the revision of advanced options.

Converting Simple Database Connections

To convert a Database connection that currently uses an ODBC driver to one that uses a JDBC driver, follow these steps:

  1. Open the Database connection that uses an ODBC driver. In this example, a connection using the PostgreSQL driver was opened:

  2. Test the connection by clicking the Test button to make sure that it works:

  3. If the connection was successful, you can proceed with this conversion. If not, fix any errors before continuing.
  4. Check if any additional connection parameters were specified by clicking the Optional Settings at the bottom of the configuration screen:

    • If no additional connection parameters were specified beyond the defaults shown above, you can proceed with converting the Database connection following the remainder of these instructions.
    • If there are additional connection parameters specified other than the defaults shown above, see the next section on Converting Connections with Additional Connection Parameters.
  5. Change the Driver Type to JDBC, then use the Driver dropdown to select the appropriate JDBC driver. In this example, we selected the PostgreSQL JDBC driver.

  6. Test the revised connection by clicking the Test button to make sure that it works:

  7. Click the Save Changes button to save the revised Database connection.

Converting Connections with Additional Connection Parameters

If your connection uses additional connection parameters beyond the default values shown above, either as Additional Connection String Parameters or the box Use Connection String was checked and the connection string was entered manually, additional work may be required to convert the connection from ODBC to JDBC. For example, the SQL Server ODBC Additional Connection String Parameters might be (to use NTLM Windows Authentication):


An equivalent SQL Server jTDS JDBC driver Additional Connection String Parameters (to use NTLM Windows Authentication) would be:


Connection string parameters are specific to the database driver you use (e.g. Microsoft SQL, MySQL, PostgreSQL, Oracle). Review the driver specifications to determine the required parameters. If you require assistance with converting connection strings or parameters for a JDBC driver, contact Jitterbit Support.

On This Page

Last updated:  Jun 09, 2020

  • No labels