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

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        11d 6h 35m 1 Stefan Gessler 13/Sep/16 5:21 PM
        In Progress In Progress Answered Answered
        5s 1 Stefan Gessler 13/Sep/16 5:22 PM
        Answered Answered Closed Closed
        20s 1 Stefan Gessler 13/Sep/16 5:22 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        backlogmanager Backlog Manager made changes -
        Summary [Fiware-tech-help] [IoT Broker] Iot broker clarifications FIWARE.Request.Tech.IoT.BackendIoTBroker.Iot broker clarifications
        HD-Node Unknown [ 10852 ]
        gessler Stefan Gessler made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        gessler Stefan Gessler made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        gessler Stefan Gessler made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        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
        backlogmanager Backlog Manager made changes -
        Assignee Stefan Gessler [ stefan.gessler ]
        backlogmanager Backlog Manager made changes -
        HD-Chapter Unknown [ 10845 ] IoT [ 10839 ]
        mev Manuel Escriche made changes -
        HD-Enabler Unknown [ 10910 ] IoT Broker [ 10885 ]
        backlogmanager Backlog Manager made changes -
        HD-Enabler Unknown [ 10910 ]
        HD-Chapter Unknown [ 10845 ]
        HD-Node Unknown [ 10852 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        fw.ext.user FW External User created issue -

          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: