...
→ For details on setting up the execution review the Solution Deployment (Reference) page.
...
Runtime in the Four Pillars (Concept)
Runtime Execution Overview
During Runtime, the Four Pillars transform from static configuration into an active system. Each pillar operates as an independent yet interconnected layer, with data flowing from field devices through the foundation layer, processed by business logic, and presented to users through visualization interfaces.
...
Execution model (Runtime, services, UNS)
Client types (desktop, web)
Basic diagnostics you’ll use first
...
Runtime Components
| Component | Function | Access |
|---|---|---|
| TServer | Core execution engine | Runs as service |
| Tag Database | Real-time data storage | In-memory |
| Module Engines | Execute specific functions | Auto-started |
| Client Server | Serves displays to clients | TCP port 9000 |
Component Relationships
- TServer hosts the tag database
- Modules connect to TServer for data exchange
- Client Server retrieves data from TServer
- All components share the solution configuration
...
Execution Modes
Development Mode
- Full diagnostics enabled
- Detailed error messages
- Performance monitoring
- Online configuration changes
Production Mode
- Optimized performance
- Minimal logging
- Security enforced
- Stable operation
The same solution behaves differently based on the execution mode, controlled by the Execution Profile selected at startup.
...
Client Types
Runtime supports multiple client types simultaneously:
Desktop Client (Rich)
- .NET WPF application
- High-performance graphics
- Local installation required
- Direct server connection
Web Client
- HTML5 browser-based
- No installation needed
- Responsive design
- WebAssembly support
Mobile Client
- Adapted web interface
- Touch-optimized
- Works on tablets and phones
- Same server connection
...
Basic Diagnostics
Three essential tools for monitoring Runtime:
1. Runtime Information
- Access: Solution Center → Tools → Runtime Info
- Shows: Module status, memory usage, connections
- Purpose: Overall system health
2. Property Watch
- Function: Monitor tag values in real-time
- Details: See quality indicators and timestamps
- Usage: Debug data flow and values
3. Diagnostics Window
- Content: View logs and traces
- Analysis: Performance metrics
- Troubleshooting: Error identification
Monitoring Runtime
- Runtime Information
- Solution Center → Tools → Runtime Info
- Shows module status, memory, connections
- Property Watch
- Monitor tag values in real-time
- See quality and timestamps
- Diagnostics
- View logs and traces
- Analyze performance
...