How connectors work
- Synopsis
- Full Details
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
- Find the work in the connector catalog and note how its connector runs.
- If it is a legacy type, make sure a current relay and a registered LSAM agent are in place.
- If it needs a saved connection, have an administrator create one.
- 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.
- 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.
- A legacy type with no working relay cannot be placed at all, which shows as no compatible agent rather than as a relay error.
A connector is what lets OpCon Continuum do a specific kind of work — run a command, wait for a file, move a file between machines, call into a legacy system. Each connector contributes one or more job types. When a Builder adds a job to a workflow, they choose a job type; that choice determines what the job does and what settings it needs.
This is the surface customers care about most: connectors are how OpCon Continuum integrates with the systems a bank or credit union already runs.
- The Three Ways a Connector Runs
- Connections
- Where a Job Type Can Run
- Before a Job Runs
- The Connector Catalog
The Three Ways a Connector Runs
How a connector runs determines what (if anything) has to be set up before a customer can use it.
| How it runs | What it means | Setup needed | Examples |
|---|---|---|---|
| Built-in | Ships with the Universal Agent | None | Run Command, Run Script, Wait for File |
| Platform-internal | Runs inside the platform — no agent involved | None | Null Job, Workflow Container |
| Legacy (relay) | Runs on an existing on-prem machine through the relay | A relay and reachable machines | UNIX/Linux LSAM, Windows LSAM, IBM i LSAM, SQL LSAM, SMAFT File Transfer, OpCon MFT |
Database work runs through the relay. The SQL LSAM connector runs SQL Server, Oracle, MySQL and ODBC or OLE DB work on an existing SQL LSAM machine; no connector runs database work on the Universal Agent.
Connections
Some connectors need a saved connection — the endpoint and credentials for an external system or the account a job runs as. A legacy UNIX job, for example, takes a batch user connection for the account it runs on the machine as. Built-in utility connectors (Run Command, Run Script, Wait for File) need no connection because they act on the agent itself.
Credentials in a connection are delivered to the connector securely at run time and are not exposed in the job definition. (Connection setup and security is an Administrator topic.)
Where a Job Type Can Run
A job type can require a specific operating system or agent type. The platform only dispatches a job to an agent that matches — for example, a MySQL job targets SQL LSAM agents, and a UNIX LSAM command targets UNIX LSAM agents. If no matching agent is available, the job can't be assigned. A legacy job whose machine name points at an agent of another type is refused when it is dispatched rather than sent — see A legacy job aimed at an agent of another type.
Before a Job Runs
When a Builder saves a job, its required parameters must be filled in. Most other values are checked when the job runs: by the relay at dispatch for the legacy types, so a refused job fails before anything reaches the machine, and by the agent for the Universal Agent types — see the Job type catalog. Each connector also runs in isolation on the agent, so one connector's failure doesn't affect others.
The Connector Catalog
Eighteen connectors provide 76 job types today. Each connector declares a category, which the Marketplace administration page shows beside each plugin and lets you filter by.
| Connector | Category | Job type(s) | How it runs | Needs a connection? | Runs on |
|---|---|---|---|---|---|
| Run Command | Script | Run Command | Built-in | No | Universal Agent (Windows/Linux/macOS) |
| Run Script | Script | Run Script (PowerShell, Bash, Python, Shell) | Built-in | No | Universal Agent (Windows/Linux/macOS) |
| Wait for File | Utility | Wait for File | Built-in | No | Universal Agent (Windows/Linux/macOS) — see Wait for File job |
| Null Job | Internal | Null Job | Platform-internal | No | No agent — completes immediately |
| Workflow Container | Internal | Workflow Container | Platform-internal | No | No agent — runs another workflow as a step |
| UNIX/Linux LSAM | Integration | UNIX Command, UNIX - File Arrival, UNIX - Embedded Script, and seven UNIX - Episys types (Run JobFile, Answer Prompts, Compare ACH Totals, three Find types, FTP all Reports in List) | Legacy (relay) | Yes — a UNIX Batch User connection, the account the job runs as; four Episys types also take an Episys credential connection | Legacy UNIX/Linux LSAM agent |
| Windows LSAM | Integration | Windows Command, Windows - WS_FTP Pro, Windows - Command: File Copy / Move / Rename / Delete, Windows - Corelation, Windows - Fiserv DNA, Windows - Fiserv DNA (File Loader), Windows - File Arrival, Windows - Embedded Script, Windows - Web Services | Legacy (relay) | Optional — a Windows Batch User connection; blank runs the job as the agent's service account | Legacy Windows LSAM agent |
| IBM i LSAM | Integration | IBM i Command, IBM i - Operator Replay, IBM i - Restricted Mode, IBM i - FTP, IBM i - File Arrival | Legacy (relay) | Optional — an IBM i Batch User connection; blank uses the job description's default user | Legacy IBM i LSAM agent |
| SQL LSAM | Integration | SQL - MS SQL Script, SQL - MS SQL Job, SQL - MS SQL DTExec, SQL - Oracle, SQL - Other DB, SQL - MySQL | Legacy (relay) | A SQL Batch User connection — optional on MS SQL Script, MS SQL DTExec and Other DB, where blank runs the job as the agent's service account; required on MS SQL Job, Oracle and MySQL; not taken by an MS SQL DTExec job running a package from the file system, or by an Other DB job using an OLE DB connection string without Windows Authentication | Legacy SQL LSAM agent |
| SAP R/3 and CRM LSAM | Integration | SAP R/3 Job | Legacy (relay) | No — the agent signs on to SAP with the SAP user configured on it | Legacy SAP R/3 and CRM agent — see SAP R/3 Job |
| SAP BW LSAM | Integration | SAP BW Process Chain | Legacy (relay) | No — the agent signs on to SAP with the logon configured on it | Legacy SAP BW agent — see SAP BW Process Chain |
| z/OS LSAM | Integration | z/OS Batch Job, z/OS Started Task, z/OS REXX Exec, z/OS Console Command, z/OS Tracked Job, z/OS Queued Job | Legacy (relay) | No — a z/OS Batch Job's User ID field names the z/OS user the job is submitted as; the other five have no user field | Legacy z/OS agent — see z/OS |
| MCP LSAM | Integration | MCP Run, MCP Start, MCP EAE/AB Suite, MCP Copy, MCP Change, MCP Remove | Legacy (relay) | Yes — an MCP Batch User connection, the usercode the job runs under; an MCP Start job may take a second one for its job summary | Legacy Unisys MCP agent — see MCP |
| OS 2200 LSAM | Integration | OS 2200 Job | Legacy (relay) | No — a User ID field names the user the runstream starts as | Legacy Unisys OS 2200 agent — see OS 2200 Job |
| SMAFT File Transfer | File Transfer | SMAFT File Transfer | Legacy (relay) | Up to two Batch User connections, one per end, matching each machine's platform (none for a z/OS end) | Legacy Windows, UNIX or z/OS LSAM agent — see SMAFT File Transfer job |
| OpCon MFT | File Transfer | OpCon MFT Transfer | Legacy (relay) | Optional — an OpCon MFT Compression Password connection, used only when the transfer compresses or decompresses | OpCon MFT agent — see OpCon MFT Transfer job |
| OpCon RPA | Integration | OpCon RPA Task | Legacy (relay) | No — none of any kind | OpCon RPA agent — see OpCon RPA Task job |
| EASE (Episys As A Service) | Integration | Twenty EASE - types (RSJ, RSJMULTI, RSJEDIT, MONITOR, PROMPT, PROMPTSEQ, TRANSLATE2COMMAS, RESET, SEQ, SEQ-SEND, five letter-file and report types, FILEPERMS, RUN-FTP-OUT, and three BUNDLE types that are not supported yet) | Legacy (relay) | No — none of any kind | EASE agent — see EASE jobs |
For the full per-job-type breakdown — internal names, connection types, and OS requirements — see the Job type catalog.
- Null Job is a workhorse for workflow design, not a no-op to dismiss: it's used to aggregate dependencies, hang events off a single point, and build a workflow on hold.
- Workflow Container embeds one workflow inside another — when troubleshooting a workflow, remember a job may itself be an entire child workflow.
- Legacy LSAM job types only work through a configured relay; "no agent available" for any of them usually points at the relay or LSAM connectivity, not the Universal Agent.
- Windows LSAM carries more than one job type. Besides Windows Command it provides a WS_FTP Pro file transfer, four file operations (copy, move, rename, delete), a Corelation batch job, and two Fiserv DNA jobs (an SQT job and a File Loader) — all with command lines the relay builds for you from form fields, so there's no command-line field to fill in. File Arrival is the exception: it waits for a file to turn up on the machine using the LSAM's own file watcher, so there is no connector to install and no command line at all. Windows LSAM also runs an Embedded Script job, which runs a script from the script library, and a Web Services job, which runs a multi-step HTTP/REST workflow through the SMA Web Services connector on the machine.
- IBM i LSAM now carries five job types — a batch job (IBM i Command), an Operator
Replay script, a Restricted Mode script, an FTP transfer and a File Arrival wait.
None of them has an exit-criteria setting, because IBM i exposes no exit code for the
relay to translate; a job can instead carry a message monitor that answers or acts on the IBM i
messages it raises. The message ID the agent reports when a job ends, such as
SMA0036, is the job's termination description. - SQL LSAM reaches beyond SQL Server. Besides its three SQL Server types it runs an Oracle SQL*Plus script, a MySQL script through the mysql client and, through Other DB, SQL over any ODBC driver or OLE DB provider installed on the machine. All six take an exit-criteria table, which Continuum always evaluates itself because the SQL agent cannot receive one.
- SAP R/3 and CRM LSAM starts an SAP background job that already exists in SAP, by its job name and job number. It has no exit-criteria setting and takes no connection: the SAP agent's verdict is the job's outcome, and the result code it reports is the job's exit code.
- SAP BW LSAM starts an SAP BW process chain that already exists in SAP, by its technical name, in the same way: no exit-criteria setting, no connection, and the agent's verdict is the outcome.
- z/OS LSAM has the z/OS LSAM submit a JCL member through JES, with JCL substitutions (z/OS Batch Job), start a procedure as a started task (z/OS Started Task), run a REXX exec (z/OS REXX Exec) or issue an operator command (z/OS Console Command). It has no exit-criteria table and takes no connection: a batch job or started task sets a condition-code range, and optional Step Control rows, that the z/OS agent judges each step by, a REXX exec a return-code range, and the agent's verdict is the outcome; a console command finishes as soon as the agent issues it. Dataset Pre-run rows can hold any of them until the datasets the job depends on are ready. Two more types, z/OS Tracked Job and z/OS Queued Job, hold no JCL: they give a job the z/OS agent reports — one submitted outside OpCon, or one the agent is holding — a place on its schedule, and finish with the condition code the agent reports.
- MCP LSAM runs a program (MCP Run), starts a WFL job (MCP Start), runs an EAE/AB Suite report (MCP EAE/AB Suite), or copies, renames or removes a file or a whole directory (MCP Copy, MCP Change, MCP Remove) on a Unisys MCP system, under an MCP usercode held in an MCP Batch User connection. It has no exit-criteria table: the MCP agent matches the job's fail codes against the MCP console display, and its verdict is the outcome. Any of the six can have a prerun, a second MCP job the agent runs first; the job waits and tries again until the prerun succeeds.
- OS 2200 LSAM starts an ECL runstream on a Unisys OS 2200 system (OS 2200 Job), with the run card values and runstream tokens you give. It has no exit-criteria table and takes no connection: the OS 2200 agent judges the run by the job's Completion Status rules, and its verdict is the outcome. The job can also wait on a prerun runstream, or on up to eight files, that the agent checks before it starts the job.
- SMAFT File Transfer is the one connector that spans platforms — a single job can move a file between a Windows, a UNIX and a z/OS machine — and the one whose machine you don't pick. You name both machines, and Start Transfer On decides which of the two runs the job. It also has no exit-criteria setting: the file-transfer agent's own verdict is the job's outcome.
- OpCon MFT is reached through a relay but is not an LSAM. It is a separate kind of agent with its own HTTPS API, so it has no JORS port and no file-transfer endpoint, and it cannot be either end of a SMAFT transfer. Its transfer job names one agent and moves files between two endpoints configured on it, and the endpoint and PGP key lists you pick from are read live from the agent rather than held in Continuum.
- OpCon RPA is the second connector reached over REST rather than the LSAM wire. Like OpCon MFT it rides a relay without being an LSAM, so it has no JORS port and no file-transfer endpoint, and the relay has to report that it can serve RPA agents before one can be registered under it. Its job type takes no connection at all and has no exit-criteria setting — the process status the RPA agent reports is the job's verdict.
- EASE is the third connector reached over REST rather than the LSAM wire, and the first that runs its jobs somewhere you do not administer. An EASE job adds a pre-built job to today's instance of your schedule on Jack Henry's EASE OpCon and waits for it; the remote status is the verdict, so there is no exit-criteria setting, and there is no connection to pick because the credentials live on the agent. Three of its twenty job types are in the catalog and fail at start — they add a container job to a local OpCon schedule, which Continuum has no equivalent for yet.
- Two connectors move files, and they solve different problems. SMAFT File Transfer moves a file between two legacy LSAM machines; OpCon MFT moves files between two endpoints on one MFT agent, with optional compression, PGP encryption and renaming along the way. Neither substitutes for the other.
Related topics