Datasource Properties
Insert excerpt _standard_settings _standard_settings nopanel true
In addition to the standard icons, the properties toolbar includes
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Basic Settings
| Field | Description | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | Enter the name for this datasource object. You will use this name to specify this datasource in other collector and exporter objects. | ||||||||||||||||||
| Enabled |
| ||||||||||||||||||
| URL INSTANCE | Enter the URL to connect to the datasource; see Connection URLs below. This option has gone. How does the datasource know where the database is? | ||||||||||||||||||
| Allow Anonymous Export | Use this option when a datasource is connected to an exporter that will be run by a task, such as a scheduled task.
The datasource uses the anonymous username and password configured ...where?.The datasource can only use the logged in user's credentials (see Use user credentials below). (This statement from the orginal paragraph makes no sense with the sentence above. for the specific instance (see below) You must have the Allow anonymous updates on datasources privilege to change this option. | ||||||||||||||||||
| Use User Credentials on Export | Use this option when a datasource is connected to an exporter being run interactively. This may be via an application action or when a user clicks
| ||||||||||||||||||
| Protect during import |
When a parent application is deleted by the import, its datasources will also be deleted. This prevents orphaned datasources persisting in PhixFlow. | ||||||||||||||||||
| Driver Class | Required. Select the driver class for the type of database to which the datasource connects.
|
Database Instance
Advanced have these gone away? I don't see an Advanced section?
| Field | Description |
|---|---|
| Check Query | 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. |
| Datasource Profile | 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. |
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:
Platform | Example Connection String |
|---|---|
Oracle | jdbc:oracle:thin:@hostname:1521:phixflow |
| Oracle > 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; |