Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-7195

FIWARE.Request.Tech.IoT.BackendIoTBroker.Iot broker clarifications

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None

          Description

          sabrine fatnasssi sent a message using the contact form at
          http://catalogue.fiware.org/.

          Hello,

          I have some questions concerning the iot broker :

          1. how can I activate an optional bundle?
          I tried to enable it in the "setup.sh". It seems working but I dont know if
          it is the good way to do so.

          2. Can I get the last value of an entity attribute without querying the data
          source?
          I am used to Orion and I can get the last value updated from the data source
          queringwithout it.

          Thanks in advance for your help.

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-tech-help mailing list
          Fiware-tech-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-tech-help

          [Created via e-mail received from: sabrine.fatnassi@eglobalmark.com]

            Activity

            Hide
            Permalink
            fcirillo Flavio Cirillo added a comment -

            Dear Sabrine,

            regarding the first point, all the bundles provided by us are already mentioned in the setup.sh. Some of them are activated if the respective feature is enabled which are: bigdatarepository, historicalagent, entitycomposer, association.
            In order to activate them please add the respective configuration in the iotbroker.conf.local as described here: https://github.com/Aeronbroker/Aeron#configure-the-iot-broker-with-setup-scripts.
            Otherwise, if you other bundles implemented by you, you can add in the way you have done which is correct.

            Regarding the second point, we have developed a new feature in the last year which is the historicalAgent. The latter in charge of store historically contextElement passing through the IoT Broker. In order to activate it, make sure to have 'iotbroker_historicalagent="enabled"' configuration in the iotbroker.conf.local file.

            Thank you very much for using such features.
            Flavio

            Show
            fcirillo Flavio Cirillo added a comment - Dear Sabrine, regarding the first point, all the bundles provided by us are already mentioned in the setup.sh. Some of them are activated if the respective feature is enabled which are: bigdatarepository, historicalagent, entitycomposer, association. In order to activate them please add the respective configuration in the iotbroker.conf.local as described here: https://github.com/Aeronbroker/Aeron#configure-the-iot-broker-with-setup-scripts . Otherwise, if you other bundles implemented by you, you can add in the way you have done which is correct. Regarding the second point, we have developed a new feature in the last year which is the historicalAgent. The latter in charge of store historically contextElement passing through the IoT Broker. In order to activate it, make sure to have 'iotbroker_historicalagent="enabled"' configuration in the iotbroker.conf.local file. Thank you very much for using such features. Flavio

              People

              • Assignee:
                gessler Stefan Gessler
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: