1.modbus Protocol
Analysis: temperature and humidity sensors.
2. MQTT-SN
resolve: MQTT UDP-based version.
3.EMQ
resolve: EMQ is a distributed one million things MQTT open source messaging server.
4.EMQ service port
resolved:
[. 1] 1883: the MQTT protocol port
[2] 8883: MQTT / SSL ports
[3] 8083: MQTT / WebSocket port
[4] 8080: HTTP API port
[5] 18083: Dashboard Management Console port
5.EMQ back-end Web console
resolve: EMQ provides a back-end Web console, users can through the Web console, view the server running, statistical data, the client [Client], the session [Session], the theme [Topic] , subscription [subscription], plug [plugin].
[1] access to the address: http: // server IP: 18083
[2] default user name: ADMIN
[3] default password: public
6.Portainer
resolved:
[1] Portainer is a lightweight graphical management tool, which allows you to easily manage Docker different environment. Portainer deployment and use are very simple, it can run on any Docker engine consists of a container components.
[2] Portainer function is very comprehensive, providing state of the display panel, application templates for rapid deployment, container mirrored the basic operation of the network data volumes [including uploading and downloading images, create operational containers], event log shows, containers console operator, Swarm and clusters centralized management and operation services, user login management and control functions. Basically meet all the needs of small and medium units for container management.
7.MQTTBox
resolve: MQTTBox can be both a publisher message may also be a subscriber of the message.
8.Device Profile
Analysis:
[1] a portion of the apparatus is how to read from the data
[2] is another portion of the command control apparatus
9.consul
resolved: consul service registration and discovery is the key to dynamic stretching of micro-services architecture system, while the system is deployed it should be the first service to be launched.
10.Core-Metadata
Analysis: mainly Edgex micro-system equipment and service devices and device data associated metadata management, a total of nine major interfaces, namely: Schedule, Schedule Event, Device, Device Report, Provison Watcher, Device Service, Device Profile, Addressable, Command.
11.Device Services
Analysis: Micro service is the only device users need a device according to the physical interface protocol to develop their own micro-service official has provided Device Service SDK, the user can use several interfaces and to achieve a specific device data structure can be.
A mounting device 12.
Analysis: need to register the device profile, the device configuration register corresponding to the micro-service register associated Addressable, the Schedule register, register Schedule Event, and these generally involve registrars different micro service.
13.config-seed
resolve: config-seed upload service configuration parameters of all micro-services and other services, the program runs only once before EdgeX system deployment.
14.docker-compose up -d consul
解析：Start the configuration and registry microservice which all services must register with and get their configuration from
15.docker-compose up -d config-seed
解析：Populate the configuration/registry microservice
16.docker-compose up -d mongo
解析：Start the NoSQL MongoDB container
17.docker-compose up -d logging
解析：Start the logging microservice - used by all micro services that make log entries
18.docker-compose up -d notifications
解析：Start the notifications and alerts microservice–used by many of the microservices
19.docker-compose up -d metadata
解析：Start the Core Metadata microservice
20.docker-compose up -d data
解析：Start the Core Data microservice
21.docker-compose up -d command
解析：Start the Core Command microservice
22.docker-compose up -d scheduler
解析：Start the scheduling microservice -used by many of the microservices
23.docker-compose up -d export-client
解析：Start the Export Client registration microservice
24.docker-compose up -d export-distro
解析：Start the Export Distribution microservice
25.EdgeX Foundry microservices
解析：
| EdgeX Foundry Microservice | Docker Compose Container | Container Name | Port | Ping URL |
|---|---|---|---|---|
| Core Command | command | edgex-core-command | 48082 | http://[host]:48082/api/v1/ping |
| Core Data | data | edgex-core-data | 48080 | http://[host]:48080/api/v1/ping |
| Core Metadata | metadata | edgex-core-metadata | 48081 | http://[host]:48081/api/v1/ping |
| Export Client | export-client | edgex-export-client | 48071 | http://[host]:48071/api/v1/ping |
| Export Distribution | export-distro | edgex-export-distro | 48070 | http://[host]:48070/api/v1/ping |
| Rules Engine | rulesengine | edgex-support-rulesengine | 48075 | http://[host]:48075/api/v1/ping |
| Support Logging | logging | edgex-support-logging | 48061 | http://[host]:48061/api/v1/ping |
| Support Notifications | notifications | edgex-support-notifications | 48060 | http://[host]:48060/api/v1/ping |
| Support Scheduler | scheduler | edgex-support-scheduler | 48085 | http://[host]:48085/api/v1/ping |
| Virtual Device Service | device-virtual | edgex-device-virtual | 49990 | http://[host]:49990/api/v1/ping |
参考文献：
[1]EdgeX Foundry Documentation：https://docs.edgexfoundry.org/2.0/getting-started/Ch-GettingStartedUsers/
