This page is for administrators who need to configure PhixFlow with database drivers connect PhixFlow to external databases using Driver Classes.
Overview
In PhixFlow analysis models, you can use a Datasource to connect to an external database, and then load data from it.
PhixFlow requires database drivers access to the database driver jar files in order to communicate with a database to which:
...
. Use the driver class properties to configure with the details of the database, its driver and the location of the Jar files.
PhixFlow is installed with a set of driver jar files and their associated Driver Classes in the repository. You You can use these driver classes in a datasource. However, you cannot update or change the pre-configured driver classes, which are:
- DB2
- Debug JDBC
- Google Big Query
- Hadoop Hive
- MariaDB
- Microsoft (MS) SQL Server Server
- MySQL
- Netezza
- Oracle
- Sun ODBC Bridge
- Teradata
| Info | ||
|---|---|---|
| ||
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. |
PhixFlow is installed on a database, either MariaDB, SQL Server or Oracle.
How to Configure Driver Classes
...
To add a new driver, right-click ICON and select
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
| Field | Description |
|---|---|
Name | Enter a unique name for the driver, which will appear in the PhixFlow repository. |
| Driver Class Name | Enter the driver class name, which you will find in the driver documentation. For example, for MySQL, the driver name is: |
| Description | Optionally enter a description for the driver. |
Driver Class File
This section has a toolbar with standard buttons.
The grid contains a list of jar files and their file path. To add a jar file to the list:
...