Advanced Queuing - Oracle

Converting Messages
Because the MQSeries native message format does not allow you to specify
user-defined message property information, you cannot specify values that the
gateway MQSeries driver interprets as values to use for AQ message properties. As
a result, the AQ message properties of the message enqueued to the destination
queue are based on the default mappings described in Table 18–1 and the default
values for the remaining (nonmapped) AQ properties.
Using XML Message Propagation: Examples
This section provides examples of how to set up propagation between AQ queues
with ADT payloads and foreign queues using XML messages.
The messages to propagate in the examples are book orders. The payload type of
the AQ queue, AQ_book_orders, is book_order_typ. The foreign queue, FQ_
book_orders, is capable of storing XML documents.
The following PL/SQL script creates entities in the Oracle database for the two
inbound and outbound propagation examples that follow. Assume that the script is
run by database user mgwuser.
-- create the type book_order_typ
CREATE OR REPLACE TYPE book_order_typ AS OBJECT
(
order_no number,
book_name varchar2(100),
book_isbn varchar2(15),
book_amount number,
payment varchar2(30),
ship_addr varchar2(160),
order_date date
);
/
-- grant privilege to PUBLIC
GRANT EXECUTE ON book_order_typ to PUBLIC;
BEGIN
-- create queue table
dbms_aqadm.create_queue_table(
queue_table => ‘book_order_qtab’,
queue_payload_type => ‘book_order_typ’,
multiple_consumers => TRUE,
compatible => ‘8.1’);
-- create the queue
dbms_aqadm.create_queue(
18-40 Oracle9i Application Developer’s Guide - Advanced Queuing