OpenEdge Adapter for SonicMQ configuration and management
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) — ServerConnect is for OpenEdge Application Servers (WebSpeed and AppServer). With this configuration there is a single adapter process per AppServer process, allowing multiple Application Server agents to connect to this single adapter process. ServerConnect is configured at the server.
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.
Note: For BrokerConnect, the OpenEdge installation program creates one instance of the OpenEdge Adapter for SonicMQ. In most circumstances, this single adapter instance is sufficient. Although it is possible to create additional instances, there is normally no reason to run multiple OpenEdge Adapter for SonicMQ instances on the same host. Each instance of BrokerConnect runs as a broker process. This process is multi-threaded, with one thread for each active client application; it can connect to any SonicMQ Broker.
For information on the OpenEdge Adapter for SonicMQ architecture, see OpenEdge Getting Started: Application and Integration Services.
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.