Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WSO2 Message Broker (WSO2 MB) uses two transport protocols for the purpose of The Message Broker profile of WSO2 EI uses Advanced Message Queueing Protocol (AMQP) as the transport protocol for brokering messages between publishers and subscribers. These protocols are the Advanced The Advance Message Queueing Protocol (AMQP) and the Message Queueing and Telemetry Transport (MQTT)is a wire-level messaging protocol used by the broker for message queueing.

The topics given below explains explain how these protocols are enabled and configured for WSO2 MBthe EI Message Broker profile:

Table of Contents

Advanced Message Queuing Protocol (AMQP)

The Advance Message Queueing Protocol (AMQP) is a wire-level messaging protocol used by WSO2 MB for message queueing.

Enabling the transport

The <MB<EI_HOME>/repositorywso2/broker/conf/broker.xml file contains parameters related to configuring the AMQP transport. The transport can be enabled as shown in the following extract of the broker.xml file:

Code Block
languagexml
<amqp enabled="true">
	<!-- most of the amqp configurations reside in qpid-config.xml since we inherit the qpid messaging model during AMQP.-->
	<port>5672</port>
	<sslPort>8672</sslPort>
	<maximumRedeliveryAttempts>10</maximumRedeliveryAttempts>
	<allowSharedTopicSubscriptions>false</allowSharedTopicSubscriptions>
    <allowStrictNameValidation>true</allowStrictNameValidation>
</amqp>

Related Parameters

Parameter NameDescriptionDefault Value
enabledIf the value of this parameter is true, the AMQP transport is enabled and the AMQP protocol will be applied to messages sent to the specified listening port.true
portThe listening port specified for the AMQP transport. The AMQP broker would be initialized with this port by default.5672
sslPortThe listening SSL port for the specified AMQP transport. The AMQP security socket will be initialized with this port by default. 8672
maximumRedeliveryAttemptsThe maximum number of times the WSO2 MB broker should attempt to redeliver a message that has not reached a subscriber. For example, when this value is set to 10, another 10 attempts will be made to deliver the message. The default value can be changed depending on your reliability requirements.10
allowSharedTopicSubscriptionsIf this parameter is true, a durable subscription to a topic can be shared among multiple subscribers. That is, multiple clients can subscribe to a topic in WSO2 MB the broker using the same client ID. Read more about durable subscriptions to topics.false
allowStrictNameValidation
If this parameter is true, the queue names and topic names will be validated according to the AMQP specification. When this parameter is set to false, it is possible to use ":" in topic names.
true

Refer the description of the broker.xml file for further details.

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.

QoS 1 - At Most One - At this level, messages are delivered to subscribers in the most efficient manner. A message is dispatched only once.

QoS 2 - At Least One - At this level, the system will ensure that a message is received by the subscriber at least once. The level of delivery is assured through acknowledged delivery.

QoS 3 - Exactly Once - At this level, the message is delivered only once to its subscriber. This level is also defined as Assured Delivery.

Enabling the transport

The <MB_HOME>/repository/conf/broker.xml file contains parameters related to configuring the MQTT transport. The transport can be enabled as shown in the following extract of the broker.xml file.

Code Block
languagexml
<mqtt enabled="true">
	<port>1883</port>
	<sslPort>8883</sslPort> <!-- put proper default ssl port -->
    <inboundBufferSize>32768</inboundBufferSize>
    <deliveryBufferSize>32768</deliveryBufferSize>
    <security>
             <authentication>OPTIONAL</authentication>
             <authenticator>org.wso2.carbon.andes.authentication.andes.CarbonBasedMQTTAuthenticator</authenticator>
    </security>
</mqtt>

Related Parameters

If the value for this parameter is true, the MQTT transport is enabled and the MQTT protocol will be applied to messages that are sent to the specified listening port
Parameter NameDescriptionDefault Value
enabled
.
true
portThe listening port for the MQTT transport. The MQTT broker will be initialized with the specified port by default. This value would be incremented based on the offset specified in the carbon.xml.1883
sslPortThe listening SSL port for the MQTT transport. The MQTT secure socket will be initialized with the specified port by default.8883

...