Installation of IDAS to Use with ORION CB - fiware

I have an Orion CB working on a virtual machine just fine.
Now i have a gateaway that communicates in mqtt. So i want to use IDAS as an iot Agent to make the link between my GW and Orion CB.
My question is how do i install IDAS?
I have this : https://github.com/telefonicaid/fiware-IoTAgent-Cplusplus/
It really is not clear at all what are the spteps to take in order to install and use it. Can any one explain?
Or is there any kind of Virtual machine with IDAS already installed on it, like for the orion CB?
Thanks

I think I ended up asking the same question here.
The easiest way to install IDAS on a CentOS machine is through its RPM's available in it's calogue page.
As of now I'm having other issues with such installation, but maybe you won't have them.
I hope this helps even though it comes so late.

Related

fiware-orion context broker mongoDB docker

I am trying to run Orion Context Broker on Linux Mint using docker, but i cant start it. Also I tried installing MongoDB version 3.2 also on Linux Mint using docker, but cant find any installation solution.
Can someone help me?
Thank you for your help!!!
Orion, at startup, connects to Mongo. If mongo isn't accepting the connection, Orion exits. There is nothing the broker can do without its database.
So, that would explain why Orion doesn't start.
Why such an old version of Mongo?
Lastly, if you add detailed information on the problem you see, perhaps you can get some help. Without that, there's no way to help.

Connect Context Broker with mysql

How to store data in mysql using OrionContext broker and Cygnus?
I installed the image: orion-PSB-image-R5.2.
But I do not know where to configure Orion.
Should I install base_centos_6 and then install ContextBroker and Cygnus?
Fiware documentation is very confusing.
You don't need to install Orion if your VM has been created using the orion-psb-image-R5.2 image. You can start Orion (if it doesn't started yet) using the following command:
sudo /etc/init.d/contextBroker start
Orion documentation can be found here. In addition, you can find useful the following introduction. We think that Orion documentation is rather complete and detailed, but if you find confusing is some point, please explain exactly in which one so we can improve it.

Fiware: Can we use cygnus on Raspberry Pi

Can we install cygnus on RaspberryPi?
Thinking of using it with Cepheus to add persistance on the gateway level.
Thanks in advance for your help!
Never tried, nevertheless it is a Java application, so having a JVM and the proper libraries should work. Most probably the memory is a problem, so it is probably you could not handle a high througput of notifications. In any case, as said, it is a matter of trying.
The keypoint for using it with Cepheus is if Cepheus notifies in the same format than Orion Context Broker. If not, Cygnus will not understand the notifications.
Another important thing is the storage aimed to be used for persistence. I don't know if any of the supported storages in Cygnus, for instance MySQL or MongoDB, can be run wihtin a Raspberry Pi! In this case, the best option may be to install the storage in a remote machine.

Fiware IDAS & Orion Production Deployment

I would like to know what is the common deployment pattern for IDAS and Orion in a production environment. Are they usually deployed as docker images or as a native service? If they are as a docker images then do they usually go together in one container or separate containers?
Thank you.
I can provide an answer from the point of view of Orion Context Broker (I hope that some of my colleagues from IDAS team can answer also that part).
Deployment options (look for slides "How to get Orion" in this presentation) are the following ones:
Image in FIWARE Lab cloud
Docker contaniner
VirtualBox image
RPM installation (from FIWARE repositories)
Compiling from sources
For IDAS it depends on the specific IoT-Agent you are using.
If you are using Ultralight2.0/HTTP or MQTT to connect devices, all the information for installation is available here:
https://github.com/telefonicaid/fiware-IoTAgent-Cplusplus/blob/release/1.3.0/README.md
On the other hand, if you will use OMA LWM2M/CoAP to connect devcies, this info is here:
https://github.com/telefonicaid/lightweightm2m-iotagent/blob/master/docs/administrationGuide.md
Also, docker files are available here:
http://catalogue.fiware.org/enablers/backend-device-management-idas/creating-instances
Hope this helps.
Cheers,

How to connect to my MQTT Broker in Openshift

Following these two tutorials (https://www.anavi.org/article/182/ and http://wei-meilin.blogspot.tw/2014/05/red-hat-openshift-xpaas-simple-mqtt.html) I have installed a MQTT Broker using JBoss Fuse.
Although my mqtt-container disappears after a while (I don't know why) I can make a port-forwarding and test the broker.
But I would like to know how to connect directly to the broker. Do you know how to do it?
I have tried this tutorial (http://training.runcloudrun.com/advanced/16-Network-and-Protocols.md.html - AMQ Example) but I don't have access to "/var/lib/openshift/.httpd.d/sniproxy.cfg"
I am the author of the first tutorial that you pointed out. If you want to use MQTT without local port forwarding please have a look at the remark at the article on my blog and the AMQ cartridge that demonstrates the SNI features:
The port forwarding is not convenient for real life cases, especially if the MQTT clients are working on embedded devices such as microcontrollers and it is recommended to use a SNI Proxy as explained here: http://training.runcloudrun.com/advanced/16-Network-and-Protocols.md.html
I was using Online Openshift and that feature is only available for Enterprise edition.
Why doesn't Openshift have this feature (complete) in the Online mode?
One way to work around is to use the mqtt over websocket feature with a DIY cartridge. See the SO question "How can I access socket through Openshift" for some pointers to further details about how to run websocket on openshift.
The mosquitto seems to have implemented the websocket feature though I have not verified by testing it out.