Page History

Image Removed

Understanding Execution Profiles

During the solution's life cycle is typical that the same solution has to be executed in distinct environment, such as:

• Development
• Custom (like a Laboratory or a Customer site) 
• Validation 
• Production 

In general, each of those environments may have an specific setup for testing Databases and Devices, so even though the solution you want to run and test is the same, those specific connection settings are unique to each of those environments. 

Most of the platforms require a manual modification in the solution, before running on those environments. That manual intervention is time-consuming and risky, because it can easily introduce errors to the solution configuration. 

Our platform provides a simple and unique way to manage that. You just define the various Profiles you may have, and you can customize specific connections to each one those profiles. 

The Production profile corresponds to the Solution Configuration with no replacements. For the other Profiles, you can configure which connections shall be replaced when running on those other environments.

Configuring Execution Profiles

To configure Execution Profiles, follow these steps:

1. Go to Runtime → Execution Profiles.

2. Choose the profile (Development, Validation, Custom).

3. Check the Enable Profile Settings box to activate the profile settings.

4. Select which modules should be set to read-only mode at Set ReadOnly on Modules.

5. The On Startup Replace Connections option uses the data grid to specify and manage the connections that need replacement at startup.

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

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:

Using Execution Profiles

To use Execution Profiles, follow these steps:

1. Go to Runtime / Startup.

2. At Execution Profile, select the desired profile.

3. Run the solution with the selected profile, which dynamically applies the configured database connections or device nodes.

Running profiles as a service

To run a solution using the settings from one of the execution profiles as a Windows service, follow these steps:

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

1. 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

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

See Also

• Runtime Designer UI (Reference) - Parent section
• Runtime Startup (Reference) - Profile selection
• Solution Settings (Reference) - Environment setup

Image Added

Connection Properties

This table outlines each property, helping to understand its purpose and role within the Execution Profiles configuration.

Property

Description

ReplaceObject

Specifies the object (database or device node) to be replaced during execution. Identifies the target object within the solution configuration.

Replace

Indicates whether the replacement should occur. A boolean value (true/false) that enables or disables the replacement process for the specified object.

TableType

Shows which DataTable is being replaced or changed. Its name is the manual pathing to such table, e.g. DatasetsDBs for Datasets / DBs.

ServerIP

Defines the IP address of the server to connect to during execution. Used to specify the target server for the connection replacement.

DateCreated

Records the date and time when the replacement entry was created. Provides a timestamp for tracking changes in the configuration.

DateModified

Records the date and time when the replacement entry was last modified. Tracks updates and modifications to the configuration.

ReplaceConnection

In this section: