The OpenEdge Adapter for SonicMQ allows OpenEdge applications to communicate via JMS Messaging through SonicMQ. The OpenEdge Adapter for SonicMQ consists of three connection modes:
-
OpenEdge Adapter for SonicMQ ClientConnect (ClientConnect)
ClientConnect is for OpenEdge clients and will run transparently as a background process in conjunction with an OpenEdge client or OpenEdge Application Server agent process, with a single adapter process per client process. The application running on the OpenEdge client handles messaging control. ClientConnect takes little or no configuration.
-
OpenEdge Adapter for SonicMQ ServerConnect (ServerConnect)
The ServerConnect is for OpenEdge Application Servers (WebSpeed and AppServer). With this configuration, there is a single adapter process per unified broker process, allowing multiple Application Server agents to connect to this single adapter process. ServerConnect is configured at the server.
The ServerConnect process that runs inside of the AppServer or WebSpeed server is multi-threaded and allows for multiple SonicMQ connections within the same process. Additionally, each connection to a SonicMQ Broker uses multiple threads.
Prior to using ServerConnect in an AppServer or WebSpeed server, the AppServer or WebSpeed server must be enabled for SonicMQ ServerConnect enabled using Progress Explorer or by directly editing following entry in ubroker.properties file using MQEnabled=1 parameter.
-
OpenEdge Adapter for SonicMQ BrokerConnect (BrokerConnect)
BrokerConnect is for OpenEdge client applications. It runs as a separate server process to handle OpenEdge client requests. BrokerConnect is a Unified Broker product, part of the AppServer administration framework. Thus, you can use the Progress Explorer in Windows, and the command-line tools adaptconfig and adaptman on all supported platforms, to manage BrokerConnect. You can also edit its properties in the ubroker.properties file. No configuration is required within the SonicMQ environment.
