...
Parameter Name | Description | Required | Possible Values |
---|---|---|---|
mqtt.server.host.name | The name of the host. | Yes | A valid host name |
mqtt.server.port | The port ID. | Yes | 1883 ,1885 |
mqtt.client.id | The client ID. | Yes | A valid client ID |
mqtt.topic.name | The name of the topic | Yes | A valid topic name |
mqtt.subscription.qos | The QoS value. | No |
|
mqtt.session.clean | Whether session clean should be enabled or not. | No | true , false |
mqtt.ssl.enable | Whether ssl should be enabled or not. | No | true , false |
mqtt.subscription.username | The username for the subscription. | No | A valid user name |
mqtt.subscription.password | The password for the subscription. | No | A valid password |
mqtt.temporary.store.directory | The path of the directory to be used as the persistent data store for quality of service purposes. | No | A valid local path. The default value is the ESB temp path. |
mqtt.blocking.sender | Whether blocking sender should be enabled or not. | No | true , false |
mqtt.content.type | The content type. | No | A valid content type. the default content type is text/plain . |
mqtt.message.retained | Whether the message should be retained or not. This parameter can be used only in the transport sender. | No |
|
For a sample that demonstrates how Axis2 publishes a message on a particular topic, and how an MQTT client subscribed to that topic receives it, seeĀ Sample 272:Publishing and Subscribing using WSO2 ESB's MQ Telemetry Transport.