OpenLegacy Community

roi.m

Query Console Enhancements

Nested Table Tree Structure (7186692)
- Replaced table selection list with a nested tree structure for better organization
- Implemented context menus for table actions (create, alter, drop)
- Added table selection toggle and improved table details management
- New dialog for creating and altering tables
- Enhanced layout and responsiveness
Full Schema Loading & Inline Editing (5ffb78e)
- Background loading of full schema data for improved metadata management
- Inline editing for table cells with direct value modification
- Temporary and modified row tracking for unsaved changes
- Confirmation dialogs for unapplied modifications
- Enhanced error handling and user feedback
Query History (50cd30a)
- New history dialog for previously executed queries
- QueryHistoryService for managing query history per connection
- Ability to select and reuse past queries
- Improved data organization and user experience
Table Details Toggle (c1c8285)
- Button to toggle visibility of table details
- Improved layout handling for overflow
- Better responsiveness across different screen sizes

Data Export & Import

CSV Export (458125d)
- Export query results to CSV format
- Copy results to clipboard functionality
- User feedback via snack bars for operations
JSON Schema Export (e3eb18a)
- Export selected table schemas to JSON files
- Backend POST /export-json endpoint
- Export mode selection via radio buttons
JSON Schema Import (1020be2)
- Import table schemas from JSON files
- Option to override existing tables with drop option
- Backend POST /import-json endpoint
- File upload dialog with connection selection

Connection Management

Clone Connection (c0755b9)
- Clone existing database connections
- Automatic unique name generation
- Clears sensitive information (IDs, passwords) for cloned connections
- Updated UI layout for clone action button

Query Chat Enhancements

Sample Query Generation (4457b2b)
- Display sample queries for selected tables
- Generate sample INSERT statements for up to five tables
- Improved UI/UX for sample links and buttons

Utilities

Copy Table Details (bf53827)
- Copy table name and column details to clipboard
- Error handling and user feedback via snack bars

Bug Fixes

Token Fix (cdf496a)
- Fixed token-related issue

Other Changes

Merge Updates (e0c1083)
- Merged latest changes from main branch

Summary

This release includes significant enhancements to the Query Console, including a complete revamp with nested table tree structure, inline editing capabilities, query history, and comprehensive export/import functionality. The connection management has been improved with clone functionality, and the Query Chat component now supports sample query generation.
Total Commits: 12 (excluding merge commits)
Contributors: roi0507, Eddie

roi.m

Added Chat support (with full schema in context)
Solved navigation issues
Added ability to click on table details columns or result columns to add WHERE automatically

roi.m

Modernizing Green-Screen Access: Introducing OL Terminal for TN3270 & TN5250

For decades, TN3270 and TN5250 terminals have been the gateway to mission-critical systems on IBM mainframe and IBM i. These systems still run the heart of many enterprises, but the access method has barely changed. Traditional desktop terminal clients introduce cost, maintenance, and security risks.

OL Terminal changes that completely.

OL Terminal provides a modern, browser-based experience that mirrors traditional green-screen environments, but with centralized management, secure access, and zero desktop dependencies.

A Terminal Experience with No Installation

Users simply open a browser and start working. There is nothing to install, update, or distribute. This eliminates:

MSI rollouts
Admin permissions
Manual configuration
Version inconsistencies across locations

Any authorized user with a browser can access the host immediately.

Secure Access Over HTTPS

Traditional terminal connections often rely on unsecured TN streams. OL Terminal runs natively over HTTPS, introducing enterprise-grade security:

Central authentication
Encrypted sessions
SSO compatibility
Access control and auditing

Remote workers operate with secure connectivity without requiring desktop VPN-installed emulators.

Real-Time Terminal Interaction with WebSockets

OL Terminal communicates using WebSockets, providing responsive user interaction:

Instant screen refreshes
Synchronized cursor position
Reliable keystroke delivery
Low latency even across distance

The result is a true 1:1 experience comparable to classic installed emulators.

Productivity Enhancements

OL Terminal preserves a familiar terminal interface while introducing enhanced usability:

Macros

Automate multi-step sequences up to full process flows.

Type-Ahead Support

Users can continue entering commands even during screen transitions.

Keyboard Mapping

Define key layouts suitable for modern devices and user preferences.

Print-to-PDF

