Hi Harshani, *What is expected off this project is as follows - *
Like you have correctly understood when a new device needs to be added to the WSO2 IoT Server, a new Device Plugin has to be created. This plugin goes into the IoTServer. When the IoT Server is started it will recognise all the available "Device Plugins" and register the device-type specific to the Device Plugin as a new device in the IoT Server. So if you want a "connected-cup" installed into the server you will have to write a "Device Plugin" for the connected-cup and install it into the IoTServer. *The Device-Plugin (specific to a device-type) has several components to it: * - Plugin component that gets registered to the CDMF via OSGI - Device Management & Controlling APIs written as JAX-RS webapps - UI Components as to how the device-type is listed - Analytics Component - *Device Agent* - etc... Whilst all the above components of the plugin are Java code that goes into the server the "*Device Agent*" is some code written to be *burned/installed/uploaded* into the device hardware in order for it to communicate with the IoT-Server using the proper API's that you have written in the other components. This agent can be in different languages according to the device. Ex: *Arduino - Arduino C (an abstraction on top of C/C++)* *RaspberryPi - Python, Java, C* *ESP8266 - Lua* So what we basically expect off this project is to specifically focus on making the experience of writing the "*Device Agent*", of the plugin easy for an end user. So the SDK should ideally have implementations of the complex bits of communicating to the server (using languages such as C, C++, java, python) which can be utilised by the Device-Agent writer. Hope this helps. Regards ------------------------------------- *Shabir Mohamed* *Software Engineer* WSO2 Inc.; http://wso2.com Email: sha...@wso2.com <ayy...@wso2.com> Mobile: +94 77 3516019 | +94 71 6583393 > > Hi all, > I successfully build carbon-apimgt, uuf-template-app, > carbon-device-mgt, carbon-device-mgt-plugins and all the repositories are > in correct branch. But when I try to build the product-iot-server I got the > error "The command line is too long". When I searched for the error I > realized this error may be because I'm using Windows 10. I decided to build > the WSO2 IoT Server after installing Linux. > > Since I'm getting errors and there's only few more days for > the deadline for proposals, I started working on my project proposal. For > this I need to get confirm whether my understanding on this project is > correct and I also need to know the scope of the project. > As I understood I should build an SDK for IOT - Device > specific agents to connect to the IoT Server using languages such as C, > C++, java, python. That SDK should have special feature such as hide the > complexities of communicating authentication, encryption with the IoT > Server, abstract the protocol complexities and should be easily portable > for different hardware. > when I went through the documentation on WSO2 IoT Server > <https://docs.wso2.com/display/IoTS100/About+IoT+Server> I realized that > when a new device is connected to the IoT Server, need to write device > plugins for each device as each device type requires their own device > plugin in WSO2 IoT Server. As I understood the IoT SDK that I'm going to > build, should perform all these tasks when a new device is connected to the > IoT Server. > I would be grateful if you could provide me the necessary > details. > > Thank you. > > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
