Runtime Execution Profiles Reference

 Manage multiple execution profiles.

Reference → Solution → Runtime → UI → Startup | Build and Publish | Execution Profiles | Monitor

Profile Overview

Execution Profiles eliminate manual configuration changes when moving solutions between environments:

Production profile uses solution's main configuration. Other profiles apply replacements at runtime.

Configuration Interface

Profile Settings

For each profile (Development/Validation/Custom):

Read-Only Modules

Select modules to protect from changes:

• Tags
• Devices
• Alarms
• Scripts
• Displays

AI Runtime-Write Gate

Each profile carries a per-profile gate that controls whether the DesignerMCP set_object_value tool is allowed to drive runtime values (Tag.* and other Object Model paths) under that profile. The tool is the AI authoring counterpart to a Script writing into a tag — same write semantics (eRunEvent.Changed: equal-write is silent), same kernel coercion, same downstream effects on subscribers (Scripts on Tag.Changed, Alarms watching the value, Historian on-change samplers, Device output handlers).

When a profile blocks AI runtime writes, the tool refuses with errorCode AI_OBJECT_WRITE_DISABLED and a structured payload pointing to this column — the AI surfaces the exact "uncheck the AIWriteReadOnly flag on this profile” guidance to the user.

The flag has the same polarity as the Read-Only Modules family above — checked means blocked, unchecked means allowed. Partner integrations that write tags via the WebAPI use a separate JWT-scoped gate model (see Runtime API reference) and are unaffected by this column.

Connection Replacement

Replacement Table Columns

Supported Replacements

Using Profiles

In Designer

1. Go to Runtime → Startup
2. Select Execution Profile
3. Run solution
4. Profile replacements apply automatically

Command Line

bash

# Development
TStartup.exe /solution:"solution.dbsln" /profile:1

# Validation
TStartup.exe /solution:"solution.dbsln" /profile:2

# Custom
TStartup.exe /solution:"solution.dbsln" /profile:3

Windows Service Configuration

Running Profiles as Service

AutoStart is Production-only by default. To run other profiles:

1. Enable AutoStart in Production profile
2. Edit Registry Key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TStartup-<SolutionName>

1. Modify ImagePath:

# Original (Production)
TStartupService.exe /solution:"path\solution.dbsln" /port1:3101

# Modified (Development)
TStartupService.exe /solution:"path\solution.dbsln" /profile:1 /port1:3201

Profile Index Values

Typical Configurations

Development Profile

Common replacements:

• Local test database
• Simulation devices
• Debug file paths
• Test email server

Validation Profile

Common replacements:

• Staging database
• Test PLCs
• QA file shares
• Test notifications

Custom Profile

Use cases:

• Laboratory setup
• Customer demo
• Training environment
• Pilot installation

Best Practices

Profile Design

DO:

• Keep Production unchanged
• Document all replacements
• Test profile switching
• Use meaningful names

DON'T:

• Modify Production directly
• Mix environment data
• Skip validation testing
• Use production credentials

Security Considerations

• Never store production passwords in profiles
• Use environment-specific credentials
• Limit profile access
• Audit profile changes
• Leave AI Runtime-Write blocked on Production / Validation / Custom unless an engineer has explicitly opted in for an authoring session

Verification

Check Active Profile

Monitor shows current profile:

• Info.ProfileName property
• Runtime System Monitor page
• Client status bar

Verify Replacements

Confirm replacements applied:

1. Check connection strings
2. Test device communication
3. Verify database access
4. Monitor data flow

Troubleshooting

In this section...