JMS Addressing
JMS Vendor Suppport - which JMS implementations are compatible with MagooClient?
The MagooClient JMS transport architecture is designed to allow any compliant JMS provider to be used with MagooClient. When configuring a JMS transport, you will only need to provide details of the required JAR files and JNDI properties. Note that due to licensing restrictions, MagooClient does not ship with JMS client libraries - you will need to obtain these from the JMS vendor and install them separately. Dynamic class-loading however will allow you to hot-configure the JMS Client JARs from your JMS client installation without needing to modify the MagooClient classpath. Multiple JMS transports can be configured in parallel.
MagooClient has been tested against the following JMS products:
- IBM WebSphere MQ V5.3/6.0
- Sun ONE Message Queue V3.x
- Weblogic JMS V8.1/V9.2
- JBossMQ V4.x
- Sonic MQ V6.1/7.0/7.5
- Tibco EMS V4.3
For each of these, pre-configured transport templates with the required libaries and sample JNDI settings are provided. A generic JMS Transport template is also provided to allow MagooClient to connect to alternative JMS providers. If you would like a particular JMS offering to be added to the supported matrix then please contact Magoo Support.