KMSYS Worldwide
All documentation
eQuate/User Guide

eQuate — Overview and Quick Start

Tour eQuate components, runtime modes, the publish/runtime model, and the basic steps for capturing host screens and shipping an eQuate application.

Last updated November 20, 2013

What eQuate is

eQuate captures legacy host screens (UTS and T27) and presents them as modern Windows applications without changing the host program. Designers capture screens, define forms and actions, then publish a runtime database; end users run the resulting application from the eQuate Session Manager or through eQuate Web.

The publish / runtime model

Designers and administrators work locally and then publish to a shared server. The published bundle contains the eQuate runtime files, the application database, and per-user configuration (routes, station names, host IP addresses). End users always run against the published copy — never edit the local working copy directly.

Components

  • Capture — records the host screens that drive the application.
  • Application Manager — bundles screens into applications, manages forms, pick lists, help text, and standard messages.
  • Form Designer — visual editor for the Windows-side forms users actually see.
  • Action Editor and Script Editor — author the navigation and business logic that wires form events to host transactions.
  • QPort T27/UTS Config and WinQ T27/UTS Config — connection transports.
  • Administration — user accounts, profiles, backup/restore.
  • Session Manager — the launcher end users run; one row per available application.
  • Unpackage — restore a published bundle on a new server.

Runtime modes

  • Screen Mode — the default; the form is presented and host traffic is hidden.
  • Command Mode — exposes the underlying host screen for debugging or for transactions the designer chose not to wrap.

Basic steps to a working application

  1. Configure a connection (QPort or WinQ) and verify it reaches the host.
  2. Use Capture to record the screens the application will own.
  3. In Application Manager, define the application, attach the captured screens, and pick a default form.
  4. Open each form in Form Designer and lay out controls; bind fields to capture variables.
  5. Author the action / script logic that moves users between forms and submits transactions.
  6. Publish the application database and runtime files to the shared server.
  7. End users sign on through Session Manager (or eQuate Web) and pick the application.