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.

The Internet Data Access Presentation (IDAP)<br />

Table 17–3 Client Requests for Dequeue—Arguments and Attributes for AQXmlReceive<br />

Argument Attribute<br />

consumer_options destination—specify the queue/topic from which messages are to be<br />

received. The destination element has an attribute lookup_type which<br />

determines how the destination element value is interpreted<br />

DATABASE (default)—destination is interpreted as<br />

<br />

schema.queue_name<br />

LDAP—the LDAP server is used to resolve the destination<br />

- consumer_name—Name of the consumer. Only those messages matching<br />

the consumer name are accessed. If a queue is not set up for multiple<br />

consumers, then this field should not be specified<br />

- wait_time—the time (in seconds) to wait if there is currently no message<br />

available which matches the search criteria<br />

- selector—criteria used to select the message, specified as one of:<br />

- visibility<br />

correlation—the correlation identifier of the message to be<br />

<br />

dequeued.<br />

message_id— the message identifier of the message to be dequeued<br />

condition—dequeue message that satisfy this condition.<br />

<br />

A condition is specified as a Boolean expression using syntax similar to the<br />

WHERE clause of a SQL query. This Boolean expression can include<br />

conditions on message properties, user data properties (object payloads<br />

only), and PL/SQL or SQL functions (as specified in the where clause of a<br />

SQL query). Message properties include priority, corrid and other<br />

columns in the queue table<br />

To specify dequeue conditions on a message payload (object payload), use<br />

attributes of the object type in clauses. You must prefix each attribute with<br />

tab.user_data as a qualifier to indicate the specific column of the queue<br />

table that stores the payload. The deq_condition parameter cannot exceed<br />

4000 characters.<br />

ON_COMMIT (default)—The dequeue is part of the current transaction.<br />

<br />

The operation is complete when the transaction commits.<br />

IMMEDIATE—effects of the dequeue are visible immediately after the<br />

<br />

request is completed. The dequeue is not part of the current transaction.<br />

The operation constitutes a transaction on its own.<br />

Internet Access to <strong>Advanced</strong> <strong>Queuing</strong> 17-21

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

Saved successfully!

Ooh no, something went wrong!