Connection
Connection objects define a JDBC connection to a database system. They are used when XDM requires access to database objects.
Connections are used in DC and TC task templates, installed applications, and in override properties of the corresponding objects. The definition depends on the database system type, the JDBC URL and a credential.
The credential is used to authenticate the user with the database system. This happens during the batch execution of a task or when using the schema browser facility in a connection.
| The name of a connection must be globally unique. It is not possible to have different connection variations with the same name. |
Using connections as source and/or target
When using a connection in a task template or task, it can be used as a source connection or as a target connection. However, a connection is often only used as source connection (e.g. a production database) or only as a target connection. In particular, it might be undesirable to permit write access to certain connections.
In XDM it is possible to solve this situation with permissions. A connection has two additional permissions named Use as source and Use as Target. For every user or role it is possible to set this permission individually. If Use as source is set on a connection for a specific user, the connection can be used by that user as a source connection, but not as a target connection, when creating a task or task template or when executing a task.
| A connection can be used in an installed application, when either Use as source or Use as target is set. |
Variations
Connections have the following different variations, whereby each variation has its own rule types and properties:
Custom parameter
This object has the possibility to use existing custom parameters. These parameters can, for example, be used as variables in scripts.