Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Basic Settings
In addition to the standard icons, the properties toolbar includes datasource_show_tablesdatasource_show_tables, which opens a list of tables visible for this datasource using the default login details; see the Table Details window.For a datasource, you must:
- Enter a Name.
- Select a Driver class.
- Add at least one datasource instance.
- Tick the Enabled check box when it is ready to use.
We recommend you tick Protect during import to prevent this datasource being updated or deleted during import.
Enter the name for this datasource. It is helpful to use a name that reflects the type of database to which it will connect. This name appears in the Datasource drop-down list for database collectors and exporters.
title | More ... |
---|
Note |
---|
Exception: If the datasource parent and the datasource have been deleted in the source instance, then the import deletes the datasource from the target instance. This prevents orphaned datasources persisting in PhixFlow. |
Select the driver class for the type of database to which the datasource connects.
Tip |
---|
The drop-down list may contain driver classes that are deprecated and do not have the necessary database drivers; see Driver Classes. |
When a driver class is selected, to open its properties, click the Driver Class heading.
Datasource Instances
This section has a toolbar with standard buttons.
The grid contains a list of datasource instances that belong to this datasource. Double-click on a row to open the datasource instance properties.
To add a datasource to the list, clickDatabase Collectors
This section has a toolbar with standard buttons.
The grid contains a list of database collectors that use this datasource. Double-click on a row to open the database collector properties. You can change whether or not the collector uses this datasource or whether the collector is enabled.
Note |
---|
Any changes you make will affect the analysis models in which the collector is used. |
Analysis Models
This section has a toolbar with analysis models that use analysis model descriptiondescriptionBasic Settings
For a datasource instance, you must:
- Enter a Name.
- Enter the URL for the database.
- Specify the Username and Password.
- Tick the Enabled check box when it is ready to use.
Other settings are optional.
Basic Settings
Name
Enter the name for this instance. In the properties for collectors and exporters, you can specify this instance by using its name in the Datasource Instance Expression.
Enter the URL for the target database.
Example URLs
- Oracle
jdbc:oracle:thin:@hostname:1521:phixflow
- Oracle for versions above 12c, with PDB containers
jdbc:oracle:thin:@hostname:1521/phixflow
- SQL Server
jdbc:sqlserver://
hostname\myservice
;databaseName=phixflow
- MySQL
jdbc:mysql://
hostname
/phixflow
- Big Query
jdbc:bigquery://@hostname:@port;ProjectId=@Project;
Select:
- Local: to provide user credentials from PhixFlow. When you select this option, the Username and Password properties are available.
- External: to provide user credentials from the secure keystore. When you select this option, the Username Key and Password Key properties are available.
Use this option for greater security.
These options are available when Authorisation Type is Local.
This username and password must match an account that is configured to access the datasource instance. PhixFlow connects to the datasource using this username and password.
Enter the key that identifies the username in the keystore.
These options are available when Authorisation Type is External.
The keys must match a username and password stored in the keystore and these are configured to access the datasource instance. PhixFlow connects to the datasource using this username and password.
Advanced
Only use these options if you know about database connections and SQL queries. For help with these options, contact support@phixflow.com.
Check Query
Use this field when connections to the target database might go stale. This can happen if the target database disconnects long-running connections.
Enter a database query that will return a row from the database.
PhixFlow runs the query against the database just before each use of a pooled connection. If the query does not return a row, the connection is discarded and a new connection is created. To avoid any performance impact, the query should execute quickly.
See the Query String section of the Database Collector Properties page for information about writing SQL queries in PhixFlow.
Use this field when the target database has additional requirements not covered by the datasource and datasource instance properties.
Enter the path to an external datasource connection profile.
PhixFlow will use the configuration information in the profile to connect to the target database.