Because many people have experienced the same kind of issues we are attempting to provide a better overall solution:
BE Device Manager GE implementation (IDAS) as initially designed and developed as a carrier-grade m2m solution to translate lots of IoT specific protocols to our ContextBroker protocol/API (NGSI).
Therefore the software was significantly monolithic/heavy and difficult to install for external guys and its extensibility via C++ plug-in was OK for Telco partners but not for the overall common ity of developers that we are targeting now once we have open-sourced it too.
As a consequence, to address better long tail developers we are in the process of totally re-factoring this component in a much lighter and modular architecture, where each southbound IoT protocol will be translated to NGSI at the north with an specific “IoT Agent”.
The functionality will be the same as the previous IDAS/SBC except we are providing support to new IoT protocols such as LWM2M/CoAP (in addition to the current SML/UL2.0 over HTTP and MQTT) but the installation process in your own VMs will be better automated in OpenStack and it will be easier to be installed in any other VMs at other Clouds or physical machines too.
Because of all this, we recommend to use our public IDAS/SBC instance in the Cloud today. See the details of this instance and the APIKEY (shared secret) to use at this post:
http://www.fi-ware.org/2014/06/18/connect-your-own-internet-of-things-to-fi-lab/
For installing the software we encourage you to wait for the above-described re-factorization to happen (IoT Agents will be provided in Jan 2015 together with installation documents).
however, you may try to deploy your own image please login in our Cloud at https://cloud.lab.fi-ware.org , then go to the images folder (https://cloud.lab.fi-ware.org/#nova/images/) and then select the one called “eidas-sbc-img” and deploy it for your own usage.
We will close this ticket, should you have any other doubt, want to keep the same issue or issue it again, please provide us with a new ticket.
Thanks for using our IoT enabler!
extRequest
Major
Because many people have experienced the same kind of issues we are attempting to provide a better overall solution:
BE Device Manager GE implementation (IDAS) as initially designed and developed as a carrier-grade m2m solution to translate lots of IoT specific protocols to our ContextBroker protocol/API (NGSI).
Therefore the software was significantly monolithic/heavy and difficult to install for external guys and its extensibility via C++ plug-in was OK for Telco partners but not for the overall common ity of developers that we are targeting now once we have open-sourced it too.
As a consequence, to address better long tail developers we are in the process of totally re-factoring this component in a much lighter and modular architecture, where each southbound IoT protocol will be translated to NGSI at the north with an specific “IoT Agent”.
The functionality will be the same as the previous IDAS/SBC except we are providing support to new IoT protocols such as LWM2M/CoAP (in addition to the current SML/UL2.0 over HTTP and MQTT) but the installation process in your own VMs will be better automated in OpenStack and it will be easier to be installed in any other VMs at other Clouds or physical machines too.
Because of all this, we recommend to use our public IDAS/SBC instance in the Cloud today. See the details of this instance and the APIKEY (shared secret) to use at this post:
http://www.fi-ware.org/2014/06/18/connect-your-own-internet-of-things-to-fi-lab/
For installing the software we encourage you to wait for the above-described re-factorization to happen (IoT Agents will be provided in Jan 2015 together with installation documents).
however, you may try to deploy your own image please login in our Cloud at https://cloud.lab.fi-ware.org , then go to the images folder (https://cloud.lab.fi-ware.org/#nova/images/) and then select the one called “eidas-sbc-img” and deploy it for your own usage.
We will close this ticket, should you have any other doubt, want to keep the same issue or issue it again, please provide us with a new ticket.
Thanks for using our IoT enabler!