Publishing Reports to the Web - Downloads - Oracle

Integrating with Oracle Advanced Queuing
Then we enqueue the message using the enqueue procedure provided by Advanced
Queuing.
…
dbms_aq.enqueue(queue_name => 'myQueue',
enqueue_options => enqueue_options,
message_properties => message_properties,
payload => PList_Object,
msgid => message_handle);
…
The message is put into the queue. Because we did not set up any message
distribution, the message will stay in the queue until it is fetched by a
dequeuing-procedure, which is discussed in the next section.
17.4.3 Creating the Dequeuing Procedure
Note: For the exact syntax of dbms_aq.enqueue refer to the
Advanced Queuing API Reference document.
You'll find additional examples in the srwAQsetup.sql file
included with your OracleAS Reports Services installation.
Look for upcoming information about Reports APIs on the Oracle
Technology Network, (http://otn.oracle.com).
A dequeuing procedure reads out all available messages in a queue and processes
them. In our case, we want to read out the message and submit a job to the server
using the parameter list that was attached to the message.
To accomplish this, we follow this example:
BEGIN
dequeue_options.wait := 1;
loop
DBMS_AQ.DEQUEUE(queue_name => 'myQueue',
dequeue_options => dequeue_options,
message_properties => message_properties,
payload => PList_Object,
msgid => message_handle);
COMMIT;
plist := plist_object.params;
r_jid := SRW.RUN_REPORT(plist);
end loop;
exception when aq_timeout then
begin
NULL;
end;
END;
This code example will read out the queue until all messages have been processed.
Time allowed for processing is determined by the time-out defined in the second line
of code. This time-out defines the amount of seconds the dequeue procedure should
wait for a message before creating a time-out exception.
The DBMS_AQ.DEQUEUE built-in is provided by Advanced Queuing for reading out
messages. It puts the payload of the message, the object that holds the information,
into the object defined by the payload parameter.
Using Event-Driven Publishing 17-9