Difference between revisions of "WISE-PaaS/RMM Server"
(→Architecture) |
|||
(6 intermediate revisions by 3 users not shown) | |||
Line 12: | Line 12: | ||
==Architecture== | ==Architecture== | ||
− | In order to manage lots of device and sensors. The single machine cannot have much more capability, therefore parallel extension and load balancing that we focus. Adopt a different open source project and technology to deal with these problems. Such as ZeroMQ and | + | In order to manage lots of device and sensors. The single machine cannot have much more capability, therefore parallel extension and load balancing that we focus. Adopt a different open source project and technology to deal with these problems. Such as ZeroMQ and RabbitMQ. We have 3 layers for server structure, web, server and message brokers, each layer support parallel extension. The blue diagram like a virtual machine, work independently. |
− | Currently use | + | Currently use PostgreSQL for relation database and MongoDB on sensor data store/calculate Next, integrated public cloud (DocumentDB/Hbase) is planning to solve storage problems, due to huge sensor raw data. Furthermore, advanced data analytic and predict on machine learning. |
[[File:WISE-PaaS RMM Structure.png|800px]] | [[File:WISE-PaaS RMM Structure.png|800px]] | ||
Line 21: | Line 21: | ||
*[[RMM Dashboard Builder|Dashboard Builder]] | *[[RMM Dashboard Builder|Dashboard Builder]] | ||
− | ==Document== | + | == Document == |
− | *[[Media:WISE-PaaS_RMM_3. | + | |
− | *[[Media:WISE-PaaS_RMM_3. | + | *[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.6.pdf|''RMM 3.2 Server User Manual (pdf)'']] |
+ | *[[Media:WISE-PaaS_RMM_3.2_REST_API_DG_V1.0.pdf|''RMM 3.2 REST API Developer Guide (pdf)'']] |
Latest revision as of 11:08, 31 August 2017
Introduction
The WISE-PaaS/RMM Server centralizes management of each device/gateway/sensor, through MQTT 3-way handshake protocol for communication. Not only remote control these devices, but collect and analytics each sensor information. The remote features including terminal, screenshot, remote KVM (via VNC Server), power control, protection (via McAfee), recovery (via Acronis) and so on.
In addition, provide several Restful APIs (more than 140+) for application/UI to integrate. More than 500 million devices will be added to the expanding IoT during 2016. Therefore the cluster server/dynamic load balancing designed is required. Leverage latest technology and open source project to achieve these goals. For instance, ZeroMQ, and RabbitMQ. On the database part, adopt PostgreSQL to process related data, and MongoDB for sensor store/calculate.
Architecture
In order to manage lots of device and sensors. The single machine cannot have much more capability, therefore parallel extension and load balancing that we focus. Adopt a different open source project and technology to deal with these problems. Such as ZeroMQ and RabbitMQ. We have 3 layers for server structure, web, server and message brokers, each layer support parallel extension. The blue diagram like a virtual machine, work independently.
Currently use PostgreSQL for relation database and MongoDB on sensor data store/calculate Next, integrated public cloud (DocumentDB/Hbase) is planning to solve storage problems, due to huge sensor raw data. Furthermore, advanced data analytic and predict on machine learning.