Prior to OpenEdge 10.1A the SonicMQ Adapter architecture was (and still is) a server based component, the existing connection mode is now known as OpenEdge Adapter for SonicMQ BrokerConnect (BrokerConnect) - BrokerConnect is for ABL 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.
Note: In OpenEdge 12.2 the Generic JMS Adapter (formerly known as SonicMQ Adapter) is started as a standalone process (using oemessaging[.bat/.sh]) as the Unified Broker has been removed from the product:
How to Start/Stop and get the status of the SonicMQ Adapter in OpenEdge 12.0?
Two additional connection modes were added in 10.1A:
OpenEdge Adapter for SonicMQ ClientConnect (ClientConnect) - ClientConnect is for OpenEdge clients and will run transparently as a background process in conjunction with a Progress ABL client or OpenEdge Application Server agent process, with a single adapter process per client process. The application running on the ABL client handles messaging control. ClientConnect takes little or no configuration.
OpenEdge Adapter for SonicMQ ServerConnect (ServerConnect) -ServerConnect is for OpenEdge Application Servers (WebSpeed and AppServer). With this configuration there is a single adapter process per AppServer Broker process, allowing multiple Application Server agents to connect to this single adapter process. ServerConnect is configured at the server.
Note: Please refer to the documentation on how to setup these connection modes.