Export screens and workflows directly to PDF, without hardware printers.

Centralized IT Control and Visibility

Traditionally, green-screen usage is invisible once installed on desktops. OL Terminal changes this.

Admin Session Viewer

Support teams can observe session interaction live for:

Issue diagnosis
Training
Operational support

Policy Enforcement

Connection entry points, timeout values, routing paths, and identity rules can be defined centrally.

Session Inventory

Gain visibility into who is connected, where, and to which system.

This simplifies support, audit readiness, and usage monitoring.

OL Hub Integration – From Screens to APIs

Combined with OpenLegacy Hub, OL Terminal helps organizations modernize screen-based transactions.

Real session usage can be translated into:

Logical screen structures
Input/output data definitions
Sequence flows
Dynamic field relationships

These are surfaced as screen-based APIs without modifying COBOL, RPG, or existing transactions.

For example, customer lookup screens can become REST APIs using real navigation patterns observed through OL Terminal sessions.

This lets organizations gradually migrate business workflows into digital channels.

OpenLegacy TermIQ – Analytics, Insights & Auditing

TermIQ extends OL Terminal with usage intelligence:

Identify frequently used screens
Measure operational efficiency
Detect repeated errors
Audit user navigation
Track processing time

Examples of insights:

Why processing time differs across teams
Which flows frequently reach exception screens
Where user training gaps appear

This visibility was previously unavailable in traditional emulation models.

When OL Terminal Provides Maximum Value

OL Terminal is ideal for:

Customer support centers
Back-office and processing teams
Distributed branches
Remote and offshore workers
Testing environments
Training environments

All gain modern browser access without rollout effort.

Why OL Terminal Matters

OL Terminal uniquely combines:

User familiarity — same screens, same workflow
Centralized IT ownership — controlled access, observable sessions
Modernization readiness — terminal flows become APIs and analytics inputs

And the solution is free to use, lowering barriers for IT teams.

Summary

Area	Value
Access	Web-based, no installation
Security	HTTPS encrypted access
Operations	Session visibility and control
Productivity	Macros, type-ahead, PDF export
Modernization	Screen-to-API creation with OL Hub
Analytics	TermIQ tracking, behavior insight

OL Terminal modernizes access to mainframe and IBM i systems while preserving operational familiarity and offering IT new layers of visibility, control, and modernization opportunity.

Simple to deploy. Secure by design. Free to use.

This is the new standard for terminal access.

roi.m

Streamline Your OpenLegacy Development with Docker Compose

Introduction

If you're working with OpenLegacy tools, you know the pain of managing multiple services, configuring ports, and keeping track of different Docker commands. Today, I'm sharing a simple Docker Compose setup that brings all your OpenLegacy development tools together in one place, with a beautiful homepage to boot!

The Problem

Running OpenLegacy tools typically involves:

Memorizing (or constantly looking up) long docker run commands
Managing multiple container instances manually
Tracking which port runs which service
Dealing with volume permissions and data persistence
Remembering to set environment variables correctly

It's tedious, error-prone, and takes you away from what matters: building great applications.

The Solution

I've created a streamlined Docker Compose configuration that launches all your OpenLegacy tools with a single command. The setup includes:

A Beautiful Homepage (localhost:8080) - No more bookmarking multiple ports! A clean, modern landing page shows all your tools at a glance
OL Terminal (localhost:8081) - Your terminal-based development environment
OL Code (localhost:8082) - Full-featured code editor
️ SQOL (localhost:8083) - SQL and data management interface

Key Features

One Command to Rule Them All

Gone are the days of copy-pasting Docker commands. Just run:

./apps.sh start

That's it. All services spin up, properly configured, with persistent data volumes.

Centralized Configuration

All credentials and licenses are managed in a single config.env file. Update once, apply everywhere. No more hunting through Docker commands to change a password or license key.

Smart Data Persistence

Your work is automatically saved in named Docker volumes that survive restarts, updates, and even system reboots. Data only disappears if you explicitly delete it—no more "where did my data go?" moments.

Permission Issues? Solved.

The setup runs containers with proper permissions out of the box. No more FileNotFoundException or permission denied errors when tools try to write configuration files.

Professional Homepage

The included landing page isn't just functional—it's genuinely nice to look at. With a modern gradient design, hover animations, and responsive layout, it makes accessing your tools a pleasure rather than a chore.

