Using JMS CTS

In order to use JMS CTS, the following are required:

  • A JMS provider
  • A proxy to enable the JMS CTS to connect to, and administer, the JMS provider
  • A configuration file to enable the JMS CTS to locate the proxy classes
These are discussed in the following sections.

JMS Providers

There are many JMS providers available, both commercial and opensource, some of which are listed below:

OpenJMS
JBossMQ
JORAM
SonicMQ
SwiftMQ
FioranoMQ
iBus//MessageServer

Proxies

The JMS CTS requires a set of proxy classes to connect to a JMS provider and administer it.

These are needed as the JMS specification does not mandate how a JMS provider should be connected to, or administered.

The JMS CTS is distributed with sample proxies for OpenJMS , FioranoMQ and iBus//MessageServer . These can be used as guides when developing proxies for other JMS implementations.

Configuration

To configure the JMS CTS to test a JMS provider, the provider proxy and any dependent JARS need to be added to $JMSCTS_HOME/config/providers.xml . E.g.: 

<?xml version="1.0"?>
<configuration>

  <provider>
    <name>OpenJMS</name>
    <class>org.exolab.jmscts.openjms.OpenJMSProvider</class>
    <paths>
      <path>${jmscts.home}/lib/openjms-provider-0.5-b2.jar</path>
      <path>${openjms.home}/lib/openjms-0.7.6-rc2.jar</path>
    </paths>
    <config>
      <path>${openjms.home}/config/openjms.xml</path>
    </config>
  </provider>

</configuration>

In the above:

  • < class > specifies a class implementing the Provider interface.
  • < paths > lists the JARS that are required to test the provider.
  • < config > specifies properties to configure the provider with, using java bean naming conventions.