Connection
A connection defines how a Task reaches the system it executes against. Every task has exactly one connection.
A connection is also a point of load control: parallelism and load limits set on it apply to all tasks using it, regardless of which Group or Scenario those tasks belong to.
For creating and editing connections, see edit-connection.
Contents
Provider types
| Class | Provider |
|---|---|
| Database | PostgreSQL |
| MySQL | |
| MS SQL | |
| Oracle | |
| JDBC (generic) | |
| Script | OS Command |
| Powershell | |
| SSH | |
| ETL | ODI |
| Cloud | AWS |
| Azure | |
| Google Cloud Platform | |
| REST | HTTP REST job |
The fields shown when editing a connection depend on the provider — host, port, instance, database, schema, login, URL and so on are offered only where they apply. Default ports are pre-filled for the providers that use them.
Details of how each class executes a task are on the sub-pages: database-connection, shell-script-connection, etl-tool-connection, cloud-services-connection.
Common attributes
| Attribute | Description |
|---|---|
| Name | Name of the connection. |
| Description | Free text. |
| Provider | The connection type. |
| Parallel limit | The maximum number of tasks running simultaneously through this connection. |
| Load limit | The maximum combined weight of tasks running through this connection. |
| Alternative connection | A second connection used if the first fails. Available for providers that support failover. |
Where both a group limit and a connection limit apply to a task, the stricter one is enforced. See Resource management.
Cancellation support
Whether a running task can actually be cancelled depends on its provider. Cancellation is supported for:
- PostgreSQL, MySQL, MS SQL, Oracle and generic JDBC
- ODI
- HTTP REST job
- Azure
It is not supported for OS Command, Powershell, SSH, AWS or Google Cloud Platform. For those, requesting a cancel will not stop the work; the task continues until it completes on its own. See Handling failed tasks.
Repair
The Repair action on a scheduled task is offered only for providers that support it. In the current version this is Azure.
Credentials
Authentication fields vary by provider and include login and password, key-based authentication, integrated authentication and managed identity.
Two operational points:
- Export does not include credentials. Passwords and authentication keys are not written to the export file, so a connection created by import must have its credentials set by hand.
- Several fields have a variable counterpart, allowing the value to be supplied from the environment rather than stored in the definition. This is the preferred approach where the same definition is deployed to several environments.
