Skip to main content

Connections

In briefA connection stores the configuration and credentials a job needs, encrypted, so no secret is embedded in the workflow. Batch users hold the account a legacy job runs as — for a SQL job, its database login; the other types hold a credential one job type needs. Each connection type comes from a plugin and declares which of its fields are secret.

WhereAgents › Connections, with New Connection on the list. A job attaches a batch user from its Connection field.

When

  • A SQL LSAM database job needs a login.
  • A legacy Windows, UNIX, IBM i or SQL job must run as a specific account, or an MCP job under a usercode.
  • An OpCon MFT transfer needs a compression password, or an Episys job needs its credential.
  • The same job needs a different credential in each environment.

How

  1. Open Agents › Connections and select New Connection.
  2. Pick the Connection Type, give it a Name, fill in its fields, and select Create.
  3. Select Test Connection on the saved connection to check its configuration.
  4. Attach it to the job, for a legacy job from the Connection field.

The full steps are in Manage connections.

Notes
  • Secret fields read back blank. Leave one blank when editing to keep the stored value.
  • Test Connection checks the configuration only; it never contacts the target system.
  • A connection's type cannot be changed after it is created.
Watch out
  • Sending an empty value for a secret field is refused; it never clears the stored secret.
  • A UNIX job must name a batch user, and so must an MS SQL Job, Oracle, MySQL or MCP job. On Windows and the other SQL types a blank Connection runs as the agent's own service account.
  • To change credentials per environment, target the job's connection reference in a transformation rule, never the Connection parameter.
  • The Episys credentials are visible in the job's output.