D³ MQSeries Server Interface isTigerLogic's implementation of the IBM MQSeries (now known as WebSphere MQ) API (MQI) (see below) in FlashBASIC. This API is an extension to the standard Pick/BASIC programming language. The D³ MQI interface is a collection of BASIC calls. The entire underlying infrastructure to communicate with the MQSeries server is handled by this API. As a developer, the benefit of D³ MQSeries is that it allows interoperability between D³ or other RDBMS-based systems via messaging. You do not need to worry about setting up a communication layer and protocol with the foreign system.

D³ MQSeries Server Interfaceprovides ease of integration between heterogeneous applications. An advantage is D³ MQSeries can be used between D³ servers for data replication or Hot Backup solution by adding the MQI subroutine calls to CALLx functions.

Overall, with D³ MQSeries Server Interface, the underlying networking layer is completely hidden from the developer.

For more information on D³ MQSeries Server Interface, please send an e-mail to connectivity@tigerlogic.com.

About MQSeries

WebSphere MQ is a Message Queuing middleware system by IBM. It comprises a server interface that manages message queues from different computer systems. A client interface is used to communicate with a server queue. This client interface is in the form of an API coupled with a network interface. It is the network layer that allows applications from different platforms and operating systems to exchange information. MQSeries shields the developer from the complexity of data interchange.

The principle is very simple: Program A sends a message to a selected queue (a system can have more than one queue) and forgets about the message. Whenever appropriate, Program B fetches the messages from the queue for processing. There is no direct interaction between Program A and Program B. If B detects an error on the message or needs more information from A, B sends a message to A via the queue.

Messages sent between Program A and Program B are straight ASCII text streams. Before a transaction can be performed, A and B need to agree on a message format. In many cases, XML is the format of choice.

MQSeries serves as a mail P.O. box. Messages are deposited into a numbered box. Whoever has access to the box then retrieves the messages in the order they were received.

There are many advantages to this solution:

• A and B do not need to know each other.
• A and B can be running on totally different hardware and software. They just need to be able to talk to the queue.
• Developers do not need to worry about communication protocols and network configurations.
• The MQSeries API implementations on different platforms are identical; learn once and use anywhere.
• MQSeries is cross-platform.

For more information on MQSeries, please visit IBM's web site at http://www-01.ibm.com/software/integration/wmq/