Advanced Queuing - Oracle

General Features of Advanced Queuing
Persistence for Scheduling
Queuing systems need message persistence so they can deal with priorities:
messages arriving later may be of higher priority than messages arriving earlier;
messages arriving earlier may have to wait for messages arriving later before
actions are executed; the same message may have to be accessed by different
processes; and so on. Priorities also change. Messages in a specific queue can
become more important, and so need to be processed with less delay or interference
from messages in other queues. Similarly, messages sent to some destinations can
have a higher priority than others.
Persistence for Accessing and Analyzing Metadata
Message persistence is needed to preserve message metadata, which can be as
important as the payload data. For example, the time that a message is received or
dispatched can be a crucial for business and legal reasons. With the persistence
features of Advanced Queuing, you can analyze periods of greatest demand or
evaluate the lag between receiving and completing an order.
General Features of Advanced Queuing
The following general features are discussed:
Point-to-Point and Publish-Subscribe Messaging
Oracle Internet Directory
Oracle Enterprise Manager Integration
Message Format Transformation
SQL Access
Support for Statistics Views
Structured Payloads
Retention and Message History
Tracking and Event Journals
Queue-Level Access Control
Nonpersistent Queues
Support for Oracle9i Real Application Clusters
XMLType Payloads
Introduction to Oracle Advanced Queuing 1-5