I am a student who just started working on a research project, which is to compare Kaa with Eclipse Kura. I don't have any knowledge about IoT before working this project, so I got really lost and had no idea how to compare them. Hope someone can give me some advice. Thanks!
I cannot speak to the specifics of Kaa, so you would need to thoroughly review their documentation. From my understanding, Kaa is mainly focused on the Cloud side of the IoT stack. They provide SDKs for various languages that you need to compile and install on whatever device you intend to connect to the Cloud.
Eclipse Kura is a Java/OSGi framework that runs on an IoT gateway. The framework provides built in services for managing the gateway (networking, cloud connectivity, remote management, etc.) and abstracts away many of the complexities in writing applications for the gateway (GPIO, serial, BLE, etc.). Eclipse Kura doesn't provide a Cloud backend itself, but has built in support for connecting to open source platforms such as Eclipse Kapua and industrial backends such as Eurotech Everyware Cloud, Amazon AWS IoT, Microsoft Azure, etc. In theory you could install the Kaa Java SDK in Eclipse Kura and have Kura connect to Kaa, but I have never tried this.
I hope this helps,
--Dave
Related
I have made a simple project in Corda. My project has 4 nodes including notary and also SpringBoot APIs in the clients folders. I don't know how to deploy my project to the server. I saw the Corda docs but that tutorial was for a single node. So, my question is how to deploy the Corda project with Multiple nodes on the Server and also the SpringBoot APIs. Can anyone help me with this?
There are actually some good youtube videos on this (from me!).
You can find that here: https://www.youtube.com/watch?v=NtVbkUCSt7s
There's other videos there for GCP and Azure as well.
Essentially you need to make sure that your corda node config's p2pAddress specifies the IP address of the machine in your cloud provider of choice.
I am planning to use alfresco. What is the hardware requirement for installing it? Do I need a windows server machine to run? Can I install it in a windows 7 machine?
Your hardware requirements highly depend on your requirements & expected usage (number of documents/transactions, concurrent users etc.)!
You can run Alfresco as in a simple Desktop OS (e.g. Win7). You should have at least 1GB RAM available for Alfresco (that means your machine should have min. 2GB).
To add onto what Alfrescian has posted, I also recommend you review the "Installation" Chapter in the Alfresco One documentation. There you should find information about environment and architecture validation which should provide you information on base hardware needs.
http://docs.alfresco.com/4.2/topic/com.alfresco.enterprise.doc/concepts/ch-install.html
If you plan to run Alfresco in a production environment, I highly recommend you go with Alfresco Enterprise. Deploying Alfresco Enterprise will further constrain what platforms you may use. You can find the support platforms information here: Alfresco Supported Platforms
The supported platforms documentation will give you an idea of what platforms you will need to be able to run deploy Alfresco.
Is there support for a cluster of iis nodes when using SignalR? Or do I need some third party message bus?
Not yet, but they are working on it.
It's planned for the 0.4 release.
When ready, more information will probably be published in the wiki: SignalR and Webfarms on the wiki
Edit2:
Azure, SQL-Server and Redis are implemented.
We just implemented this addon in our application and so far it works flawlessly. It uses a RabbitMq instance to distribute the messages to other servers and is really easy to configure.
https://github.com/mdevilliers/SignalR.RabbitMq
We haven't tried this on a production server yet.
I am developing an application that needs to communicate with a Mobile Operator Messaging Center via CIMD2 protocol. I am trying to find something that has already been implemented, but the only solutions I can find cost around 1000$ US. Can anyone suggest anything?
I found that there is a Linux based program http://www.kannel.org/, and people run it on a linux box and communicate with it from .NET on a Windows box. (might run the linux box on a virtual machine).
You might also want to port the code to C# (there is a JAVA port out there).
In developing software for the Pocket PC platform, I have been happily using the Pocket PC emulator that Microsoft provides with Visual Studio (and as a free download). It provides for much faster develop/deploy/test cycles. (Of course, I do still final testing on real hardware). I have also found that providing the emulator to other folks in the office (e.g. the documentation team) allows them to get accurate screen shots with little effort. So, I'm convinced this is a great tool for my situation.
Here's the concern:
In order to use the networking capabilities of the emulator, one must install Microsoft Virtual PC on the machine that will run the emulator. This seems like an awful heavyweight requirement for such a small tool. Has anyone found a simpler way to enable networking functionality on the Pocket PC emulator?
It's possible to extract the driver required for the Emulator from the Virtual PC 2007 setup file. For Windows 7 users that have Windows Virtual PC installed, this is actually the only known way to get the Emulator working in a network environment (since installing Virtual PC 2007 is not an option once Windows Virtual PC has been installed).
Here's the blog post explaining the procedure. In a nutshell, you extract the VMNetSrv driver from the Virtual PC 2007 SP1 setup file and then manually install this driver on the network adapter you use for Internet connectivity:
BrianPeek.com: Windows Virtual PC and the Microsoft Device Emulator
Simple answer is no, but...
Have you considered using Microsoft's free remote display control from power toys and running your app across ActiveSync. This means that you are using the actual hardware, network comms and all, but with screen, keyboard and mouse reflected to the screen. I find it works a treat.
We went event a step further. We create a solution for building against compact framework and one solution for building against the win32 .net framework. As all code is just C#, there shouldn't be any problems compiling and running the application as Win32 application on the PC.
There is another great benefit - it's much faster to compile for Win32 than for WinCE.
Hope this helps...