Start, monitor, and manage your solution’s runtime execution. 

How-to → Solution Lifecycle How-to →  Runtime | Tutorial | How-to Guide | Reference

Overview

This guide covers starting, monitoring, and managing runtime execution, including execution profiles, online changes, and troubleshooting.

Prerequisites

  • Solution configured in Designer
  • Appropriate runtime license
  • Understanding of execution profiles

Starting the Runtime

Startup Methods

MethodStepsUse Case
Designer Test ModePress F5 or click Run TestDevelopment testing (2-hour limit)
Designer Full RuntimeRuntime → Startup → Run StartupDevelopment with profile selection
Solution CenterSelect solution → Run in ProfileProduction deployment
Command LineTStartup.exe /solution:"name" /profile:ProductionAutomation/service mode

Startup Sequence

  1. TStartup.exe loads solution and parses parameters
  2. TServer.exe starts real-time database
  3. Modules initialize (Historian, Alarms, Devices, Scripts)
  4. Execution profile applies settings
  5. Client connections become available

Command Line Parameters

TStartup.exe /solution:"MySolution" /profile:Production /username:admin /redundancy:primary
ParameterDescription
/solution:Solution name or path
/profile:Development/Validation/Production
/username:Credentials if required
/redundancy:Primary/secondary/standalone

Execution Profiles

Profile Configuration

ProfileDatabaseStorageSecurityDiagnostics
DevelopmentSQLite localMemory onlyMinimalFull trace
ValidationTest SQL ServerTest storageTest credentialsPerformance metrics
ProductionProduction SQLFull storageFull authenticationErrors only

Configuring Profiles

  1. Go to Runtime → Execution Profiles
  2. Select profile to configure
  3. Set database connections
  4. Configure historian storage
  5. Define alarm database
  6. Adjust communication ports

Monitoring Runtime Status

Status Information

PropertyLocationInformation
Solution StatusRuntime → StatusRunning/stopped, uptime, profile
Module StatusModule InformationIndividual module health
Resource UsageDiagnosticsCPU, memory, threads
CommunicationDevices statusChannel and node status

Using Info Namespace

// Check runtime status
bool isRunning = @Info.Module.IsRunning;
string solution = @Info.Solution.Name;
bool testMode = @Info.TestMode;

// Write trace message
@Info.Trace("Runtime started successfully");

// Check license
int tagCount = @Info.License.TagCount;

Online Configuration Changes

Hot Reload Capabilities

Apply Without RestartRequires Restart
- Tag values and limits
- Display modifications
- Script logic updates
- Alarm conditions
- User permissions		- Device channels
- Database connections
- Port assignments
- Module enable/disable
- License changes

Applying Online Changes

  1. Make changes in Designer
  2. Save modified items (Ctrl+S)
  3. Click Apply Online Changes
  4. Select modules to update
  5. Confirm application

Client Connections

Connection Types

Client TypeSetupAccess Method
Web ClientNo installationhttp://server/solution
Smart ClientAuto-downloadClick-once deployment
Rich ClientFull installationDesktop application
MobileResponsive designBrowser on device

Build and Publish

Build Process

  1. Go to Runtime → Build
  2. Select build options: • Compile scripts • Validate displays • Check references
  3. Click Build
  4. Review output for errors

Publish Process

  1. Go to Runtime → Publish
  2. Set version number
  3. Choose publish options: • Read-only (.dbrun) • Encrypted • Include resources
  4. Click Publish
  5. Deploy .dbrun file

Runtime Diagnostics

Diagnostic Tools

ToolPurposeAccess
Property WatchMonitor/modify tag valuesRuntime → Diagnostics → Property Watch
Trace WindowView system messagesRuntime → Diagnostics → Trace Window
Module InformationModule performance metricsRuntime → Diagnostics → Module Info

Trace Levels

  • Error - Critical issues only
  • Warning - Warnings and errors
  • Info - General information
  • Debug - Detailed diagnostics

Stopping Runtime

Shutdown Methods

MethodStepsNotes
DesignerRuntime → Startup → Stop RuntimeGraceful shutdown
Solution CenterSelect solution → StopRemote shutdown
Command lineTStartup.exe /solution:"name" /stopScripted shutdown
EmergencyTask Manager → End TServer.exeForce stop

Troubleshooting

Common Issues

IssueCheckSolution
Runtime won't startLicense, ports, databaseCheck event log, verify connections
High CPU usageScripts, scan ratesOptimize scripts, reduce scan frequency
Memory growthHistorian, scriptsCheck retention, dispose objects
Client can't connectFirewall, servicesOpen ports, verify server running
Database failsConnection string, networkTest connectivity, check credentials

Best Practices Checklist

Startup

  • Use appropriate profile for environment
  • Test in Development before Production
  • Document profile settings
  • Backup before changes

Monitoring

  • Set up critical error alerts
  • Monitor resource usage trends
  • Archive trace logs periodically
  • Check module health daily

Online Changes

  • Test changes in Development first
  • Apply during low-activity periods
  • Have rollback plan ready
  • Document all changes

Explanation - to understand concepts

→ Modules / Solution Lifecycle  / Runtime

Tutorials - to learn by doing

→ Tutorials /  Solution Lifecycle / Runtime Tutorial

How-to Guides - to accomplish specific tasks

→ How-to Guides / Solution Lifecycle / Runtime How-to Guide

Reference - technical details

→ Technical Reference /  Solution Lifecycle / Runtime Reference


In this section...