Try OpenEdge Now
skip to main content
Messaging and ESB
OpenEdge Applications in the Sonic Environment : OpenEdge Adapters for Sonic integration : OpenEdge Adapter for SonicMQ : OpenEdge Adapter for SonicMQ operation
 
OpenEdge Adapter for SonicMQ operation
The following table shows the operation features for each connection mode.
Table 1. Adapter features
Feature
BrokerConnect
ClientConnect
ServerConnect
Unified Domain
Yes
Yes
Yes
Client Persistence
No
Yes
Yes
Fault Tolerance
No
Yes
Yes
Message Selectors
Yes
Yes
Yes
Serialized Connections
Yes
Yes
Yes
Temporary Queues and Topics
Yes
Yes
Yes
To establish a connection and start a session, the client application identifies connection options as an argument to the ptpsession, pubsubsession, jmssession procedure (depending on the chosen JMS messaging domain), specifies the appropriate SonicMQ Broker as an argument to the setBrokerURL procedure, and runs the beginSession procedure.
Messages are processed when the application is in a WAIT-FOR or other IO-blocking state. Non-UI applications, such as AppServer processes or batch processes that cannot use WAIT FOR, can use the waitForMessages procedure, as can all GUI, character, AppServer, WebSpeed, and batch applications. Applications use the existing ABL error-handling mechanisms to deal with ABL–JMS errors.
After the application finishes executing, it calls deleteSession procedure to free adapter resources for use by other clients.