The OpenEdge Adapter for SonicMQ ClientConnect (ClientConnect) architecture combines the adapter with the OpenEdge client process. ClientConnect runs as a process started and managed by OpenEdge clients directly when an application requires messaging. There is a single adapter process per client process, as shown in the following figure. The SonicMQ Broker acts as a service point for all JMS sessions.
Figure 28. OpenEdge Adapter for SonicMQ ClientConnect architecture
ClientConnect provides a direct connection between an ABL client and the SonicMQ Broker. This connection provides complete and reliable end-to-end messaging, and supports message fault tolerance. Additionally, ClientConnect supports JMS domain unification, client persistence, server-based message selectors, serialized connection objects, temporary destinations, TempTable messages, DataSet messages, and enhanced XML support.
