The Datasource defines a connection to an external database. You need to define at least one of these in order to push and pull data to and from external database systems.
It has a name and a driver class (which should match the kind of datasource you are connecting to, e.g. Oracle, MySQL, SQLServer etc.). The protect during import flag can be used to prevent this datasource being updated or deleted during import. Remember to set the enabled flag to make the datasource active. Most importantly, ensure you have configured at least one datasource instance.
...
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Advanced Configuration
...
Panel | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
There are two flags on the details tab that determine what credential the datasource sends when connecting to the external source. When the Anonymous Export Allowed flag is ticked, the datasource can be used by an exporter as part of the work done in executing a task e.g. when processing a scheduled task. In this mode, the datasource will use the configured anonymous username and password. If anonymous export is not allowed, the datasource cannot be used by an exporter during the execution of a task. The datasource can only use the logged in user's credentials (see Use user credentials below). When the Use User Credentials on Export flag is ticked, the current logged in user's own PhixFlow username and password will be used to connect to the target database when an exporter is used interactively. Note that this means that the username/password must be set up on the target system by a Database Administrator.
|
...