Use the JMS 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.
 |
On the JMS 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 |
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 |
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:
 |
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 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:
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 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  |