Applies to ReadyAPI 3.0, last modified on November 12, 2019

Use the JMS Servers tab of the Environments editor to modify JMS connections for different environments. ReadyAPI will use the specified JMS servers when you switch between environments.

Tip: To add a new JMS server, use the JMS dialog.
ReadyAPI: The JMS Servers tab of the Environments editor

Click the image to enlarge it.

On the JMS Servers tab, you can see all the JMS servers that were configured in the JMS dialog. The table has the following columns:

Column Description
Name The JMS server name.
Initial Context Factory Class The class that will be used to create an InitialContext object. You specify it when adding a row to the table. See below.
Provider URL URL of the JMS server you use. The JMS Connector plugin sets a default value for the selected provider.
Connection Factory Name The name of the ConnectionFactory object you use to connect to the JMS broker. You specify it when adding a row to the table. See below.

To add server options, create new JMS connections in the JMS dialog.

To edit server options, select a server and click , or double-click the server’s name in the table:

ReadyAPI: The JMS server options in the Environments editor

Click the image to enlarge it.

Here, you can edit the following properties:

Property Description
JMS Provider A list of preconfigured JMS providers.
Install the JMS Connector plugin for your JMS provider in order for it to appear in the list.
Initial Context Class The class that will be used to create an InitialContext object.
If you use the JMS Connector plugin, this value is provided by the plugin and cannot be changed. Otherwise, you need to specify it manually. Here are context classes for some popular JMS providers:
Apache ActiveMQ org.apache.activemq.jndi.ActiveMQInitialContextFactory
IBM WebSphere MQ    Depends on how the context class is configured.
For more information, see WebSphereMQ Configuration.
Oracle Weblogic weblogic.jndi.WLInitialContextFactory

For other JMS providers, you can find the initial context class name in the provider documentation.

Provider URL The URL of the JMS server you use. The JMS Connector plugin sets a default value for the selected provider.
Connection Factory JNDI Name The name of the ConnectionFactory object you use to connect to the JMS broker. For most JMS providers, you can specify the name when setting up the provider.
The JMS Connector plugin sets a default value for the selected provider.
User Name The name of the user that is used to authenticate with the JMS broker.
Password The password of the user who authenticates with the JMS broker.
Additional JNDI Properties Custom JNDI properties that you may need depend on the JMS provider you use.
For example, the ActiveMQ JMS broker does not include a fully functional JNDI server, so you need to use the properties to provide JNDI context for your requests. You do this by adding custom properties, such as queue.SampleQueue = SampleQueue for static queues. For more information about working with JNDI in ActiveMQ, see the ActiveMQ documentation.
JMS testing: JNDI destination name

Click the image to enlarge it.

See Also

SOAP Services Tab
REST Services Tab
Custom Properties Tab
JDBC Connections Tab
Environments

Highlight search results