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 Data Services (RTDS), simplifies the development of such applications, using Adaptive Server with TIBCO Enterprise Messaging Service (EMS).
EMS is the TIBCO implementation of a Java messaging
service (JMS). Since Adaptive Server only supports EMS, the reference
to EMS and JMS refer to the same thing in this document.
Messaging systems allow senders and receivers to be detached. Not all components must be running, and connected for operation at all times. A messaging system can be asynchronous, in that an application can send messages without requiring receiving applications to be running.
JMS 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 is centralized or decentralized, or a hybrid of the two.
Adaptive Server performs messaging operations within SQL statements, using built-in functions.
Real-Time Data Services provide a way to capture transactions (data changes) in an Adaptive Server database and deliver them as events to external applications using JMS message bus, provided by TIBCO EMS.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
