Skip to main content

How connectors work

In briefA connector is what gives OpCon Continuum a kind of work to do. Each connector is a plugin that contributes one or more job types — eighteen connectors provide 76 today — and runs in one of three ways: built in to the Universal Agent, inside the platform, or on an existing legacy machine through a relay.

WhereConnectors are chosen as job types: in the workflow editor, open a job and use the Job Definition tab › Job Type list. Which ones appear there is set on the Marketplace page, where an administrator enables or disables each plugin, and each of its job types, for the organization. Saved connections — batch users and the other credentials a job takes — are managed by an administrator, and legacy agents are registered on the Agents page.

When

  • You are deciding which job type can do a piece of work, and what it needs before it can run — an agent, a relay, a saved connection.
  • A job type you expected is not in the Job Type list.
  • You need to know whether a job runs on a Universal Agent, inside the platform, or on a legacy machine through a relay.

For every field of a particular job type, go to its own reference page instead — the Job type catalog links each one.

How

  1. Find the work in the connector catalog and note how its connector runs.
  2. If it is a legacy type, make sure a current relay and a registered LSAM agent are in place.
  3. If it needs a saved connection, have an administrator create one.
  4. Add the job, choose the job type, and fill in its parameters. The platform dispatches it only to an agent that matches what its job type needs.
Notes
  • A job type appears in the Job Type list only when it and its plugin are on for your organization. Every shipped plugin, and every job type in it, is on by default. Turning one off does not stop the jobs that already use it.
  • Legacy LSAM types take a batch user connection for the account the job runs as — an MCP usercode on the MCP types — all but SAP R/3 Job and SAP BW Process Chain, which use the logon configured on the agent, z/OS Batch Job and OS 2200 Job, which name the user in a User ID field, and the other five z/OS types, which have no user field; the built-in types take none.
  • Database work — SQL Server, Oracle, MySQL, ODBC and OLE DB — runs through the SQL LSAM job types on an existing SQL LSAM machine.
Watch out
  • A legacy type with no working relay cannot be placed at all, which shows as no compatible agent rather than as a relay error.