...
...
...
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
If you want to connect to any other database,
go get the database drivers
save them into the PhixFlow directory System Configuration / Driver Class File Directory
set up your own driver class/ driver class file(s) to point to the driver classes
There are a set of driver classes in the repository.
They are deprecated. Don’t use them.
They are not linked to any database driver jar files.
To configure communication with a database, you need:
- the appropriate database driver jar files saved to a location outside the tomcat directory.
- A Driver Class and Driver Class File set up in PhixFlow. Together these specify the location of the driver jar files
- we recommend that they stop using these driver entries and instead that they set up user-defined drivers
- in the short term they may install the driver files into $tomcat/lib, but they should be aware that we will remove the ability to do this in a future release
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.
...
- MariaDB
- Microsoft (MS) SQL Server
- Oracle
PhixFlow uses the appropriate driver class to communicate with its own database.
. You can use these driver classes in a datasource. However, you cannot update or change the pre-configured driver classes, which are:
mariadb is functionally equivalent to mysql, and that in general you can use the mariadb driver to connect to a mysql database.
Deprecated Driver Classes
Present for backwards compatibility. We recommend you do not use the following preconfigured driver classes
- DB2
- Debug JDBC
- Google Big Query
- Hadoop Hive
- MySQL
- Netezza
- Sun ODBC Bridge
- Teradata
...
...
...
...
...
...
...
...
...
...
Driver Classes and Driver Class File Properties
We should point out that The Driver Class (File) GUI lets the user define the driver class, but not to upload the jar files using the GUI – you have to create the containing directories and install the jar files directly on the server.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Some databases require multiple jar files. Add a Driver Class File Location for each of the jar files.
...
...
...
...
...
...
...
...
...