Getting Started is Easy

Clone the repository
Copy your OpenLegacy license from your Community profile
Paste it into config.env
Run ./apps.sh start
Visit http://localhost:8080

That's the entire setup. No complex configuration, no troubleshooting, no headaches.

Perfect for Teams

The beauty of this setup really shines in team environments:

Consistent environments - Everyone runs the same configuration
Easy onboarding - New team members are productive in minutes
Version controlled - Check the compose file into Git (excluding the sensitive config.env)
Documentation included - Comprehensive README covers all common scenarios

Beyond the Basics

The helper script (apps.sh) provides convenient commands for common tasks:

./apps.sh logs     # View real-time logs
./apps.sh status   # Check service health
./apps.sh restart  # Quick restart
./apps.sh pull     # Update to latest versions

It also automatically loads environment variables from config.env, ensuring your configuration is always in sync.

Technical Highlights

For those interested in the implementation details:

Uses official OpenLegacy ECR images
Lightweight nginx:alpine for the homepage (just 40MB!)
Named volumes for data persistence
Root user execution to avoid permission issues on Windows/Mac
Environment variable interpolation for flexible configuration
Restart policies for automatic recovery

Conclusion

This Docker Compose setup transforms OpenLegacy development from a juggling act into a smooth, professional workflow. Whether you're a solo developer or part of a larger team, having all your tools accessible from a single, beautiful interface makes a real difference in daily productivity.

The entire setup is open and ready to use. Fork it, customize it, make it your own. Happy coding!

Repository: https://github.com/openlegacy/apps-manager
License: OpenLegacy
Contributions: Welcome!

Have questions or suggestions? Drop them in the issues section or reach out through the OpenLegacy Community.

roi.m

Ability to use mock session with trail file. Demo trails are available out of the box for mainframe and AS/400 cards demo
Zip package (JAR deployment) now contains mainframe.sh and as400.sh scripts for deploy/start/stop JAR on a remote host via SCP & SSH

roi.m

Hi @JZZSMB_gme , new version is available with JAR deployment on z/OS is available:
https://forum.community.openlegacy.com/topic/23/new-version-1.4.8-is-available

roi.m

Official support for running ol-terminal as JAR on Mainframe and AS/400. Readme and admin help documentation has how-to
Light/Dark themes
New buttons as icons (disconnect/refresh/restart/flip)
Fixed Hebrew PDF display issues for AS/400 when running on Docker
Printer panel improvements:

Save last filter selection
Do not load prints after loaded once (only on refresh/filter change)
Add local search field to search on the various print properties
Display date time, and file number on card

ohad.m

Hi @JZZSMB_gme ,

Running OL-Terminal on the Mainframe is on our roadmap.
Should be available soon.

I'll be sure to keep you updated

ruslan.a

Hi @JZZSMB_gme
Could you please share the Docker command you used to start the image?
You can send it here or via email to support@openlegacy.com

ohad.m

Hi @jeremiszlapka ,

We identified the problem with the TLS connectivity and fixed it.
You can download a new version from HERE.

Thanks

OpenLegacy Community

Global Moderators

Posts

Query Console Enhancements

Data Export & Import

Connection Management

Query Chat Enhancements

Utilities

Bug Fixes

Other Changes

Summary

Modernizing Green-Screen Access: Introducing OL Terminal for TN3270 & TN5250

A Terminal Experience with No Installation

Secure Access Over HTTPS

Real-Time Terminal Interaction with WebSockets

Productivity Enhancements

Macros

Type-Ahead Support

Keyboard Mapping

Print-to-PDF

Centralized IT Control and Visibility

Admin Session Viewer

Policy Enforcement

Session Inventory

OL Hub Integration – From Screens to APIs

OpenLegacy TermIQ – Analytics, Insights & Auditing

When OL Terminal Provides Maximum Value

Why OL Terminal Matters

Summary

Streamline Your OpenLegacy Development with Docker Compose

Introduction

The Problem

The Solution

Key Features

One Command to Rule Them All

Centralized Configuration

Smart Data Persistence

Permission Issues? Solved.

Professional Homepage

Getting Started is Easy

Perfect for Teams

Beyond the Basics

Technical Highlights

Conclusion

Member List