The Progress OpenEdge JMS Adapter allows you to connect to third-party JMS
providers including SonicMQ, ActiveMQ, WebSphereMQ, and more. JMS clients connect to the
JMS server differently for different JMS providers, and require different connection
strings. For example:
SonicMQ connection requires the SonicMQ Broker URL such as
tcp://myhost:2506
ActiveMQ connection requires the ActiveMQ broker URL such as tcp://myhost:61616
WebSphereMQ connection requires the QueueManager name as it is
configured in the JNDI namespace.
As the Progress OpenEdge JMS Adapter behaves as a proxy client for the JMS
connection, the ABL API that creates connection with the JMS provider must provide an
appropriate input for the provider.
The following figure shows the architectural relationships between the Progress
OpenEdge JMS Adapter and the JMS provider Broker in BrokerConnect mode:
If you wish to wish to migrate your applications from SonicMQ to another
JMS provider such as ActiveMQ or WebSphereMQ, you must modify your ABL-JMS API to point
to the appropriate MQ Broker URL as follows:
Update WebSphereMQ connection strings
For WebSphereMQ:
RUN setBrokerURL IN psSessionH (INPUT "SampleQMgr").
where
SampleQMgr is the name of the QueueManager or
the connection factory for the queue or the topic that you want to use.
Note:
You can create the Connection Factory in the WebSphere
MQClient Mode as ConnectionFactory, QueueConnectionFactory, or TopicConnectionFactory. When an ABL client
tries to use the Connection Factory that you created, make sure that the ABL
Session type and the corresponding ConnectionFactory that you are using to connect are compatible
as listed below:
Use jmsSession with ConnectionFactory, TopicConnectionFactory or QueueConnectionFactory.
