When you are deploying the Edge MQTT application to a site, you must specify how to access the MQTT broker by setting the following parameters.
- MQTT port: Port to use for accessing the MQTT broker.
- MQTT service name: Service name for accessing the MQTT broker.
- MQTT over Websocket port: Port to use for accessing the MQTT broker over WebSocket protocol.
- Ports mode: Specifies how the broker service is accessible.
- node-port: Exposes the Service on each Node’s IP at a static port from range 30000-32768.
- host-port: Opens a port on the node on which the pod is running.
- Persistence: If enabled, Edge MQTT buffers the messages to disk (otherwise, the messages are buffered in memory).
- Enable monitoring: If you have enabled monitoring for the site (see Configure site), you can enable application monitoring to collect metrics about the performance of your deployment. For details on accessing the collected metrics, see Observing Great Bear.
- MQTTS Bridge hostname:port: The address of the MQTT broker to send the messages to in hostname:port format.
- Bridge username: The username used to authenticate on the MQTT broker.
- Bridge token: The authentication token that Edge MQTT uses to access the broker. Make sure that it provides write access.
- Skip server certificate validation: Do not validate server certificate of MQTTS bridge in order to allow connections to your own MQTT bridge over TLS
If the Edge MQTT app is deployed without the MQTTS Bridge parameter defined, then the app runs as a standard MQTT message broker at the edge.