Execution profiles enable distinct configurations for a single solution, facilitating a seamless and swift transition between devices and databases.Development, Validation, and Production encompass diverse scenarios in which a solution must operate over its lifecycle. At times, these scenarios might intertwine, thereby posing risks to the entire operational environment. In this version, we introduce an intuitive approach to segregate these stages, thereby enhancing security and reliabilityProfiles 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. Functionality includes selecting profiles, enabling profile settings, setting modules to read-only, and replacing connections at startup. Before usage, configure profiles and enable settings. Use the Startup configuration interface to select and run profiles, applying environment-specific configurations.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Purpose and Key Concepts
When configuring a database or a device, it is necessary to provide the IP address along with access credentials through which our platform can communicate within the network. By associating different network access configurations with the same namespace, we establish the concept of execution profiles.
From the inception of a solution, a certain amount of time is required until it functions appropriately. During this period, it is common for its functionalities to undergo testing, adaptation, and occasionally, corrections.
Development
During the creation of a solution, it is imperative to test its functionalities as they are being implemented. At this stage, successive tests with slight parameter variations are often necessary to determine the optimal adjustments for the given scenario.
Production
The final stage of a solution involves its deployment into production. Here, all functionalities must have successfully passed through the validation process. Data generation, processing, and storage should be executed correctly.
This systematic approach ensures a meticulous progression from development to production, fostering efficient testing, verification, and reliable execution of the solution's functionalities.
Validation
At this stage, the proposed functionalities are subjected to verification, alongside vulnerability assessment. Consequently, the solution needs to closely resemble its state during production, ensuring its similarity.
Understanding Execution Profiles
The table is used to configure which database connections will be replaced when starting the application with a specific profile. The columns indicate which objects will be replaced, whether replacement is enabled, and provide details about the new database connections to be used. The entries in the table ensure that when selecting a profile, the appropriate connections are automatically applied, facilitating the management of different environments (development, validation, production).
Configuring Execution Profiles
To configure Execution Profiles, follow these steps:
Select Runtime Profile: Choose the profile (Development, Validation, Custom).
Enable Profile Settings: Check the box to activate the profile settings.
Set ReadOnly on Modules: Select which modules should be set to read-only mode.
On Startup Replace Connections: Use the data grid to specify and manage the connections that need replacement at startup.
Using Execution Profiles
To use Execution Profiles, follow these steps:
On the Designer workspace, go to Runtime/Startup.
Select the desired profile.
Run the solution with the selected profile, which dynamically applies the configured database connections or device nodes.
Properties Reference
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:
| Page Tree | ||||
|---|---|---|---|---|
|