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
Command | Function | Status Indicators |
---|---|---|
Run Startup | Starts the application | Button changes to Stop |
Stop | Stops the application | Button changes to Run |
Online Configuration | Apply changes in real-time | Must 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:
Profile | Purpose | Default Port |
---|---|---|
Development | Debugging enabled, dev tools active | 3301 |
Validation | Testing environment | 3201 |
Production | Optimized for production | 3101 |
Custom | User-defined settings | User-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:
Setting | Description | Default |
---|---|---|
Main Port | Primary access port per profile | Profile-dependent |
Auto Ports | Auto-select if main unavailable | Disabled |
WA Port | Windows Authentication port | As configured |
Windows Authentication | Require Windows auth only | Unchecked |
SSL Port | HTTPS web access | 3111 |
AutoStartup/Windows Service | Run at system startup | Disabled |
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
Option | Description | Use Case |
---|---|---|
Direct File Access | Local file access | Single-user development |
Solution Server | TWebServices connection | Multi-user collaboration |
Path/Use Solution Path | Override default path | Redundancy configuration |
DataHub Service
Enable solution data sharing:
Setting | Function |
---|---|
Publish to DataHub | Share objects with remote DataHub |
DataHub Settings | Configure 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:
Setting | Function |
---|---|
Publish to MQTT Broker | Make UNS visible to MQTT clients |
TMQTT Broker Settings | Configure security and options |
Startup Modules
Select modules to activate at startup:
Module | Function | Impact |
---|---|---|
Devices | Enable device communication | Required for field data |
Alarms | Enable alarm processing | Required for notifications |
Historian | Enable data logging | Required for trending |
Datasets | Enable database access | Required for queries |
Reports | Enable report generation | Required for documents |
Scripts | Enable script execution | Required for logic |
Displays | Launch WPF client locally | Opens TRichClient |
OpenBrowser | Launch web client | Opens default browser |
OPC Server | Enable OPC DA/UA server | External access |
Redundancy Settings
Configure high-availability environment:
Setting | Description | Format |
---|---|---|
Primary Server IP/Port | Main server address | IP:Port |
Secondary Server IP/Port | Backup server address | IP:Port |
Timeout | Switchover delay | Seconds |
On Primary Startup | Recovery behavior | Switch/Keep |
Replication | Data to replicate | Alarm/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
Client | Command/URL | Options |
---|---|---|
Rich Client | TRichClient.exe /port1:3101 | NoSplash, ViewOnly |
Smart Client | http://IP:Port/smartclient | SSL available |
HTML5 Client | http://IP:Port/html5 | SSL available |
Client Options
Option | Function |
---|---|
NoSplash | Skip splash screen |
WA | Windows Authentication |
SSL | Secure connection |
ViewOnly | Read-only mode |
Network Access
Accessing HTML5 from Other Devices
- Identify server IP (not 127.0.0.1)
- Ensure port accessibility
- Use URL:
http://ServerIP:Port/html5
- For SSL:
https://ServerIP:Port/html5
Example:
- Server IP: 192.168.0.8
- Port: 3201
- URL:
http://192.168.0.8:3201/html5
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 Designer UI (Reference) - Parent section
- Runtime Execution Profiles (Reference) - Profile configuration
- Runtime Build and Publish (Reference) - Solution deployment
- Solution Deployment (Guide) - Production setup
Runtime Startup Page when All Features are enabled
Runtime Startup Page, when Basic Modules Filter is Selected
In this section: