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 reliability.
On this page:
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.
| Index | Description |
|---|---|
| 1 | Select the profile to run the solution. |
| 2 | When running a solution, it's possible to select one or more modules to run on read-only mode. This means that the module will not write any data on Databases or create report files on server. |
| 3 | This table shows all the parameters that will be overwrite when change to selected profile. |
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 placeholder
In this section: