Kbase P135034: What are the different methods to connect to SonicMQ from OpenEdge ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/3/2011 |
|
Status: Unverified
GOAL:
What are the different methods to connect to SonicMQ from OpenEdge ?
GOAL:
What are the connection modes for the SonicMQ 4GL Adapter ?
FACT(s) (Environment):
OpenEdge 10.1x
All Supported Operating Systems
FIX:
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.
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 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.