Overview
Execution Profiles is a configuration feature in the Runtime Module that manages database connections and device nodes for different environments. It automates the application of settings for development, validation, and production stages. Features include selecting profiles, enabling profile settings, setting modules to read-only, and replacing connections at startup. Before use, configure the profiles and enable the settings. Use the Startup configuration interface to select and run profiles, applying environment-specific configurations.
On this page:
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:
- Go to Runtime → Execution Profiles.
Choose the profile (Development, Validation, Custom).
Check the Enable Profile Settings box to activate the profile settings.
Select which modules should be set to read-only mode at Set ReadOnly on Modules.
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:
Go to Runtime / Startup.
At Execution Profile, select the desired profile.
Run the solution with the selected profile, which dynamically applies the configured database connections or device nodes.
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. |
ServerIP | Defines the IP address of the server to connect to during execution. Used to specify the target server for the connection replacement. |
DataCreated | 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 | Specifies the connection string or parameters for the new connection. Defines the details of the replacement connection to be applied at startup. |
In this section: