Configuring Transports for the Broker

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

The topics below explain how these protocols are enabled and configured for the EI Message Broker profile:

Enabling the transport

The <EI_HOME>/wso2/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:

<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 Name	Description	Default Value
enabled	If 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
port	The listening port specified for the AMQP transport. The AMQP broker would be initialized with this port by default.	5672
sslPort	The listening SSL port for the specified AMQP transport. The AMQP security socket will be initialized with this port by default.	8672
maximumRedeliveryAttempts	The maximum number of times the 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
allowSharedTopicSubscriptions	If 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 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