NEO6 is a modular, extensible platform for legacy modernization and interoperability, focused on enabling seamless integration between modern applications and mainframe/COBOL systems. The project is organized into several subfolders, each with a specific role in the overall architecture.
-
agent-runtime/: Core runtime and orchestration logic for NEO6 agents. Handles lifecycle, scheduling, and communication between agents and the platform.
-
aiops-agent/: Components and logic for AIOps (Artificial Intelligence for IT Operations) within NEO6. Provides monitoring, anomaly detection, and automated remediation capabilities.
-
cobol-agent-core/: Core libraries and utilities for COBOL agent integration. Facilitates communication and data mapping between COBOL programs and the NEO6 platform.
-
python-agent-core/: Core libraries and runtime for Python-based agents. Used for scripting, orchestration, and integration tasks that require Python's flexibility.
- neo6-chat/: Python-based conversational interface for NEO6 systems. Features:
- Interactive terminal chat (Claude-style interface)
- OpenAI-compatible API server
- LangChain integration for MCP (Model Context Protocol) servers
- Support for local LLMs via LM Studio
- Tool calling capabilities for NEO6 proxy operations
- docs/: Project documentation, architecture diagrams, and technical references for developers and users.
- infra/: Infrastructure-as-code, deployment scripts, and configuration for cloud/on-prem environments. Includes Terraform, Docker, and CI/CD resources.
- neo6-admin/: Administrative interface and management tools for NEO6 proxies. Provides web-based dashboard for monitoring, configuration, and control of proxy instances.
- neo6-auth/: Robust authentication and session management module for NEO6. Features:
- Session management for both NEO6 clients and external servers
- Multi-protocol authentication support (TN3270, LU6.2, MQ, REST APIs, TCP, JCA)
- User authentication with role-based access control
- Server authentication configuration and credential management
- Integration with neo6-proxy for automatic authentication checks
- REST API for authentication operations and session monitoring
-
neo6-protocols/: Rust workspace containing protocol adapters and traits for all supported legacy and modern protocols (LU6.2, MQ, REST, TCP, JCA, MCP, etc). Includes:
neo6-protocols-lib/: Common protocol traits and helpers (e.g.,ProtocolHandler).lu62/,mq/,rest/,tcp/,jca/,mcp/,tn3270/: Protocol-specific implementations.tests/: Protocol-level tests.
-
neo6-proxy/: Main proxy server for NEO6. Exposes REST, TCP, MQ, and MCP endpoints to modern and legacy clients, routing requests to the appropriate backend (COBOL, microservices, etc). Features:
- Multi-protocol support with dynamic transaction routing
- Integrated authentication checks via neo6-auth
- Configuration-driven transaction mapping
- Comprehensive logging, metrics, and monitoring
- Support for all major enterprise protocols
-
runtime/: Deployment runtime with binaries, configurations, and startup scripts for running NEO6 in production environments. Includes:
- Control script (
neo6.sh) for managing all NEO6 services - Complete configuration management for all modules
- Authentication configuration and credential management
- Protocol-specific configurations and examples
- Logging and monitoring setup
- Control script (
For more details on each component, see the README.md inside each folder or the documentation in docs/.
cd runtime/
./neo6deploy.sh # Build and deploy all components
./neo6.sh start # Start authentication + admin services
./neo6.sh status # Check service status- Admin Dashboard: http://localhost:8090 (proxy management and monitoring)
- Authentication API: http://localhost:8091 (authentication and session management)
- Admin API: http://localhost:8090/api (programmatic proxy control)
- NEO6 Proxy: Start with
neo6-proxy/for core functionality - Admin Interface: Use
neo6-admin/for management and monitoring - Authentication: Configure
neo6-auth/for secure access control - Chat Interface: Try
neo6-chat/for conversational interaction with NEO6 systems
NEO6 includes comprehensive authentication for enterprise environments:
- Server Authentication: Configure credentials for mainframes, MQ servers, REST APIs
- User Management: Role-based access control with admin and operator roles
- Session Management: Automatic session handling and cleanup
- Multi-Protocol Support: TN3270, LU6.2, IBM MQ, REST/OAuth2, TCP, JCA
See runtime/config/auth/ for configuration examples and documentation.
- Robust Authentication: Multi-protocol authentication for mainframes, APIs, and legacy systems
- Session Management: Secure session handling with configurable TTL and automatic cleanup
- Role-Based Access: Granular permission control with admin and operator roles
- Credential Security: Encrypted credential storage with Argon2 password hashing
- Mainframe Protocols: TN3270, LU6.2 (SNA/APPC) for CICS and legacy systems
- Enterprise Messaging: IBM MQ, TCP sockets for reliable messaging
- Modern APIs: REST/HTTP, OAuth2, API key authentication
- Enterprise Integration: JCA (Java Connector Architecture) adapters
- AI Integration: Model Context Protocol (MCP) for LLM interactions
- Scalable Architecture: Modular design with independent service scaling
- Comprehensive Monitoring: Built-in metrics, logging, and health checks
- Easy Deployment: Single-script deployment with automatic dependency management
- Configuration Management: YAML-based configuration with validation and examples
- Conversational Interface: Natural language interaction with enterprise systems
- AIOps Integration: Automated monitoring and remediation capabilities
- LLM Integration: Support for local and cloud-based language models
- Tool Calling: Direct LLM access to NEO6 proxy operations
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ NEO6 Chat │ │ NEO6 Admin │ │ NEO6 Auth │
│ (Port 8000) │ │ (Port 8090) │ │ (Port 8091) │
│ │ │ │ │ │
│ • LLM Interface │ │ • Web Dashboard │ │ • User Auth │
│ • Tool Calling │ │ • Proxy Control │ │ • Server Auth │
│ • MCP Support │ │ • Monitoring │ │ • Session Mgmt │
└─────────┬───────┘ └─────────┬───────┘ └─────────┬───────┘
│ │ │
└──────────────────────┼──────────────────────┘
│
┌─────────────────┐
│ NEO6 Proxy │
│ (Dynamic) │
│ │
│ • Protocol Hub │
│ • Transaction │
│ Routing │
│ • Auth Checks │
└─────────┬───────┘
│
┌───────────────────┼───────────────────┐
│ │ │
┌─────▼─────┐ ┌─────▼─────┐ ┌─────▼─────┐
│Mainframes │ │ APIs │ │ Legacy │
│ │ │ │ │ Systems │
│• CICS/TSO │ │• REST │ │• TCP/MQ │
│• TN3270 │ │• OAuth2 │ │• JCA │
│• LU6.2 │ │• Banking │ │• Custom │
└───────────┘ └───────────┘ └───────────┘
-
🔐 NEO6 Authentication Module: Complete authentication and session management system
- Multi-protocol server authentication (TN3270, LU6.2, MQ, REST, TCP, JCA)
- User authentication with role-based access control
- Automatic session management with configurable TTL
- Integration with neo6-proxy for transparent authentication checks
-
🚀 Enhanced Runtime Management: Improved deployment and service management
- Unified control script (
neo6.sh) managing all NEO6 services - Automatic service dependency handling (auth → admin → proxies)
- Comprehensive service monitoring and health checks
- Simplified deployment with
neo6deploy.sh
- Unified control script (
-
⚙️ Configuration Management: Streamlined configuration handling
- YAML-based configuration with validation
- Example configurations for all supported protocols
- Centralized credential and authentication management
- Environment-specific configuration support
- Security Enhancements: Argon2 password hashing, encrypted credential storage
- API Improvements: Comprehensive REST APIs for all services
- Monitoring: Enhanced logging, metrics, and status endpoints
- Documentation: Updated technical documentation and configuration examples
For detailed information on each component, see the README.md files in individual folders or the comprehensive documentation in docs/.
✅ System Validation: See INTEGRATION_VALIDATION.md for complete integration validation report and system status.
The NEO6 project has undergone comprehensive integration testing and validation. All core components are operational and properly integrated:
- Authentication & Security: ✅ Fully operational with multi-protocol support
- Service Management: ✅ Complete deployment and runtime management
- Documentation: ✅ Comprehensive technical documentation
- API Integration: ✅ All service APIs working and validated
For detailed validation results and system status, see the Integration Validation Report.