Get familiar as an Administrator
Reading about OpCon Continuum only gets you so far. The fastest way to learn it is to do the core Administrator tasks in a test environment. Work through this checklist from top to bottom, checking off each item as you complete it. Each item links to the page that explains it in detail.
Goal: stand up and maintain the environment, agents, connections, and access.
Agents and pools
- Open an agent pool, then an individual agent.
- Read an agent's status (Online, Offline or Unknown), its last heartbeat, and its detected runtimes. An agent someone has deliberately taken out of service reads Marked Offline or Marked Draining instead.
- Adjust an agent's maximum concurrent jobs.
- See Manage agents and agent pools.
Plugins
- Open Plugins and view a plugin's detail.
- Enable an external plugin. Note that built-in and legacy LSAM plugins are enabled out of the box, but external plugins are not.
- Find where to set a plugin's default version.
- See Manage plugins.
Connections
- Confirm your role grants the
connectionspermissions on all workspaces — a connection carries no workspace, so a role scoped to particular ones cannot reach it. See Connections are tenant-wide. - Create a database connection and use Test Connection to confirm it works.
- Edit the connection and confirm credential fields appear blank. That's intentional.
- See Manage connections and Set up database connections.
Agent readiness
- Review the file paths an agent is allowed to use, and where script interpreters and database drivers need to be installed.
- See Prepare agents for connectors.
Environments, workspaces, and custom fields
- View or create an environment and check its service health.
- Create a workspace and note what's scoped to it.
- Define a custom field, and try a select field with a few options.
- See Manage environments, Manage workspaces, and Define custom fields.
Roles and permissions
- Open Roles, then browse the permission catalog at
/roles/catalog. - Create a role: choose its permissions and set its scopes.
- Run permission simulation for the role at
/roles/simulationand read the results. - Know what roles control: which screens a person can open everywhere, and every action and list in design and administration areas — but not the actions on Processes, Agents, the Event Log or Environments. See What roles control today.
- See Manage roles and permissions.
Reporting
- Run a job-history report for a date range and environment, then export it.
- See Create and run reports.
You're ready when
You can inspect an agent, enable a plugin, create and test a connection, set up a workspace, and run a report.
Related topics