Page Comparison

This guide describes what steps have to be taken when a customer wants to install SiteController-1.3 on a running system, which is already connected to the azeti Engine. This HowTo can technically not be called an upgrade. The upgrade functionality will not be given for version 1.3. Instead the customer has to do a fresh installation. This guide explains the steps necessary and gives some guidelines on things to keep in mind. 

...

• The file azeti_logging.cfg is obsolete. All logging-related settings are now integrated into SiteController.cfg

• As a result SiteController.cfg is not compatible between 1.2 and 1.3 - hence a real upgrade is not possible

• Modules can be defined to autostart in SiteController.cfg or the SensorConfig
• A new major module is the data_store. This module now takes over the tasks of hd2cloud exporter & cloud connector
• Status-Command of Site Controller does now include the status of the connection to the external broker and port used / configured
• Various bugfixes and improved stability 
  • data_store is able to repair a single DB-corruption (Please note: second DB-corruption will break the Site Controller and a manual restart is mandatory)
  • XML-parsing is more robust

Abstract / Overview

This guide describes how to remove the currently installed Site Controller in version 1.2 and do a fresh install with the version 1.3 of the Site Controller. After the new version has been installed, the customer will re-apply custom changes from the old installation. An automated approach has not yet been tested to a statisfactory result, therefore the manual approach has to be taken.

...

1. Execute the script "setup.sh" 

   Code Block
   language bash
   root@ubuntu1404MaxVM1:/home/user/SiteController-install# sh ./setup.sh

   Info
   Minor errors can be ignored. Should the installation completely stop, please inspect the output for errors. Otherwise it appears to be save to ignore them.

2. During the Installation, you will be asked to provide a serial for the new installation.

   Info
   title Please make sure, that this serial is the same across both versions of SC.
   If in doubt, please have a look at the serial defined in old_SC.cfg which you backed up in Step 5.

3. Navigate to the installation-directory of the new SiteController. 

   Code Block
   language bash
   root@ubuntu1404MaxVM1:/home/user# cd /opt/azeti/SiteController/

4. Use your preferred editor to open the file "config/SiteController.cfg".

   Code Block
   language bash
   root@ubuntu1404MaxVM1:/opt/azeti/SiteController# vim config/SiteController.cfg

   
   The following values have to be present, for any SiteController to start and work:

   1. Serial (This is already set, since it was entered by the customer during the installation)
   2. External-Broker host (e.g. cloud-dev.azeti.net)
   3. organizationsShortName (e.g. QA)
   4. user_id (username of user with gateway-permissions in cloud)
   5. password (PW of said user) 
      

    

5. Depending on your SiteController-configuration it can be necessary to add / tweak more aspects of the config (eg. RemoteExecutionJobs or which Serial-Interfaces to use for ModBus-devices). Please reference your previously backed up SiteController.cfg

   Code Block

   language	bash

   root@ubuntu1404MaxVM1:/opt/azeti/SiteController#

   
   

6. After your changes have been done, save and close the file

...