Messaging is the exchange of information by two or more software applications. A message is a self-contained package of information.
Many Adaptive Server customers use messaging and queuing, or publishing and subscription systems in their own application environments. These applications are called message-oriented middleware. Often, the same application combines database operations with messaging operations.
Real-Time Messaging Services (RTMS), simplifies the development of such applications, using Adaptive Server with TIBCO Java Messaging Service (JMS) and IBM WebSphere MQ (MQ).
Messaging systems allow senders and receivers to be detached. A messaging system can be asynchronous, in that an application can send messages without requiring receiving applications to be running.
JMS and MQ are APIs that define the way in which clients communicate with message providers. The message sender and the message receiver both act as clients to the message provider.
Messaging systems are provided by message providers. The messaging provider can implement architecture that centralizes or decentralizes the storage of messages, or that is a hybrid of the two.
RTMS performs messaging operations within SQL statements, using built-in functions.
Real-Time Messaging Services provide a way to capture transactions (data changes) in an Adaptive Server database and deliver them as events to external applications using either:
JMS message bus, provided by TIBCO Enterprise for JMS, or
Message Queue Interface (MQI), provided by WebSphere MQ.
