Each datasource must have at least one datasource instance. You can add several instances if you want to configure different settings. For example you may want to connect to the same database using a different username and password for different scheduled tasks.
In the properties for collectors and exporters, you can optionally specify the datasource instance using the Advanced → Datasource Instance Expression.
Datasource Properties
Insert excerpt _standard_settings _standard_settings nopanel true
In addition to the standard icons, the properties toolbar includes
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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.
Basic Settings
Field | Description |
---|---|
Name | 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. | |||||||||
Enabled |
|
Protect during import |
|
The datasource uses the anonymous username and password configured for the specific instance (see below)
You must have the Allow anonymous updates on datasources privilege to change this option.
Note |
---|
The target database must already have the same username and password with the required permissions. Contact the database administrator to do this. |
to preserve this datasource during import. This prevents the datasource being updated or deleted. Exception: The datasource will be deleted when its parent application is deleted by the import. This prevents orphaned datasources persisting in PhixFlow. | |||
Driver Class | Select the driver class for the type of database to which the datasource connects.
|
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, click
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
To remove a datasource instance from the grid, use the toolbar button
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Database Collectors
This section has a toolbar with the
and Insert excerpt _list_show _list_show nopanel true
buttons; see standard buttons. Insert excerpt _refresh _refresh nopanel true
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. |
Datasource Instance Properties
Anchor | ||||
---|---|---|---|---|
|
Insert excerpt _standard_settings _standard_settings nopanel true
For a datasource instance, you must:
- Enter a Name.
- Enter the URL for the database.
- Specify theUsername and Password.
- Tick the Enabled check box when it is ready to use.
Other settings are optional.
Basic Settings
Field | Description | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
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. | |||||||||
Enabled |
|
When a parent application is deleted by the import, its datasources will also be deleted. This prevents orphaned datasources persisting in PhixFlow.
Required. 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. |
Database Instance
Advanced have these gone away? I don't see an Advanced section?
| ||||||||||
URL | Enter the URL for the target database. Example URLs
| |||||||||
Authorisation Type | Select:
| |||||||||
Username | Enter a username. | 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. | ||||||||
Password | Enter a password. | |||||||||
Username Key | Enter the alias that identifies the username in the keystore. | These options are available when Authorisation Type is External. The aliases 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.
| ||||||||
Password Key | Enter the alias that identifies the password in the keystore. |
Advanced
Only use these options if you know about database connections and SQL queries. For help with these options, contact support@phixflow.com.
Field | Description |
---|---|
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 page for information about writing SQL queries in PhixFlow. | |
Datasource Profile | 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 |
A datasource instance must have a name, a URL, and a username and password used to connect to the external datasource. The URL should be in one of the following formats:
Oracle
jdbc:oracle:thin:@hostname:1521:phixflow
jdbc:oracle:thin:@hostname:1521/phixflow
SQL Server
jdbc:sqlserver://hostname\myservice;databaseName=phixflow
MySQL
jdbc:mysql://hostname/phixflow
. | |
Description | Optionally enter a information about the advanced configuration. |
Remember to click
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|