...
...
...
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
In PhixFlow analysis models, you can use a Datasource to connect to an external database, and then load data from it.
PhixFlow requires access to the database driver jar files in order to communicate with a database. Use the driver class properties to configure with the details of the database, its driver and the location of the Jar files.
...
...
- DB2
- Debug JDBC
- Google Big Query
- Hadoop Hive
- MariaDB
- Microsoft (MS) SQL Server
- MySQL
- Netezza
- Oracle
- Sun ODBC Bridge
- Teradata
| Tip |
|---|
Your PhixFlow instance is installed on a database, either MariaDB, SQL Server or Oracle. PhixFlow uses the driver class to communicate with its own database. |
...
...
...
...
...
...
...
- An administrator with permission to add system files must download the required jdbc drivers and save them to the system.
To avoid your drivers being overwritten during Tomcat or PhixFlow upgrades, we recommend that you save them in a different part of the system. - The PhixFlow administrator configures a driver class for the driver, specifying the database driver name and its path.
Adding or Changing a Driver Class
...
...
...
...
...
...
...
...
...
Driver Classes and Driver Class File Properties
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Enter the full path to the jar file.
Windows example path
...
...
...
Some databases require multiple jar files. Add a Driver Class File Location for each of the jar files.
...
For application building, once you have a custom driver, you need the same driver on all instances - so you need to export/import or you will lose the refences.
...
...