Ir para o conteúdo

Database drivers on Jitterbit private agents

Introduction

Private agents include the following JDBC drivers for Linux and Windows:

The following ODBC drivers are included for Windows only:

This ODBC driver is included for Linux only:

  • PostgreSQL-jitterbit

To use a database not shown above, you must install a JDBC driver for it.

Install a JDBC driver

To install a JDBC driver on a private agent, follow these steps:

  1. Open the driver configuration file JdbcDrivers.conf in a plain text editor. If possible, use one that understands XML.

    The file is found in the installation directory JITTERBIT_HOME, by default C:\Program Files\Jitterbit Agent\ on Microsoft Windows, /opt/jitterbit/ on Linux.

  2. Add the following inside the <Drivers> element, with values substituted according to the table below:

    <Driver>
  <Name>DRIVER_NAME</Name>
  <Class>DRIVER_CLASS</Class>
  <Subprotocol>DRIVER_SUBPROTOCOL</Subprotocol>
  <!-- Optional
    <BeginQuote>B_Q_C</BeginQuote>
    <EndQuote>E_Q_C</EndQuote>
  -->
</Driver>
    Value Replace with
    DRIVER_NAME A unique name for the driver. This name appears in the IO. Once set, you should not change it.
    DRIVER_CLASS The driver's full class name.
    DRIVER_SUBPROTOCOL Used to build the connection URL jdbc:subprotocol://.
    B_Q_C, E_Q_C (Optional) Custom begin and end quote characters.

    Caution

    If you later change the name of an installed driver, you must edit all endpoints, reselect the new driver name, then redeploy affected projects.

    Example element for Microsoft SQL Server
    <Driver>
  <Name>SQL Server</Name>
  <Class>com.microsoft.sqlserver.jdbc.SQLServerDriver</Class>
  <Subprotocol>sqlserver</Subprotocol>
</Driver>

  3. Download the driver JAR file (usually, from the database vendor's website) and copy it to the driver files directory JITTERBIT_HOME/tomcat/drivers/lib/.

  4. Restart the private agent.

  5. Use the host's JDBC administration application to check connectivity between the driver and the underlying data source.

The driver should now appear as an entry when you configure an Integration Studio database connection, or as a Design Studio database source or target.