The Runtime Startup section allows you to start and stop solution execution, specify execution profiles, and customize connection settings. Settings defined here apply to all runtime scenarios including command line and Windows service startup.

Access: Runtime → Startup

Parent Page: Runtime Designer UI (Reference)



Main Commands


Execution Controls


CommandFunctionStatus Indicators
Run StartupStarts the applicationButton changes to Stop
StopStops the applicationButton changes to Run
Online ConfigurationApply changes in real-timeMust be connected to runtime

Note: All changes must be saved before they appear in runtime when online configuration is enabled.


Execution Profiles


Select the environment-specific configuration:

ProfilePurposeDefault Port
DevelopmentDebugging enabled, dev tools active3301
ValidationTesting environment3201
ProductionOptimized for production3101
CustomUser-defined settingsUser-defined

The Production profile uses main configuration without overrides. Other profiles apply configured replacements at startup.


Startup Port Settings


Configure network ports for application access:

SettingDescriptionDefault
Main PortPrimary access port per profileProfile-dependent
Auto PortsAuto-select if main unavailableDisabled
WA PortWindows Authentication portAs configured
Windows AuthenticationRequire Windows auth onlyUnchecked
SSL PortHTTPS web access3111
AutoStartup/Windows ServiceRun at system startupDisabled

AutoStartup Behavior

Windows Platform:

  • Configures as Windows Service
  • Starts without user login
  • Runs under system account

Multiplatform on Remote Devices:

  • Configures in TWebServicesRunPrograms.json
  • Starts with TWebServices
  • Enables remote management


Execution Environment


Execution Path Settings


OptionDescriptionUse Case
Direct File AccessLocal file accessSingle-user development
Solution ServerTWebServices connectionMulti-user collaboration
Path/Use Solution PathOverride default pathRedundancy configuration

DataHub Service

Enable solution data sharing:

SettingFunction
Publish to DataHubShare objects with remote DataHub
DataHub SettingsConfigure connection parameters

DataHub Settings Dialog:

  • Alias: Solution identifier
  • Primary/Secondary Host: Server addresses
  • Port: TCP communication (default: 30001)
  • AccessKey: Authentication

Built-in Broker Settings

MQTT broker configuration:

SettingFunction
Publish to MQTT BrokerMake UNS visible to MQTT clients
TMQTT Broker SettingsConfigure security and options


Startup Modules


Select modules to activate at startup:

ModuleFunctionImpact
DevicesEnable device communicationRequired for field data
AlarmsEnable alarm processingRequired for notifications
HistorianEnable data loggingRequired for trending
DatasetsEnable database accessRequired for queries
ReportsEnable report generationRequired for documents
ScriptsEnable script executionRequired for logic
DisplaysLaunch WPF client locallyOpens TRichClient
OpenBrowserLaunch web clientOpens default browser
OPC ServerEnable OPC DA/UA serverExternal access


Redundancy Settings


Configure high-availability environment:

SettingDescriptionFormat
Primary Server IP/PortMain server addressIP:Port
Secondary Server IP/PortBackup server addressIP:Port
TimeoutSwitchover delaySeconds
On Primary StartupRecovery behaviorSwitch/Keep
ReplicationData to replicateAlarm/Tag Historian

Recovery Options


  • Switch back to primary: Auto-return when available
  • Keep secondary active: Manual switchback required


Command Lines and URLs


Startup Command Line


TStartup.exe /solution:"path\solution.dbsln" /profile:1 /OnlineConfig:true /port1:3301

Parameters:

  • /solution: - Solution file path
  • /profile: - 1=Dev, 2=Val, 3=Custom
  • /OnlineConfig: - Enable online changes
  • /wa - Windows Authentication
  • /port1: - Override port


Client Access


ClientCommand/URLOptions
Rich ClientTRichClient.exe /port1:3101NoSplash, ViewOnly
Smart Clienthttp://IP:Port/smartclientSSL available
HTML5 Clienthttp://IP:Port/html5SSL available

Client Options

OptionFunction
NoSplashSkip splash screen
WAWindows Authentication
SSLSecure connection
ViewOnlyRead-only mode


Network Access


Accessing HTML5 from Other Devices


  1. Identify server IP (not 127.0.0.1)
  2. Ensure port accessibility
  3. Use URL: http://ServerIP:Port/html5
  4. For SSL: https://ServerIP:Port/html5


Example:


Monitor Access

Direct browser access to runtime monitor:

http://ServerIP:Port/html5/?Monitor=Runtime

Startup Procedure

Step 1: Launching TStartup.exe

  • Loads the Solution
  • Reads Solution Configuration
  • Parses Command Line Parameters
  • Activates Main Process TServer.exe

Step 2: Starting the Real-Time Database

TServer.exe starts by loading solution objects, tags, templates, and assets into memory. A communication service is established, allowing other modules to start and connect.

Step 3: Modules Startup

Other modules (Historian, Alarms, Devices, Scripts, Datasets, Reports) start execution by reading solution configuration and establishing connection with the main process.

Step 4: Applying Execution Profiles

Modules behave according to Execution Profile definitions. Example:

  • Development: Temporary local SQLite database
  • Production: SQL server for production data

Step 5: Solution Designer Automatic Connection

Designer automatically connects to running solution for monitoring and diagnostics.

Step 6: Opening Client-Side Displays

Operations displays (HTML5 or WPF) can be opened from any remote computer.

Step 7: Applying Online Changes and Hot Updates

System applies configuration changes without disrupting runtime.

Platform-Specific Features


Features exclusive to Windows Target Platform:

  • Windows Authentication
  • Windows Service configuration
  • OPC Classic support
  • Specific security features


See Also







Runtime Startup Page when All Features are enabled


Runtime Startup Page, when Basic Modules Filter is Selected

In this section: