|High Availability||Upgrade SwiftMQ HA Router without disruption|
|Tomcat||SwiftMQ/Tomcat 5.5, 6, 7|
|JCA Resource Adapter||SwiftMQ 7.0.1/Glassfish V2|
|JCA Resource Adapter||SwiftMQ 6.2.0/JBoss 4.0.4|
|JCA Resource Adapter||SwiftMQ 9.x/JBoss 7.x|
|JCA Resource Adapter||SwiftMQ 6.x/JOnAS 4.7.6|
|JCA Resource Adapter||SwiftMQ 5.x/IBM WebSphere 6.0 IntraVM|
|JMS XA/ASF||SwiftMQ 4.x/IBM WebSphere 5.0 IntraVM|
|JMS XA/ASF||SwiftMQ 4.x/JOnAS 2.6 IntraVM|
|JMS XA/ASF||SwiftMQ 4.x/JBoss 3.0.3 IntraVM|
|JMS/Routing||Transfering very large Messages|
|JMS Scalability||Serving many JMS Connections|
|JMS Pooling||JMS Pooling for Spring's JmsTemplate and plain JMS|
|JMS/JNDI||Enabling transparent Reconnect in SwiftMQ Universal Router|
|JMS Bridge||JMS Bridge SwiftMQ/WebsphereMQ 5.3|
|JMS Bridge||JMS Bridge SwiftMQ/Weblogic 8.1 JMS|
|JNDI||Using SwiftMQ's File System Context JNDI Provider|
|JNDI||JNDI Replication into a LDAP Server|
|JNDI||JNDI Replication into JBoss' JNDI|
|Portmapper||VPN (Telnet/JDBC) over SwiftMQ Universal Router Netwoks|
|Replicator||File Replication over SwiftMQ Universal Router Netwoks|
|Windows Service||Installing SwiftMQ Universal Router as a Windows Service|
|Windows Service||Installing SwiftMQ HA Router as a Windows Service|
|Interop||Access SwiftMQ with the Stomp Protocol|
|Swiftlet API||Swiftlet debug with JRebel (thanks to Andy Barlow)|
|AMQP 1.0||AMQP 1.0 plugins for logstash|
|AMQP 1.0||AMQP 1.0 test suite|
|AMQP 1.0||SwiftMQ AMQP 1.0 Client with Windows Azure Service Bus|
|AMQP 1.0||Microsoft ServiceBus .Net Client with SwiftMQ over AMQP 1.0|
|AMQP 1.0||SwiftMQ AMQP 1.0 Client with Apache Qpid C++ Broker and SASL EXTERNAL|
|Performance||SwiftMQ Performance Profile, 8.1.0 vs 8.0.0|
|Tuning||SwiftMQ Tuning Guide|
Enterprise Integration Patterns provides top notch messaging patterns and is a "must read" for messaging software architects!
For free help or assistance concerning SwiftMQ, visit the SwiftMQ User Forum.
IIT provides technical support as well. To use technical support, you have to purchase a support incident. Please consult the support section for further information.
To report a SwiftMQ bug, please send an eMail to firstname.lastname@example.org. Use code snippets/attach small programs that we can reconstruct it, please.
We appreciate your feedback or feature request very much. Please send it to email@example.com. We will seriously read and proof every post and file it as feature request or bug, if necessary. Please note that this might take some time and an answer isn't guaranteed. In case you need assistance, please post a message to the SwiftMQ User Forum or use our technical support.