Try OpenEdge Now
skip to main content
Messaging and ESB
Working with the Generic JMS Adapter : Configuring and administering the Generic JMS Adapter : Editing the jmsProvider.properties file
 

Editing the jmsProvider.properties file

The jmsProvider.properties file contains the class names for the provider specific connection factories for JMS client connection.
Open %DLC%\properties\jmsProvider.properties in a text editor, and add the JMS provider’s name and the following properties with the required connection factory classes:
[MyJMSProvider]
javax.jms.ConnectionFactory=
javax.jms.QueueConnectionFactory=
javax.jms.TopicConnectionFactory=
Note: The jmsProvider.properties file contains the commonly used JMS provider names. You can add your JMS provider’s name and the properties in the same format if it is not listed.
Here is a sample of the jmsProvider.properties file that provides connection factory class names for WebSphereMQ and ActiveMQ.
[WebSphereMQ]
javax.jms.ConnectionFactory=com.ibm.mq.jms.MQConnectionFactory
javax.jms.QueueConnectionFactory=com.ibm.mq.jms.MQQueueConnectionFactory
javax.jms.TopicConnectionFactory=com.ibm.mq.jms.MQTopicConnectionFactory

[ActiveMQ]
javax.jms.ConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory
javax.jms.QueueConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory
javax.jms.TopicConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory
Note: Do not modify the javax.jms.ConnectionFactory, javax.jms.QueueConnectionFactory, and javax.jms.TopicConnectionFactory property names. The property values for these property names must be specific to the provider.