Overview
Execution profiles enable distinct configurations for a single project, facilitating a seamless and swift transition between devices and databases.Development, Validation, and Production encompass diverse scenarios in which a project 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. 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:
| Table of Contents | ||||
|---|---|---|---|---|
|
Understanding Execution Profiles
During the solution life cycle is typical that the same solution has the be execution in distinct environment, such as:
- Development
- Custom (like a Laboratory or a Customer site)
- Validation
- Production
In general, each of those environments my have an specific setup for its testing Databases and Devices, so even 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 risk, as quite easily can 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. |
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 project, 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 project, 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.
Validation: At this stage, the proposed functionalities are subjected to verification, alongside vulnerability assessment. Consequently, the project needs to closely resemble its state during production, ensuring its similarity.
Production: The final stage of a project 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 project's functionalities.
Understanding
Imaginemos um projeto onde os requisitos sejam:
1 - Ler valores de uma tag do tipo Inteiro em um broker (IP: 192.168.5.39) que utilize o ptotocolo MQTT spB e armazenar em um historian.
2 - O Historiador utilizado na producao é o Canary DB.
3 - Durante o desenvolvimento deve ser utilizado um SQLite local.
Nesse cenario, é recomendavel que o projetista siga os seguintes passos:
- Criar uma Tag do tipo Integer.
- Criar um chanel MQTTspB.
- Criar um Node no chanel criado anteriormente e configurar o campo primary station com o IP 192.168.5.39, que é o IP do broker.
- Configurar
- Configurar o perfil de execução na modalidade Development.
No laboratorio, o projetista tem a sua disposicao um computador rodando Windows 10 e uma copia do PLC desejado, mas nao tem a licensa do canary e nem acesso ao servidor oficial da empresa.
O projetista decide instalar e utilizar uma vesao demo do canary em sua maquina para realizar o projeto.
Nesse cenario, o ele deve realizar a configuração do Device com o IP do do CLP de testes, assim como configurar a conexao do banco de dados local, pois esta utilizando a versao demo rodando em sua propria maquina.
Ao finalizar o projeto, se a supervisão desejar implementar o projeto,, pode-se facilmente escolher os dvices que se deseja alterar o endere
Configuring
Device configuring
add print
Dataset Configuring
Working
Content placeholderIn this section:
| Page Tree | ||||
|---|---|---|---|---|
|