Start Today

← Documentation

Getting Started

OL TermIQ turns recorded terminal activity into reusable screen knowledge, business operations, runtime evidence, Hub flows, alerts, and MCP-accessible evidence.

  1. Create or select a workspace. Or choose Add demo workspace for a ready Mainframe cards, AS/400 cards, or Mainframe insurance example.
  2. Record events through the OL Terminal webhook or import a trail.
  3. Curate screens and snapshots; optionally use AI identification.
  4. Review suggested operation definitions or create them manually; collect completed instances.
  5. Analyze completed instances in Runtime → Flow and create Hub artifacts.
  6. Monitor events and operations in reports.
  7. Raise alert rules on recorded activity and email a recipient list. Turn on the alert engine and SMTP under Account → Settings first.
  8. Use MCP to search recorded evidence, or sign in to a live terminal. A mock connection can play a stored trail instead of a host.
  9. Move design to another install with Export design time and Import design time. The file is a .trq. Recorded events stay on the source.
  10. Open API Reference in the sidebar, or /openapi, to read and try the REST API.

On cloud, Help & User Guide opens this OL Edge documentation in a new tab. On-prem and lite installs keep the bundled guide. A process started with OL_NO_UI serves the API and the API reference, and does not serve the bundled guide.

Use a dedicated workspace for each application, pilot, or analysis environment.

Use the TermIQ pipeline to capture, identify, alert, analyze, and modernize terminal activity.

Read more