09.12.2012 Views

Advanced Queuing - Oracle

Advanced Queuing - Oracle

Advanced Queuing - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Support for Statistics Views<br />

Structured Payloads<br />

Basic statistics about queues are available using the GV$AQ view.<br />

General Features of <strong>Advanced</strong> <strong>Queuing</strong><br />

You can use object types to structure and manage message payloads. RDBMSs in<br />

general have a richer typing system than messaging systems. Since <strong>Oracle</strong> is an<br />

object-relational DBMS, it supports both traditional relational types as well as<br />

user-defined types. Many powerful features are enabled as a result of having<br />

strongly typed content, such as content whose format is defined by an external type<br />

system. These include:<br />

Content-based routing: <strong>Advanced</strong> <strong>Queuing</strong> can examine the content and<br />

<br />

automatically route the message to another queue based on the content.<br />

Content-based subscription: a publish and subscribe system is built on top of a<br />

<br />

messaging system so that you can create subscriptions based on content.<br />

Querying: the ability to execute queries on the content of the message enables<br />

<br />

message warehousing.<br />

To see this feature applied in the context of the BooksOnLine scenario, refer to<br />

"Structured Payloads" on page 8-11.<br />

Retention and Message History<br />

The systems administrator specifies the retention duration to retain messages after<br />

consumption. <strong>Advanced</strong> <strong>Queuing</strong> stores information about the history of each<br />

message, preserving the queue and message properties of delay, expiration, and<br />

retention for messages destined for local or remote receivers. The information<br />

contains the enqueue and dequeue times and the identification of the transaction<br />

that executed each request. This allows users to keep a history of relevant messages.<br />

The history can be used for tracking, data warehouse, and data mining operations,<br />

as well as specific auditing functions.<br />

To see this feature applied in the context of the BooksOnLine scenario, refer to<br />

Retention and Message History on page 8-27.<br />

Tracking and Event Journals<br />

If messages are retained, they can be related to each other. For example, if a message<br />

m2 is produced as a result of the consumption of message m1, m1 is related to m2.<br />

This allows users to track sequences of related messages. These sequences represent<br />

Introduction to <strong>Oracle</strong> <strong>Advanced</strong> <strong>Queuing</strong> 1-9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!