Skip to main content

Administrator learning path

This is the order to work through the Administrator pages. Environments and workspaces come first because everything else is scoped to them, then the agents and connections that jobs actually run through.

You don't have to follow it end to end. Each module stands on its own, so it also works as a checklist for one area you're picking up.

How to read a module

Each module runs from the task to the detail: the how-to page first, then the concept behind it, then the full reference, and finally an end-to-end scenario where one exists. Stopping after the how-to page is a perfectly good outcome if that's all you need today.

8 modules · 22 pages · about 2 hr of reading estimated so far, across 7 of the 22 pages

  1. Administration

    What you'll be able to do
    • Explain roles, the permission catalog, and scope tuples
    • Explain what roles control in the interface, and what they do not protect

  2. Agents

    What you'll be able to do
    • Interpret agent status, type, and heartbeat, and explain the three routing modes
    • Explain what a relay is, how it authenticates, and how to register, install, and rotate credentials for one
    • Explain how a process on a legacy machine raises a Continuum event without an inbound network path
    • Provision and migrate the service-account credential an agent-raised event line has to carry
    • Set the Default event environment a legacy agent needs before any event it raises can be applied
    • Write an event line that Continuum accepts, including the mandatory trailing credential pair
    • Predict which event families are applied, which are refused, and which are accepted and then fail
    • Trace an agent-raised event in the event log, and know which rejections leave no trace there

  3. Connections

    What you'll be able to do
    • Explain how connections are defined, secured, and tested, and which types exist today
    • Define a batch user for a legacy Windows, UNIX, IBM i, or SQL platform and attach it to a job
    • Apply the editing rules that keep a stored secret from being destroyed by an ordinary edit

  4. Plugins

  5. Notifications

  6. Reports

    What you'll be able to do
    • Identify the report categories and how a report is built, saved, and exported

  7. Transitioning from OpCon Classic

  8. Environments

    What you'll be able to do
    • Describe what an automation bundle contains and what export omits
    • Choose between the default fail-on-conflict import and overwrite mode
    • Explain why an import is a clone rather than a restore

Where the time estimates come from​

The estimates are authored per page and not every page has one yet, so a module or role total covers only the pages that do — treat it as a floor, not a full syllabus.

Related topics