Consultor Eletrônico

SUMMARY:

This solution discusses whether and how several types of non-Java
applications can act as Progress SonicMQ messaging clients.

EXPLANATION:

HTML:

HTML alone does not provide the connection context necessary to
serve as a messaging client. However, you can use a Java applet
within HTML to access the SonicMQ Application Programming
Interface (API). You can invoke SonicMQ messaging calls from any
type of Java component including applets, servlets, application
servers and Enterprise JavaBeans (EJB).
You can launch a Java applet from HTML within the browser context
to allow the receiver to participate as a SonicMQ client.

ACTIVEX:

SonicMQ can also be called using the ActiveX API included with the
product. The SonicMQ JMS interface is packaged for ActiveX so that
objects and methods in the native Java classes are wrappered and
the Java events are presented like native ActiveX control events.
By bridging SonicMQ to ActiveX, Windows NT developers can use
familiar tools to make components that interface to JMS: Progress
4GL, Microsoft Visual C++, Microsoft Visual Basic, Borland C++,
Borland Delphi, Java and others. Refer to Progress Knowledge Base
solutions: 19464, 19762, 19735, 19680, and 19664 for further
information on ActiveX.

4GL/WebSpeed:

In 9.1B/3.1B release, Progress introduces a SonicMQ Adapter that
provides JMS support from the Progress 4GL to SonicMQ. The 4GL
programmer can use the full features of the Java Messaging Server
without knowing all the details of the technology. The adapter
works on all platforms and with all client configurations: GUI,
character, AppServer, and WebSpeed agents and batch.

SonicMQ can be called from a Java applet that can be initiated by
a WebSpeed application. However, once this applet is launched it
does not have any connection to WebSpeed. With the 4GL adapter, a
SonicMQ messaging client can also be run by a WebSpeed Web Object.

Reference to Written Documentation:
Knowledge Base Solutions at www.techweb.progress.com.

www.sonicmq.com.