TServer Components
The Runtime Engine (TServer) is the heart of FrameworX execution:
| Component | Function | Key Features |
|---|
| Core Engine | Central coordinator | Module management, event routing, memory management |
| Tag Services | Real-time database | In-memory storage, microsecond updates, quality management |
| Module Host | Module execution | Dynamic loading, lifecycle management, isolation |
| Communication Layer | Network services | Client connections, protocol handlers, buffering |
| Security Context | Access control | Authentication, authorization, audit logging |
Memory Architecture
| RUNTIME MEMORY SPACE |
|---|
Real-time Tag Database (In-Memory) - Current Values
- Quality & Timestamps
- Cached Metadata
|
Module Memory - Device Buffers
- Alarm States
- Script Context
- Client Sessions
|
System Cache - Configuration
- Security Tokens
- Performance Metrics
|
Process & Threads Model
TServer Process
- Modules - Services Thread Pool
- TagProvider
- Alarm Processing
- Historian Services
- Datasets & SQL Services
- Solution DB & Cached metadata
- Client Services Threads
- TCP Listener Thread
- Client Handler Threads (1 per client)
- Web Service Thread Pool
- System Threads
- Garbage Collection
- Performance Monitoring
- Diagnostics Logging
Script Module Process
- Script Task Execution
- Default: One Thread by Task
- Multi-thread (1 per Task)
- Configurable settings to max threads & Multiple threads per Task
- Scripts Expression Execution
- On thread, event driver execution
- Script Classes - Client Services Threads
Data Flow Architecture
Real-Time Data Flow
Event-Driven Architecture
