|
The features on this page require a GENESIS64 Advanced license and are not available with GENESIS64 Basic SCADA . |
GENESIS64 includes a way to deploy containers on IoTEdge devices integrated in Workbench.
In this way you can manage your devices without using Azure Portal.
The collection of available ICONICS containers is defined in the Containers.config.xml file (stored in C:\Program Files\ICONICS\GENESIS64\Components folder).
The configuration file contains the list of containers that it’s possible to deploy on an IoT Edge device in Workbench Desktop (from an IoT project, expanding a group of IoT devices, right clicking on an IoT Edge device and selecting ‘Configure Modules’ action).
It supports multiple versions of the product, which means that you can have multiple collections of containers for each supported version of the product.
There is a set of attributes that are in common for all the containers:
ProductVersions - The list of versions of the product that are currently supported separated by ‘;’. (e.g 10.96;10.96.1;10.96.2)
EdgeAgentVersions - The list of available Edge Agent versions, one for each supported product version separated by ‘;’ (e.g. 1.0.9;1.0.9.1;1.0.9.2)
EdgeHubVersions - The list of available Edge Hub versions, one for each supported product version separated by ‘;’ (e.g. 1.0.9;1.0.9.1;1.0.9.2)
AvailableRepositoryNames - The list of available repository names (where the containers are stored) separated by ‘;’ (e.g. repository-a;repository-b)
RepositoryNameIndex - The index of the current repository name (it’s 0-indexed)
For each container it’s possible to set these attributes:
Name - The name of the container (used internally as unique key)
DisplayName - The display name of the container (shown in the GUI)
ImageURI - The image URI of the container; it contains the placeholder [repositoryName] that will be replaced with the current repository name (e.g. [repositoryName]/containerName)
ProductVersions - The string to be placed in the Image URI to represent the selected product version, one for each supported product version, separated by ‘;’
CreateOptions - The create options of the container
DependsOn - The list of containers that are mandatory for the container (empty means that the container itself is mandatory to include in the deployment, “None” that it is totally independent)
RepositoryNameIndex - Overrides the repository name index in common (not mandatory)
When deploying a container the Image URI will be modified adding the suffix related to the currently selected product version.
For instance, let’s assume we have:
AvailableRepositoryNames=”repositoryA;repositoryB;repositoryC”
RepositoryNameIndex=”1”
and two containers:
Name=”containerA”
ImageUri=”[repositoryName]/containerA”
RepositoryNameIndex=”2”
and
Name=”containerB”
ImageURI=”[repositoryName]/containerB”
they will be resolved as:
“repositoryC/containerA”
“repositoryB/containerB”
See Also: