| Section | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Templates
Definition, Types and Structure
Templates are xml files which contain all the sensor configuration for all the sensors. This includes sensors, actions, rules and everything the azeti SiteController is programmed to do. This file will later be deployed to each site.
...
All the changes done to a template are inherited to the templates below them. So if a sensor inside component instance is edited, all the site templates and locations templates that use it will be edited as well automatically. The exception being those changes that were done directly on the lower template. So if, for example, sensor X state threshold is changed on a site template, and then on a component instance, the change done directly on the site template will take precedence, and the change done on the component instance will not be applied.
Using Components and Components instances
The first step to create a template would be to upload one:
...
This will show all the sections of the configuration file as a tree, with the values on the left side. To change this values click 
Controller Software
For the deployments, jobs, updates and validations to be done correctly, the correct version of the site controller has to be uploaded to the server. To see which ones are already uploaded go to Management→ Software → Software Packages.
...
To upload a new version click +Add and upload the new package.
Deployments
To send the Site Template to the site, upgrade the software, or update the SiteController configuration, go to Management → Provisioning → Deploy
The list of online sites will be shown. The following filters can be used to filter down the sites:
- Sites: pressing the button will show the location tree that allows to filter the alarms by location or region (as defined on the location tree).
- Online: If left checked, it will only show the alarms from online sites. Uncheck to show the alarms of all sites (both online and offline).
- Site Template: Select only the sites with an specific Site Template.
- Site Configuration: Select only the sites with an specific Site Configuration.
- Controller Software: Select only the sites with an specific Site Controller software version.
Single Site Deployment
To deploy to a single site click on the deploy button next to the site. A new window will appear:
There select the kind of deployment to be done: Site Template, Site Configuration or Controller Software. By default Site Template is selected. If the template is valid, then a green check mark will appear next to the site name: 
If a red mark (
) appears that means the site template is not valid, and the deployment will not be done. In that case please check the site template. If valid, press Schedule to trigger the update. If the template is not valid the Schedule button will be shaded and cannot be pressed.
After the deployment is done, if successfully sent, a green check will appear next to the site config (
). If not it will show a red cross (). On the bottom of the screen the reply messages from the Site Controller will appear:
Multiple Site Deployment
To deploy to multiple sites at the same time, select the sites using the check boxes at the left. Selecting the checkbox on the top will select all visible sites.
Use this in combination with the filters at the top of the page to deploy only to specific sites. The Sites Tree filters can also be used to deploy only to sites in certain location group (open the tree on the top left, click on the icon to the left of the group name)
\ 
Once the sites are selected, click the Deploy button on the top left.
The number displayed there is the number of sites that will be updated. After pressing the Deploy the same page as for the single deployment will appear:
In this case it will show all the sites to be deployed, with a mark indicating that the template is valid and ready to deploy (green check ) or no (red cross 
). If any of the sites templates is not valid the Schedule button will be shaded and cannot be pressed. If all the templates are valid press Schedule for the deployment.