Jitterbit currently supports 32-bit database drivers.
Use the MySQL 3.51 driver—and not the 5.1 version, as the 5.1 driver is unsuitable for use with Jitterbit.
It is best to use the JDBC driver for MySQL that ships with Jitterbit. When connecting to a MySQL database, the server that Jitterbit services run on needs to have the MySQL ODBC driver installed. If you need to download the driver, it can be found at https://www.mysql.com/downloads.
Connecting to the MySQL for ODBC and JDBC Drivers
Once the driver is installed, the definition of MySQL database sources and targets in the Jitterbit Design Studio is:
- Select the Driver (typically called "MySQL ODBC 3.51 Driver" for ODBC, and "MySQL" for JDBC).
Enter the Server Name (name or IP address of the database server).
Enter the Database Name (Name of the catalog Jitterbit needs to access).
Enter Login and Password (user credentials for Jitterbit to access the database with).
Test the Connection to be sure the configuration is correct.
Once the MySQL driver is installed on the same machine as the Jitterbit server, click the Refresh button to refresh the driver list in the Jitterbit client to see all the new drivers available.
- If the driver does not display in the driver list, go into ODBC manager on the server to see if the driver is visible. Check to see if the driver is listed in the Data Sources (ODBC) Windows applet (under Administrative Tools).
- If you are unable to see the driver, double-check that you are connecting to the correct machine (for example, stop the Jitterbit Apache service on that machine and make sure you can no longer connect using the client).
If you get permission errors such as "
Access denied for user 'root'@'%' to database 'test'", and you are certain that the credentials are correct, it may be a MySQL configuration problem. You can configure MySQL to accept different credentials for different IP addresses or a group of addresses. See the MySQL documentation or contact your MySQL administrator.
The port to open to allow the Jitterbit Server to communicate with a remote MySQL database depends on the port that MySQL has been configured to listen to. Open that port (the default is 3306) on the machine where the MySQL database server is running.
Securing or Encrypting the Connection
Securing the connection between a source/target and a Private Agent depends on the ODBC driver being used. The standard MySQL ODBC driver does not use encryption. The best way to enable such encryption is by tunneling the connection through SSH. This can be done on Private Agents only.
Last updated: May 24, 2019