Admin Workspace

The Admin panel (/admin) is for infrastructure configuration. Authenticate with the admin passkey, then manage hosts and endpoints. Regular users work in the main workbench and use My Credentials for host sign-in.

Hosts

Configured hosts appear as tabs. Opening a tab shows that host's address, type, and endpoints table. Only the selected tab's form is built, so switching tabs replaces the panel rather than stacking dialogs.

Add endpoints of the types this CoreIQ instance supports (RSE, JZOS, CICS, OL-CICS, CTG, IMS, IMS-DB, IMS-DLI, OL-DS, DB2, DB400, JT400, FTP, and others). Assign a catalog of the matching type so Browse, populate, and publish have a place to store associations.

Notable extras:

• IMS Connect: dataStoreName is required for Test Transaction and published APIs. IMSplex and IMS RESLIB are needed for Populate from IMS (QUERY TRAN). That flow also needs RSE on the same host.
• IMS-DB: Universal JDBC typically uses port 6695 (ODBM). Assign an IMS-DB catalog.
• OL-DS: extras control insert, update, and delete from View File (update on by default; insert and delete off).
• OL-CICS: Enable adapter test page adds Test Adapter in the tree.
• IMS-DLI: Allow user JCL template edit (on by default) lets users open Custom JCL on View Segments.

Settings

Open Settings for Hub connection options and the separate Published API form. Save the latter with Save API Settings. Generate an OpenAPI 3.0-compatible spec advertises GET .../list for table List operations instead of OpenAPI 3.2 QUERY. The router serves GET .../list either way.

AI settings (when licensed) live in the same Settings area.

Header tools

• VSAM CDC Monitor: change-data-capture sources on dataset servers: tracked VSAMs, status, destination, last cycle, and Start/Stop when the source state allows it.
• Common Regex: named regex patterns (name, category, pattern) that users apply from View File via Filter by regex. Patterns are shared, not per-host.
• Import / Export: copy configuration to another installation as a signed .crq package, from the dialog or with cURL. See Import / Export.
• Copy API Token: copies the current session bearer token after host credentials are saved. Published /api/v1/... routes accept that token as Authorization: Bearer ..., or Basic auth with the host username and password.

API-only installations

Set the OL_NO_UI environment variable (for example OL_NO_UI=true) and restart CoreIQ to run it as an API-only server. The web UI, the bundled help and docs, the /openapi and /swagger pages and the OpenAPI documents then answer 404, while /api, /host, the AI agent (MCP) interfaces, the health checks and /metrics keep working. false, 0, no or off keep the UI. Use it on any installation that only serves published APIs: the OpenAPI document lists everything published, and with the UI on it is served without sign-in.

See the child pages for token, regex, CDC, Import / Export, and published API details.