WSO2 Message Broker (WSO2 MB) uses two transport protocols for the purpose of brokering messages between publishers and subscribers. These protocols are the Advanced Message Queueing Protocol (AMQP) and the Message Queueing and Telemetry Transport (MQTT).
...
- Setting the
enabled="true"attribute ensures that SSL is enabled by default when the MB server is started.Theport="8672"attribute sets 8672 as the default SSL listener port for messages/command sent via the relevant transport. The
<keyStore>and <trustStore> element specifies the details of the keystore and trustore used. Note that, by default, the keystore configuration points to the default keystore and truststore that is shipped with the product. The location, password and certType elements are explained below.Parameter Description location The location where the keystoreused for securing SSL connections is stored. By defaultthis is the default keystore(
wso2carbon.jks) that is shipped with WSO2 MB.Note Note that this should always be a keystorecreatedfor keystore created for the super tenant. Find out more about setting up keystores for your MB server.
password The password oftheof the keystore. certType
Related Parameters
...
Message Queueing and Telemetry Transport
The Message Queueing and Telemetry Transport (MQTT) is a lightweight, broker-based publish/subscribe messaging protocol, which enables an extremely lightweight publish/subscribe messaging model. WSO2 MB 3.0.0 and later versions fully support MQTT version 3.1.0, and partially supports version 3.1.1.
The MQTT protocol allows a message to be sent to a topic based on three levels of QoS (Quality of Service) as explained below.
...