Driver

Last modified by Danniar Firdausy on 2024/09/18 19:57

In this microlearning, we will explore how to connect eMagiz with an external database by selecting and referencing the appropriate driver. You'll learn about key considerations, such as finding the correct JDBC driver and properly configuring it in your flow.

Should you have any questions, please get in touch with academy@emagiz.com.

1. Prerequisites

  • Basic knowledge of the eMagiz platform

2. Key concepts

Each type of external database has its unique driver. So the driver for an Oracle database differs from the driver needed for a Postgres or MySQL database. Furthermore, the version of the database could influence which driver you need. Also, it would be best if you searched for JDBC drivers as other drivers do not work with the eMagiz setup. Last but not least, you might need assistance in uploading the driver if the package exceeds 1 MB.

3. Driver

In this microlearning, we will delve a bit deeper into connecting eMagiz with an external database. We will take a look at how to get the driver and reference it from your flow. Before we can reference the driver within the flow, we first need to find a suitable driver. The driver needs to match the following criteria:

  • Suitable for the type of database
  • JDBC driver
  • Suitable for the version of the database you are connecting with

You can google for suitable drivers. However, some of them have already been used in other projects and will therefore be made available via the new store soon. Once you have found a suitable driver, the next step is to import the relevant resource into your project (in a similar manner as you would typically do). From there on, you only have to fill in the correct reference in the driver field. The best practice would be to use a property reference to fill in the proper reference when deploying. The correct reference should look as follows com.microsoft.sqlserver.jdbc.SQLServerDriver. Check out the help text on the component to see other driver references for different types of databases.

4. Key takeaways

  • Each type and version of an external database requires its specific JDBC driver.
  • You might need assistance in uploading the driver if the package exceeds 1 MB.
  • Always reference the driver correctly in your flow, using a property reference when deploying for best practice.

5. Suggested additional readings

If you are interested in this topic and want more information on it, please read the help text provided by eMagiz and see the following links: