AMQP SSL

review the amqp ssl integration guide docid\ ifrkcddjvibprbl8e4xk7 overview amqp ssl integration enables an edge system to connect with an amqp broker using ssl authentication supported versions supports rabbitmq versions starting with 2 0 but primarily tested against recent 3 x releases some features and behaviors may be server version specific supported communication outbound (publish data from edge to amqp broker) yes inbound (subscribe data from amqp broker to edge) no configurations true false 179false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type exchange options exchange names starting with "amq " are reserved for pre declared and standardized exchanges the client may declare an exchange starting with "amq " if the passive option is set, or the exchange already exists names can consist of a non empty sequence of letters, digits, hyphen, underscore, period, or colon each exchange belongs to one of a set of exchange kinds/types implemented by the server the exchange types define the functionality of the exchange i e how messages are routed through it once an exchange is declared, its type cannot be changed the common types are "direct", "fanout", "topic" and "headers" durable and non auto deleted exchanges survive server restarts and remain declared when there are no remaining bindings these selections are best for long lived exchange configurations like stable routes and default exchanges non durable and auto deleted exchanges are deleted when there are no remaining bindings and not restored on server restart these selections are useful for temporary topologies that should not pollute the virtual host on failure or after the consumers have completed non durable and non auto deleted exchanges remain while the server is running, including when there are no remaining bindings these selections are useful for temporary topologies that may have long delays between bindings durable and auto deleted exchanges survive server restarts and are removed before and after server restarts when there are no remaining bindings these selections are useful for robust temporary topologies or when you require binding durable queues to auto deleted exchanges note rabbitmq declares the default exchange types like 'amq fanout' as durable, so queues that bind to these pre declared exchanges must also be durable exchanges declared as internal do not accept publishing internal exchanges are useful when you wish to implement inter exchange topologies that should not be exposed to users of the broker when no wait is selected, you can continue without waiting for a confirmation from the server the channel may be closed because of an error add a notifyclose listener to respond to any exceptions compatibility validation this information is just for reference more products and versions may be supported provided they are compatible with the supported version as mentioned above true false 135,148false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type