Runtime Execution Profiles

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.

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 for the Production Profile
   In the Runtime Execution Profiles configuration, use the AutoStart option. This setting instructs the product to create a Windows service for the Production profile.
   
   
2. Edit the Windows Registry Key
   After enabling AutoStart, locate and edit the following registry key:
   Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TStartup-<SolutionName>
   Inside this key, update the ImagePath value to include the desired profile parameter in the command line used to start the solution.
   
   
3. Adjust the ImagePath Command
   By default, for a solution named Solution1, the ImagePath value appears as:
   <installation folder>\fx-10\TStartupService.exe /solution:"<path of solution>\Solution1.dbsln" /onlineconfig:true /port1:3101
   To run the Development profile, modify the key as follows:
   <installation folder>\fx-10\TStartupService.exe /solution:"<path of solution>\Solution1.dbsln" /profile:1 /onlineconfig:true /port1:3201
   The port must match the configuration set in the solution for the desired profile.
   
   
4. Profile Index Values
   Use the following values to select the execution profile:
   Development → /profile:1
   Validation → /profile:2
   Custom → /profile:3
   This approach allows you to configure and run any execution profile automatically when the service starts.
   
   
5. Verify the configuration
   Open Windows Services (services.msc).
   Find TStartup-<SolutionName> (Service).
   Open Properties and check Path to Executable.
   Confirm it reflects the Registry update, including the correct /profile: parameter.

Connection Properties

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

In this section: