Progress
External Program
Interfaces
SonicMQ Adapter Architecture
The SonicMQ Adapter belongs to the AppServer administration framework, which includes the Progress Explorer and NameServer. The SonicMQ Adapter can be started and configured by the Progress Explorer and from the command line. 4GL applications connect to the SonicMQ Adapter by specifying the connection parameters of the NameServer when the JMS session is created. Figure 13–1 shows one possible context for the SonicMQ Adapter. The application does not have to be on the Progress AppServer, nor is it even typical to have two SonicMQ Adapter brokers. The only software requirement on the 4GL side is a set of .r files that make the interface to the SonicMQ Adapter.
The installation process installs these files for the 4GL–JMS API: <Progress_install_dir>
/jms/*.r
and <Progress_install_dir>/jms/impl/*.r.
As shown in Figure 13–2, each 4GL application connection has its own thread in the SonicMQ Adapter process. Only one broker process runs, but it is multi-threaded, with each 4GL client having its own thread running. These threads talk to SonicMQ. (This differentiates the SonicMQ Adapter from AppServer or WebSpeed, which both have one or more Progress process agents running.) It is also possible to start more than one SonicMQ Adapter process under a single NameServer.Figure 13–2: The SonicMQ Adapter Architecture
![]()
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |