Three separate responsibilities
A component defines how data is read or written. A Connection combines endpoint metadata, an authentication method and protected credential custody. A worker supplies the adapter, network access and execution capacity. A connector appearing in the catalog does not prove that a particular worker has its driver or the required resource permissions.
Dova offers delimited-file, JSON, Excel, database, API and object-storage sources; available targets are delimited file, JSON, database, API and object storage. Review the actual type in Connections and the fields offered by its form. Do not interchange authentication methods between providers merely because their names look similar.
Prepare a Connection
- Confirm the tenant, role and permission to manage the Connection.
- Select an offered connector and enter only authorized endpoint metadata.
- Choose an authentication and custody method available in that form. Enter the secret through its protected control.
- Save and inspect permitted metadata. Test the saved Connection using the available action.
- Configure and publish a laboratory Mapping. Reference it from a Session with an eligible worker and run a small extraction from that Session.
For example, use a synthetic Connection named CustomerLabReadOnly, database training and table customers. These are exercise names, not instructions to connect to a real system. Verify expected columns and row counts before enabling writes. Keep the laboratory destination separate from business output.
Configure reading and output
In database table mode, selected source columns define projection. In query mode, fields depend on SQL supported by the adapter; do not assume another property rewrites arbitrary queries. Editor support does not imply that every mode works on every runtime. Review runtime compatibility before relying on a query-only feature.
File targets write their incoming schema. To exclude fields, add Field selector before the target. Successful authentication neither fixes an incorrectly configured transformation nor establishes data accuracy. Compare the actual output against a known synthetic result.
Rotate and troubleshoot
A successful connection test does not certify all reads, writes, retry policies or results. If the test passes but execution fails, inspect the worker, network, resource permissions, published version and specific operation. Check dependencies before rotating or revoking a credential.
Dova Vault protects custody; it does not authorize exposing secrets or internal references. Avoid pasting credentials into SQL, descriptions, parameters or conversations. Access to public worker capacity does not grant Connection access or make data and Sessions public. Verify the final result and retain only authorized evidence.