AMQP TCP Integration Guide

review the following guide for setting up an integration between litmus edge and an amqp broker before you begin you will need access to an amqp tcp broker refer to the following to learn more downloading and installing rabbitmq server operator documentation step 1 add a device follow the steps to connect a device docid 3eyafppweuvmblcey17sq the device will be used to store tags that will be eventually used to create outbound topics in the connector make sure to select the enable data store checkbox step 2 add tags after connecting the device in litmus edge, you can add tags docid 8se7z3pmrfwl1nmzcwalx to the device create tags that you want to use to create outbound topics for the connector step 3 add the amqp tcp connector follow the steps to add a connector docid\ ogw7fkqbwidbabn4wl5rr and select the amqp tcp provider note for configuring exchange options, see amqp tcp docid\ zacjrfl k7hap5tsz7a3k and refer to the exchange options section to learn more enter the details for the connector name enter a name for the connector hostname enter the ip address for the amqp broker port enter the port number for the amqp broker the default value is 5671 virtual host (optional) enter the virtual host path, which specifies the namespace for permissions, exchanges, queues, and bindings on the server username (optional) enter the username for authentication with the amqp broker the default value is guest password (optional) enter the password for authentication with the amqp broker the default value is guest exchange (optional) enter the northbound (third party) topic to publish to through the connector exchangetype select the exchange type (direct, fanout, topic, x custom) exchange durable select the checkbox to allow the exchange to survive restarts exchange auto delete select the checkbox to make the server no longer remain declared when there are no remaining bindings exchange internal select the checkbox to enable the internal flag exchange no wait select the checkbox to instruct the exchange to not wait for a response routing key the amqp routing key that the exchange might use to determine how to route messages to the queue iso8601 timestamp select this checkbox to convert message timestamps to the iso8601 format before sending throttling limit (optional) the maximum number of messages per second to be processed the default value is zero, which means that there is no limit persistent storage when enabled, this will cause messages to undergo a store and forward procedure messages will be stored within litmus edge when cloud providers are online queue mode select the queue mode as lifo (last in first out) or fifo (first in first out) selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first step 4 enable the connector after adding the connector, click the toggle in the connector tile to enable it if you see a failed status, you can review the manage connectors docid 3u7jzldinehy8shvifd d and relevant error messages step 5 create topics for connector you will now need to create outbound topics for the connector from the tags created in step 2 to create outbound topics click the connector tile the connector dashboard appears click the topics tab click the import from devicehub tags icon the devicehub import dialog box appears after adding all required topics, navigate to the integration overview page and ensure the connector is not disabled and still shows a connected status step 6 enable topics ensure the topics you imported are enabled by returning to the topics tab and clicking the enable all topics icon step 7 verify successful connection access the amqp broker and ensure that data is being sent from litmus edge to the broker