Hello,
Each of those data sources you have mentioned, JDBC, ODBC, Multidimensional DB, Web Service, etc., can be used to connect to local or remote resources. The difference is in the connection string that you provide when configuring the data source. When connecting to a data source, the recommended method is via JDBC, when possible. It’s the most efficient method. You can see a list of JDBC drivers that are distributed with Denodo:
https://community.denodo.com/docs/html/browse/7.0/vdp/administration/appendix/supported_jdbc_data_sources/supported_jdbc_data_sources#supported-jdbc-data-sources
For detail on creating JDBC sources, see here:
https://community.denodo.com/docs/html/browse/7.0/vdp/administration/creating_data_sources_and_base_views/jdbc_sources/jdbc_sources
If the driver of the selected adapter is not distributed with Denodo, download it from the vendor’s site, and copy it to the folder <DENODO_HOME>/lib-external/jdbc-drivers/database name - version. In the case of MySQL 5, copy the driver to <DENODO_HOME>/lib-external/jdbc-drivers/mysql-5/
For example, if you have a JDBC connection to a MySQL database that is running locally, the URI might look like this:
jdbc:mysql://localhost:3306/crm
However, you could easily point that data source to a remote resource by using a specific IP (in this case a generic example - 192.168.10.XXX) of the remote machine:
jdbc:mysql://192.168.10.XXX:3306/crm
Hope this helps.
