...
...
...
...
...
...
...
...
...
...
...
...
This page is for data modellers who want to connect to an external database, either to load data or to export processed data back to a database.
Overview
The datasource defines a connection to an external database. You need to define at least one of these datasource modelling object in order to push and pull data to and from external database systems.
...
. You can configure several datasource objects if you want to have several connections to the same database.
Datasource behaviour is also determined by these parameters set elsewhere in PhixFlow:
- Privilege 'Allow anonymous updates on datasources'. Only a user with this privilege can modify the 'Anonymous export allowed' flag on a datasource.
- System Configuration. parameter 'Allow anonymous export by default'. This causes the 'Anonymous export allowed' to be true by default on all new datasources.
To configure a datasource you must specify:
- a name
- a driver class. This should match the type of datasource you are connecting to, e.g. Oracle, MySQL, SQLServer etc.); see Driver Classes.
- The protect during import flag can be used to prevent this datasource being updated or deleted during import. T
To prevent orphaned datasources, when a parent application is deleted by the import, its datasources will also be deleted. - Remember to set the enabled flag to make the datasource active.
- Most importantly, ensure you have configured at least one datasource instance.
The toolbar has the standard icons and
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
For information about other property tabs, see Property Tabs.
...
A datasource instance defines connection details to a database. A number of instances can be defined to allow for several connections under a single datasource. At least one datasource Instance must be defined for each datasource.
Basic Settings
| Field | Description | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| NameName of | the datasource instance. Used to identify the datasource instance in collectors and exportersRequired. Enter the name for this datasource object. You will use this name to specify this datasource object in other collector and exporter objects. | ||||||||||||||||||
| Enabled |
| ||||||||||||||||||
| URL | Enter the URL to connect to the datasource. See example connection strings below. | ||||||||||||||||||
| Enabled | Flag whether this datasource is enabled or disabled. | ||||||||||||||||||
| Anonymous Username | Username for connecting to the datasource when the credentials of the PhixFlow user should not or cannot be used, for example in a scheduled task plan.; see Connection URLs below. what | ||||||||||||||||||
| Allow Anonymous Export | For datasources connected to an exporter being run by a task, such as a scheduled task. The target database must permit anonymous updates.
The datasource can only use the logged in user's credentials (see Use user credentials below). | ||||||||||||||||||
| Use User Credentials on Export | For datasources connected to an exporter being run interactively, when a user clicks
| ||||||||||||||||||
| Protect during import |
| ||||||||||||||||||
| Password | Password for connecting to the datasource with the Anonymous Username. I've ticked Allow Anonymous, and Use User, but I'm not seeing any fields where I can specify which user credentials to use. This option has gone. | ||||||||||||||||||
| Driver Class | Select the driver class for the type of database to which the datasource object connects.
|
Advanced
| Field | Description |
|---|---|
| Check Query | See Advanced Configuration. |
| Datasource Profile | See Advanced Configuration. |
| Description | A description of the datasource instance. |
Connection URLs
| Anchor | ||||
|---|---|---|---|---|
|
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:
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
Authentication to the Target Database
| Anchor | ||||
|---|---|---|---|---|
|
...
| bgColor | #e6f0ff |
|---|---|
| titleBGColor | #99c2ff |
| title | External Credentials Settings |
There are two flags on the details tab that determine what credential the datasource sends when connecting to the external source.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This is an advanced (optional) setting. Use this field when connections to the target database might go "stale", e.g. if the target database disconnects long running connections. Setting this field causes PhixFlow to run 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 also database collectors for guidance on writing SQL queries in PhixFlow. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This is an advanced (optional) setting. Use this field when connections to the target database have certain requirements that are not covered by PhixFlow's default external Datasource configuration. The value entered in this field will determine which external datasource connection profile that this datasource instance will use to connect to the target database .Panel | | |||||
|