Overview

Runtime Execution is the production environment where your FrameworX solution operates in real-time. The Runtime engine (TServer) processes all solution logic, manages communication with field devices, executes scripts, logs data, and serves information to clients. Runtime provides high-performance execution with built-in redundancy, diagnostics, and hot-reload capabilities for 24/7 industrial operations.

Where It Fits in the Platform 



Core Architecture Components

Three-Tier Architecture



Runtime is the execution layer that brings your solution to life:

Runtime Architecture

TServer (Runtime Engine)

Core execution service managing all runtime operations:

Runtime Modules

Each module runs as coordinated subsystem:

Execution Profiles

Development Profile

For testing and debugging:

Validation Profile

For system testing and validation:

Production Profile

For live operations:

Starting Runtime

Startup Sequence

  1. Initialize Database - Connect to solution database
  2. Load Configuration - Read all module settings
  3. Allocate Memory - Create tag database in RAM
  4. Start Services - Initialize each module
  5. Connect Devices - Establish field communications
  6. Accept Clients - Enable client connections

Startup Options

Command Line Parameters

TServer.exe [solution] [options]
  /solution:path     - Solution file path
  /profile:name      - Execution profile
  /port:number       - Server port
  /redundancy:mode   - Standalone or primary/backup
  /trace:level       - Diagnostic level

Server Components

Tag Runtime Database

High-performance in-memory database:

Communication Manager

Handles all external connections:

Event Processor

Central event handling system:

Module Execution

Device Module Runtime

Alarm Module Runtime

Historian Module Runtime

Script Module Runtime

Client Types

Rich Client (.NET)

Full-featured Windows desktop client:

Web Client (HTML5)

Browser-based zero-install client:

Mobile Client

Native iOS and Android applications:

Data Client

Programmatic access for integration:

Performance & Diagnostics

Performance Metrics

Real-time monitoring of system health:

Diagnostic Tools

Runtime Trace

Detailed execution logging:

Info Monitor

Real-time status dashboard:

Property Watch

Live tag monitoring:

Log Files

Persistent diagnostic information:

Hot-Standby Redundancy

Configuration

Primary and backup server setup:

Failover Process

Automatic switchover on failure:

  1. Failure Detection - Heartbeat timeout
  2. Backup Activation - Assume primary role
  3. Client Redirect - Automatic reconnection
  4. State Recovery - Restore last values
  5. Notification - Alert administrators

Synchronization

Keeping servers aligned:

Online Configuration

Hot-Reload Capability

Change configuration without stopping:

Online Change Process

  1. Make Changes - In Designer test mode
  2. Validate - Check for conflicts
  3. Apply Online - Send to runtime
  4. Verify - Confirm activation
  5. Save - Persist to database

Limitations

Some changes require restart:

Security & Access Control

Authentication Methods

Authorization Levels

Security Features

Best Practices

Startup Procedures

Performance Optimization

Maintenance Operations

Troubleshooting

SymptomLikely CauseSolution
Runtime won't startDatabase connection issueCheck connection string and SQL server
High CPU usageExcessive polling or scriptsReview device scan rates and script efficiency
Client can't connectFirewall or port issueVerify port is open and not blocked
Memory growthMemory leak or retentionCheck retentive tag settings and script objects
Slow performanceDatabase or network bottleneckAnalyze performance logs and network traffic
Failover not workingNetwork or configuration issueVerify heartbeat network and redundancy settings
Values not updatingDevice communication failureCheck device status and communication logs

Related Topics

AI Assistant Data

<details> <summary>Structured Information for AI Tools</summary>

json

{
  "module": "Runtime Execution",
  "category": "Platform Architecture",
  "purpose": "Production execution environment for real-time operations",
  "components": {
    "core": "TServer.exe",
    "modules": ["Tag Processor", "Device Manager", "Alarm Processor", "Historian", "Script Engine"],
    "profiles": ["Development", "Validation", "Production"],
    "redundancy": ["Standalone", "Hot-Standby", "Load-Balanced"]
  },
  "clientTypes": [
    {"type": "Rich Client", "platform": ".NET/Windows"},
    {"type": "Web Client", "platform": "HTML5/Browser"},
    {"type": "Mobile Client", "platform": "iOS/Android"},
    {"type": "Data Client", "platform": "API/REST/OPC UA"}
  ],
  "performance": {
    "tagCapacity": "Unlimited with proper sizing",
    "clientConnections": "Unlimited based on hardware",
    "pollingRate": "10ms minimum",
    "eventResolution": "1ms"
  },
  "diagnostics": [
    "Runtime Trace",
    "Info Monitor",
    "Property Watch",
    "Performance Logs"
  ],
  "security": {
    "authentication": ["Windows", "Forms", "Certificate", "SSO"],
    "encryption": "TLS/SSL",
    "audit": "Complete activity logging"
  }
}

</details>