Try OpenEdge Now
skip to main content
Messaging and ESB
Working with the Generic JMS Adapter : Configuring BrokerConnect

Configuring BrokerConnect

The generic JMS adapter allows you to connect to SonicMQ, ActiveMQ, and WebSphereMQ JMS providers. JMS client connects to the JMS server differently for different JMS and thus needs different inputs as follows:
*SonicMQ connection requires the SonicMQ Broker URL such as tcp://myhost:2506
*ActiveMQ connection requires the ActiveMQ provider URL such as tcp://sampleHost:61616
*WebSphereMQ connection requires the QueueManager name as it is configured in the JNDI namespace.
As generic 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.
If you wish to wish to migrate your applications from SonicMQ to ActiveMQ or WebSphereMQ, you must modify your ABL-JMS API to point to the appropriate MQ Broker URL as follows:
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.
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.
*Use pubsubSession with only TopicConnectionFactory
*Use ptpSession with only QueueConnectionFactory
For ActiveMQ:
RUN setBrokerURL IN psSessionH (INPUT "myhost:61616").
where 61616 is the port at which the ActiveMQ Broker URL is listening.