Under the Knime file/preferences/Knime/Database(Labs) options i have added ExasolDriver which is not included on default. It is working on my Laptop without any issue.
But on server i dont know how to set preferences that’s why it throws an error:
Error: Loading model settings failed: Could not find the [com.exasol.jdbc.EXADriver] database driver.
Of course this is an expected Error. I have try to find out on server side which preferences i have to change. There are pref or prefs files but i dont know what to change or add. So i cant find a solution.
To sum up, go to /workflow_repository/config/. Open preferences.epf.template, and add path to .jar in appropriate line. Then save as preferences.epf in exact same location.
But for the labs i have to add extra lines and of course the path within the those lines. But its not obvious what to add. To get these infos i have exported for Database (Labs) options by clicking file/export preferences.
/instance/org.knime.database/drivers/com.exasol.jdbc.EXADriver/database_type=default
/instance/org.knime.database/drivers/com.exasol.jdbc.EXADriver/driver_class=com.exasol.jdbc.EXADriver
/instance/org.knime.database/drivers/com.exasol.jdbc.EXADriver/paths/0= < path to exasol driver>
/instance/org.knime.database/drivers/com.exasol.jdbc.EXADriver/url_template=/instance/org.knime.database/drivers/exasol/url_template=://:/<database_name>
/instance/org.knime.database/drivers/com.exasol.jdbc.EXADriver/version=6.0.0
After i have added above lines to the server and restarting the server, it has worked without any error.
Great to hear that you solved the issue. One more KNIME Server feature that you might find useful if you have several users of the Analytics Platform who are all using the Exasol DB driver. In that case you can use the “Customizations” feature to send the driver file and configuration to clients. See the documentation here: https://docs.knime.com/latest/server_admin_guide/index.html#management-client-preferences
You’re right - the path in the template only works for the old DB integration. Since we have now moved the new framework to production-ready, we should add those lines to the template as well.