Overview
PhixFlow requires database drivers in order to communicate with a database. These are usually JDBC drivers that you download as one or more Jar files
Driver names have the form com.mysql.jdbc.Driver
When you install PhixFlow, a set of driver jar files are installed in the PhixFlow (system somewhere) and the Driver Classes are automatically configured with the install. You cannot update or change these Driver Classes, listed in the repository. In particular, Oracle, Microsoft SQL Server, MariaDB are important not to change because PhixFlow can be installed in these database. So these are maintained by Us.
You can create your own user maintained/custom
They should be flagged as sys or not. Syst maintained ones should show up with details saying you cannot change it.
You need to use different names
We looked in a US gov database that reports on security vulnerabilities. and people can hack the jar file.
You may need to support the same database with different versions may need different versions of drivers.
You may also have a brand new database drivers.
Admins should know
- driver class name
- which single jar (usually) or set of jars are needed - depends on Database person
- The database manufacturers doc will tell them.
- There may be problems with compatibility - check DB doc or download
Class path: our normal class pth is all of the lib and class dir files - these are the set of jar files that tomcat has and on top that everything in lib and on top of that everything in class. Their custom files are a layer on top.
They have to get the jar files onto the tomcat server - no specific location
NOT in tomcat (lib or class)
Additional files stored separately - to avoid them being ovewritten best if stored outside tomcat or phixflow. No system directory.
You can connect PhixFlow to (any) databases to access its data in analysis models. However, you must load and configure the database drivers. To make this easy, PhixFlow has Driver Classes for the following databases:
- DB2
- ??Debug JDBC
- Google Big Query
- Hadoop Hive
- MariaDB
- Microsoft (MS) SQL Server
- MySQL
- Netezza
- Oracle
- Sun ODBC Bridge
- Teradata
These are all system maintained - you cannot edit them or change them or see which drivers they are using. You can use them in data sources. The jar files present in the system part of the PhixFlow install.
You can have more than one driver for each database ??? And if you do how to you make sure you use the right one.
You can also create your own driver class.
?? Can we give any advice for finding the relevant one. The IBM page for DB2 had a load of different downloads with different libraries and I had no idea which would be required.??
Users could not do their own before.
This is more easy to maintain.
# How To
1. For the database you want to connect to download the appropriate driver. JDBC or ODBC
2. Upload to PhixFlow?
3. Set the Driver Class properties
4. Set the Driver Class File
Is there a connection between database collectors/datasource/database exporters.
Datasources and Database Collectors
Basic Settings -> Driver Class
Datasource Instances -> URL -> jdbc:database://localhost/phixflow_instance_name
Driver Classes and Driver Class File Properties
For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties. For a full list of all the PhixFlow property tabs and windows, see Property Tabs.
Basic Settings
| Field | Description |
|---|---|
Name | |
| Driver Class Name | |
| Description |
Driver Class File
This section has a toolbar with standard buttons.
The grid contains a list of jar files and their location. To add a jar file to the list:
- Click
Add to open a the properties for a new Driver Class Location. In the Basic Settings section, set:
Field Description Name
Enter a unique name for the driver. Connector Jar File Location Enter the full path
Windows example
Linux example
Click
OK to save and close the properties for the driver class file.
To remove a jar file from a user group, use the toolbar button 
Permanently Delete.
The full path of the jar file as seen on the server /lib/something/jar - show it being held outside - where you want to put the files.
Look for example for excel exporters and for the where we said they were berfore.
Connector Jar File Location
# security issues
Jar file is compiled code that we cannot control that will run inside the app with no checks on what it can see.
That sets of security bells.
This could connect to a jar file tht could do anyting.
We really only want admins to do this.
We don't want any phixFlow.
An admin on the server is the only one who can install the jar file.
File collectors let users upload to a file collector - system config file upload directory.
We need to have a specific place for driver class files.
Do driver class files need a jira need something to restrict where it will look for the Jar files.
Driver Classes have their own privilege??? - should be restricted to admins and import export.... but may not be at the moment
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.