Information

Title	Does Progress provide a generic JMS adapter?

URL Name	000054543

Article Number	000170762

Environment	Product: OpenEdge Version: All supported versions OS: All supported platforms Other: OpenEdge Adapter for SonicMQ

Question/Problem Description

Does Progress provide a generic JMS adapter ?
Are there any options other than the OpenEdge Adapter for SonicMQ to allow integration between the ABL and JMS messaging ?
Is STOMP a viable option for generic ABL-JMS messaging ?
Does Progress provide an adapter for IBM WebSphereMQ ?
Does Progress provide an adapter for ActiveMQ ?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

Prior to OpenEdge 11.5.1, the only certified option for integrating ABL with JMS is the OpenEdge Adapter for SonicMQ. This adapter only works with the SonicMQ JMS Provider.

In OpenEdge 11.5.1, a new Generic JMS Adapter was introduced.

The following whitepaper documents the new generic JMS Adapter in OpenEdge 11.5.1:
https://community.progress.com/community_groups/openedge_development/m/documents/1986.aspx
Please refer to the "OpenEdge Development: Messaging and ESB" documentation for OpenEdge 11.6 or later:
https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dvesb/configuring-and-administering-the-generic-jms-ad.html
The Generic JMS Adapter adapter allows integration with any JMS-compliant vendor, for example: SonicMQ, IBM WebSphereMQ and ActiveMQ. As such there is no compatibility matrix available for the Generic JMS Adapter.
In OpenEdge 11.5.1 and 11.6.0, the Generic JMS Adapter is only supported with the BrokerConnect adapter mode.
In OpenEdge 11.6.1, the Generic JMS Adapter supports BrokerConnect and ClientConnect. In addition, classic Appserver and Webspeed support the ServerConnect adapter mode.
The Pacific AppServer for OpenEdge (PASOE) does not support ClientConnect or ServerConnect, it still only supports the BrokerConnect adapter mode. Refer to Article
- Error 12667 running SonicMQ ClientConnect after starting the PASOE instance with tcman

Workaround

Prior to 11.5.1, one potential alternative for integration ABL with a non-Sonic JMS Provider is a third party adapter called STOMP. For more information refer to www.dotr.com

Notes

References to other Documentation:

Progress Articles:

How to stagger an OpenEdge Client migration from SonicMQ to another JMS Provider?
Error 12667 running SonicMQ ClientConnect after starting the PASOE instance with tcman

Keyword Phrase

Last Modified Date	11/20/2020 7:14 AM

Does Progress provide a generic JMS adapter?

Information