System operation
Basic operation
This section mainly introduces the basic operations of the community correction monitoring system. The common operations of users are: login, change password, customize group, and exit.
Login system
Login with username and password
§ Click the login button on the right side of the system login interface to expand the login window.
§ The user should enter the correct user name and the matching password, and then click the login button to log in to the community correction system (the user name and the initial password will be assigned by the system administrator);
Prompt: if you enter the error, the system will prompt "user name or password is wrong", you can ask the administrator to reset the password;
When the user logs in successfully, the homepage interface is shown as follows:
The interface layout of the home page is explained in the following table:
Advanced query, enter user name and click to query user status
Track playback and real-time tracking
Click to enter track playback as shown below
Enter the user name to view, you can choose to view time
1-4 times faster playback
Click to enter real-time tracking
Enter the page as shown below
Enter a user name to view the trace object
Details of the alarm
Click to enter warning details as shown below
You can view alarm time alarm level and alarm type
Check after the query processing
Query time is optional
The alarm state can be handled by itself
Click the user name and click the "password change" button. The user can enter the original password and the new password in the new password change window, and then click the "confirm" button to change the password.
Select log out to log out.
The management end
Background management is divided into two modules a basic information maintenance and system management
After logging into the system, the user clicks the button to the left of the user's avatar to enter the background management
When the user enters the background management, the default home page is statistics. The system user can conduct basic statistics on the data through this module, which is divided into three parts: alarm level, alarm type, and user online.
Select view time
Check the past time
management
Click the administration button in the left menu bar to expand the administration list.From this list, you can manage the monitoring objects, devices, and fences.
new
When you have new device information to add to the system, you can click
Each item is followed by a red * item;
Monitor object maintenance
Click to view
Modify object information select one line for modification, delete object select one line for operation device binding fence binding click to view user details
Management of the fence
Enter the name of the fence and the type of fence. Finally, select the organization to which you belong and delete the fence
Advanced query, enter user name to query, view details button, click to view fence details
Log management
Count user log-in logs
Rights management
Enter the permissions add list
User management
Add user with * required to fill in ok key end, user modification, user authorization, delete user batch delete.
And reset the password.
The alarm set
In order to ensure the normal installation and stable operation of IOT cloud platform, the server configuration information is specifically described as follows:
The serial number | memory | The hard disk | The CPU | Device access | Save the data |
1 | The 32 gb | 500 g | Eight core | < = 500 | Data: <=1 year;Log: last 3month |
Single version deployment: single version services are deployed on a server, for data security and high performance can not be fully guaranteed, it is recommended to use in testing, demonstration and other environments.
The serial number | role | The Numbers | The CPU | memory | The hard disk | Device access | Save the data |
1 | Data storage service | 3 | Eight nuclear | 32 gb | 2 TB | < = 5000 | Data: <=1 year Log: last 3month |
2 | Data acquisition service | 2 | Eight nuclear | 32 gb | 500 gb | ||
3 | Data analysis service | 3 | Eight nuclear | 32 gb | 500 gb | ||
4 | Message service | 3 | 4 nuclear | 16 gb | 500 gb | ||
5 | The WEB service | 2 | 4 nuclear | 16 gb | 300 gb | ||
6 | A total of | 13 | 84 nuclear | 128 gb | 10.5 TB |
Cluster version deployment: the cluster version of each server component is deployed in high-availability mode, as follows:
(1) data storage service: the data is stored in the form of two copies on three storage servers, which can support the normal operation of any one of the three servers. After the shutdown service is started, it can normally join the cluster and run again.
(2) data acquisition service: the data acquisition service is used for real-time acquisition of device data, and it is the entrance to the device access platform. The data acquisition service is highly available and deployed on two servers. It supports the normal operation of any one of the two servers.
(3) data analysis service: the data analysis service is mainly used for real-time data analysis of mass data of equipment, and it is the computing center of the entire platform, including electronic fence alarm and overspeed alarm.The data analysis is deployed in 3 copies on 3 servers. The 3 servers support traffic sharing and elastic scaling. In the worst case, 2 servers in 3 servers are down and can run normally.
(4) message service: message service is the message center of platform data, which is used for real-time message transmission of device data. It supports 3 servers to go down and 1 server to run normally.
(5) WEB services: WEB services are management systems that users can see, which are used for device access, device status monitoring, device trajectory query, device alarm analysis, device statistics and other functions.
To ensure the installation, operation and normal use of IOT cloud platform. Now the operating system version number database version number to do the following:
The serial number | Service list | The version number | instructions |
1 | CentOS - 7-1611 | Development version 1611 | Operating system development version |
2 | Zookeeper | 3.4.9 | Coordinator, configuration center |
3 | Kafka | 2.10 | The message center |
3 | Redis | 3.2.3 | In-memory database |
4 | Postgresql | 9.3 | Relational database |
6 | Cassandra | 3.10 | Big data storage |
7 | Telnet | 0.17 | Service port listening |
8 | Python | 3.5.4 | Service monitoring and boot up |
9 | Nginx | 1.16 | Front segment WEB server |
10 | Tomcat | 8.0 | Background WEB service |
To ensure the installation, operation and normal use of IOT cloud platform. The service port involved and its communication protocol are described as follows:
The serial number | The service name | port | Communication protocol | instructions |
3 | zookeeper | 2181 | TCP/IP | Coordinator, configuration center |
4 | Kafka | 9092 | TCP/IP | The message center |
5 | redis | 6379 | TCP/IP | In-memory database |
6 | psotgresql | 5432 | TCP/IP | Relational database |
7 | Cassandra | 9042 | TCP/IP | Big data storage |
9 | zkui | 9000 | The HTTP | Zookeeper management tool |
10 | KafkaOffsetMonitor | 9001 | The HTTP | Kafka monitoring tools |
11 | CBasicService | 8001 | The HTTP | Basic services |
12 | CCoreService | 8002 | The HTTP | Core services |
13 | CIOV2Service | 8009 | The HTTP | IOV service |
14 | CIOV2Analyser | 8008 | The HTTP | IOV data analysis |
15 | CIOV2Collector | 8005 8006 8007 | TCP/IP | IOV data acquisition |
16 | Nginx | 8000 | TCP/IP | WEB front-end service |
17 | Tomcat | 8080 | TCP/IP | WEB back-end services |
1. The system adopts device login and uniform authorization mechanism to prevent the connection of malicious devices.
2. The system USES the Netty asynchronous framework to stabilize the access device.
3. The system API USES the uniform authorization way, the way arbitrary user access interface.
4. The system provides an API interface update mechanism to prevent password leakage.
5. The system provides service detection and automatic recovery.
6. The system adopts data master - slave mutual backup to ensure data security in real time.
1. Robustness, also known as robustness or solidity of a system, is a measure of a system's ability to recover from various error conditions.
2. From the perspective of design or coding structure, the system adopts the company's unified coding standard, and adopts micro-service equipment to ensure the decoupling and stability of the system.
3. The system interface adopts unified specification development, exception unified handling and method interception, providing system fault tolerance rate.
4. The system provides service detection and recovery to detect and repair problems in a timely manner.
5. The system data is stored in the main and standby mode, and can be recovered directly from the standby server in the case of down machine or disk failure in the main machine room, which improves the security.
The system adopts the data backup mechanism to backup the data from the master server to the standby server in real time. When the master server's data changes