WISE-PaaS/RMM Server - Revision history

Matt.lin at 09:08, 31 August 2017

2017-08-31T09:08:02Z

Matt.lin: renew RMM Server UM

2017-08-11T06:00:58Z

renew RMM Server UM

Matt.lin at 01:41, 27 July 2017

2017-07-27T01:41:51Z

Matt.lin at 03:57, 18 July 2017

2017-07-18T03:57:14Z

Matt.lin at 06:15, 1 March 2017

2017-03-01T06:15:45Z

Dylan.chang at 08:38, 5 October 2016

2016-10-05T08:38:10Z

Sephiroth.wang: /* Architecture */

2016-05-31T08:43:26Z

‎Architecture

Sephiroth.wang: /* Architecture */

2016-05-31T08:39:48Z

‎Architecture

Sephiroth.wang: /* Introduction */

2016-05-31T08:27:16Z

‎Introduction

Sephiroth.wang: /* Introduction */

2016-05-31T08:25:36Z

‎Introduction

@@ Line 23: / Line 23: @@
 == Document ==
-*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.5.pdf|''RMM 3.2 Server User Manual (pdf)'']]
+*[[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)'']]

@@ Line 23: / Line 23: @@
 == Document ==
-*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.3.pdf|''RMM 3.2 Server User Manual (pdf)'']]
+*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.5.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)'']]

@@ Line 23: / Line 23: @@
 == Document ==
-*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.2.pdf|''RMM 3.2 Server User Manual (pdf)'']]
+*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.3.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)'']]

@@ Line 23: / Line 23: @@
 == Document ==
-*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.1.pdf|''RMM 3.2 Server User Manual (pdf)'']]
+*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.2.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)'']]

@@ Line 23: / Line 23: @@
 == Document ==
-*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.0.pdf|''RMM 3.2 Server User Manual (pdf)'']]
+*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.1.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)'']]

@@ Line 21: / Line 21: @@
 *[[RMM Dashboard Builder|Dashboard Builder]]
-==Document==
+== Document ==
-*[[Media:WISE-PaaS_RMM_3.1_Server_UM_V1.5.pdf ‎|''RMM 3.1 Server User Manual (pdf)'']]
-*[[Media:WISE-PaaS_RMM_3.1_REST_API_DG_V2.1.pdf ‎|''RMM 3.1 REST API Developer Guide (pdf)'']]
+*[[Media:WISE-PaaS_RMM_3.2_Server_UM_V1.0.pdf|''RMM 3.2 Server User Manual (pdf)'']]

@@ Line 12: / Line 12: @@
 ==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 Rabbit MQ. 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.
+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.
+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]]

← Older revision		Revision as of 08:39, 31 May 2016
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 Rabbit MQ. 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.
		+
		+	[[File:WISE-PaaS RMM Structure.png\|800px]]

	==Dashboard==		==Dashboard==

@@ Line 7: / Line 7: @@
 In addition, provide several [https://en.wikipedia.org/wiki/Representational_state_transfer 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, [https://en.wikipedia.org/wiki/ZeroMQ ZeroMQ], and [[RabbitMQ|https://en.wikipedia.org/wiki/RabbitMQ]].
+Leverage latest technology and open source project to achieve these goals. For instance, [https://en.wikipedia.org/wiki/ZeroMQ ZeroMQ], and [https://en.wikipedia.org/wiki/RabbitMQ RabbitMQ].
 On the database part, adopt [https://en.wikipedia.org/wiki/PostgreSQL PostgreSQL] to process related data, and [https://en.wikipedia.org/wiki/MongoDB MongoDB] for sensor store/calculate.

← Older revision		Revision as of 08:25, 31 May 2016
Line 1:		Line 1:

	==Introduction==		==Introduction==
		+	The WISE-PaaS/RMM Server centralizes management of each device/gateway/sensor, through [https://en.wikipedia.org/wiki/MQTT 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 [https://en.wikipedia.org/wiki/Virtual_Network_Computing VNC Server]), power control, protection (via McAfee), recovery (via Acronis) and so on.
		+
		+	In addition, provide several [https://en.wikipedia.org/wiki/Representational_state_transfer 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, [https://en.wikipedia.org/wiki/ZeroMQ ZeroMQ], and [[RabbitMQ\|https://en.wikipedia.org/wiki/RabbitMQ]].
		+	On the database part, adopt [https://en.wikipedia.org/wiki/PostgreSQL PostgreSQL] to process related data, and [https://en.wikipedia.org/wiki/MongoDB MongoDB] for sensor store/calculate.

	==Architecture==		==Architecture==